Updating games via Content Updates (CUs)
Updates, also known as patches, to XBOX games are called Content Updates (CUs). Each CU is uploaded to Partner Center as a complete package replacement, rather than using a separate update file that includes only the changes from the base game. After a CU passes certification and is published to the RETAIL sandbox, users will download only the new and updated files, minimizing the update size. There’s no charge to submit and release CUs. Also, there’s no limit to the number of updates that you can make over the life of your title. When submitting CUs, pay close attention to the Identity section of the MicrosoftGame.config file. Set a version number that’s higher than the version used in any builds submitted previously, and ensure that the IdentityName and IdentityPublisher values are unchanged. For detailed advice about building your packages, see Packaging overview.Testing Content Updates via Package Flight
We recommend that all CUs are tested in the RETAIL sandbox by using Package Flights, before you release them to the public. Testing in RETAIL enables you to validate that the CU functions as expected before you release it to players. This testing can be done before, during, or after certification. For more information, see Publishing and testing in the RETAIL sandbox and How to configure package flights for game packages.Bypass testing and the Cert Bypass program
All games are eligible to qualify for the Cert Bypass program. If a game has no unfixed Conditions for Resubmission (CFRs), CUs submitted for certification after the game releases are eligible to bypass full XBOX Requirement (XR) testing. CUs for PC games must still complete submission checks, including malware scanning. Cert Bypass CUs should take no more than one business day to be processed. You might choose to opt out of Bypass testing, or your XBOX contacts might recommend or require you to opt out. If opting out is required, inform your XBOX team before you submit your CU to certification. Common scenarios where you might need to opt out include:- Features being added to the game that require testing never previously completed, such as adding a new significant gameplay mode.
- Updating from the XBOX One XBOX Development Kit (XDK) to the Game Development Kit (GDK).
- Adding support for a new type of DLC that wasn’t tested previously, for example, adding support for a game expansion if you previously only released cosmetic items.
If a CFR is found during testing after you opt out of Cert Bypass, your next CU isn’t eligible for Cert Bypass and requires full testing until all CFRs are fixed.
Updates to XBOX services Gameplay Settings
Updates to XBOX services Gameplay Settings can be used to add new achievements, adjust title storage, add leaderboards, and more. All XBOX services Gameplay Settings validation is automated within Partner Center. These settings can be published to RETAIL directly and don’t require testing by XBOX Certification. Contact your XBOX team if you experience any problems when publishing updated XBOX services Gameplay Settings.Region expansions
If a product is initially released to only a subset of markets, you might want to release it to more markets post-launch. If not provided via the International Age Rating Coalition (IARC) ratings system, appropriate age ratings must be acquired and configured in the product’s Age Ratings module in Partner Center before you release to any new markets.- For digital-only releases, markets can be configured by updating Pricing and Availability in Partner Center.
- For games released on disc, you might need to create an updated disc that includes the age ratings for the new markets. If the required age ratings are included in the original disc, it isn’t necessary to create a new disc.