- Get Full XBOX services.
- Choose what happens to achievements.
- Set the embargo.
- Publish the configuration to RETAIL.
1234ABCD and a development sandbox, XDKS.1, that holds
the configuration the build was tested with.
1. Get Full XBOX services
A new game starts with XBOX services disabled. Limited XBOX services work only in development sandboxes, and don’t include achievements or stats. After your game concept is approved, send the game’s Store ID to your XBOX representative and ask them to onboard the product. Then select Enable full XBOX services on the game’s Game setup page in Partner Center. See Enable XBOX services. Until then, configuration with achievements fails validation:2. Choose what happens to achievements
Achievements published to RETAIL are permanent. You can still change their names, descriptions, and art, but you can’t remove them or change their unlock rules or gamerscore. Stats published to RETAIL can’t be deleted either. The game’s achievement system, title-managed or event-based, is fixed by the first RETAIL publish. Before that publish, choose one of these:
A game for PC or XBOX consoles can’t skip publishing its achievements to RETAIL. In Partner
Center, answering No to Publish Achievements to Retail? fails with:
3. Set the embargo
The embargo hides the game’s achievements, presence, and other XBOX services data from players in the XBOX app and console UI until a date you choose, and blocks screenshots and video capture. Without one, players outside the playtest can see the game’s configuration. Set an embargo only for a game that isn’t released yet. On a released game, a new embargo hides its XBOX services data from its players. In Partner Center, open XBOX services > XBOX settings, go to Embargo date, and set a UTC date and time later than the playtest’s end, and no later than the game’s public release. If the playtest runs past the release, end the embargo at the release. Select Allow Multiplayer Invites in Embargo if testers invite each other to multiplayer sessions. See Configure embargo date. The embargo is a title-wide setting, stored in theALL sandbox, and applies to every sandbox.
To check it, download ALL:
productdeveloper.xml holds the embargo:
--sandbox-id HIDDEN:
lastPublish shows the
title-wide publish succeeded:
4. Publish the configuration to RETAIL
Publish the development sandbox’s configuration straight to RETAIL. RETAIL doesn’t require a publish to CERT first, or certification. Validate first. Validation changes nothing, and lists the achievements the publish adds:FirstRetailPublishWithoutEffectiveEmbargo warning, no embargo is in
effect yet. Finish step 3, including the title-wide publish.
Publishing from XDKS.1 replaces RETAIL’s working documents that have the same names, and
RETAIL’s global title storage files, deleting any files only RETAIL holds. See
Cross-sandbox publishing.
When the validation is clean, publish. The command describes the publish and asks first:
lastPublish until the publish finishes:
