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.XBOX Rapid Updates
All games are eligible to qualify for the XBOX Rapid Updates program. If a base game passes XBOX certification with no unfixed Conditions for Resubmission (CFRs), subsequent CUs submitted for certification are eligible to bypass full XBOX Requirement (XR) testing. CUs for PC games must still complete submission checks, including malware scanning. Qualifying XBOX Rapid Updates should take no more than one business day to be processed. Some updates must be tested even when your game qualifies for XBOX Rapid Updates. This applies to prerelease updates, including day-one updates, as well as post-release ones. Updates that must be tested include, but aren’t limited to, those that add functionality that didn’t previously exist and requires full certification. For example, updates that:- Add multiplayer to a formerly single-player game.
- Add cross-network play.
- Add mod support.
If a CFR is found during full XR testing, your game doesn’t qualify for XBOX Rapid Updates and future CUs require 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.
