Certification Tested Xbox Requirements for Xbox Console Games

Artikel
12/01/2023

Version 13.1 - 10/01/2024

Introduction

Xbox Requirements (XRs) consist of the policies, technical requirements, and product component-related requirements to which all developers and publishers of Xbox console titles must conform. XRs ensure that products created for Xbox consoles are not only stable and reliable but also provide a user experience that is consistent, safe, secure, and enjoyable.

Unless specifically noted, all Xbox Requirements apply to both the Xbox One and Xbox Series X|S console generations.

This page defines the XRs for the Xbox console games tested in Xbox Certification. For a list of all XRs, including those not tested in Xbox Certification, go to Xbox Requirements.
For a summary of the changes in this release, see changes in this release at the bottom of this page.
To review the historical change log of XRs and test cases, see Change History for Xbox Requirements and Test Cases.
View the top ten failing test cases on console.

Base Requirements

The requirements in this category apply to the general rules for the standards of coding, behavior of titles, and submission of titles.

XR-001: Title Stability *

Titles must be compliant with Microsoft Store policies regarding Title Stability. The following policy applies to this Requirement:

10.1.2
Your product must be fully functional and must provide appropriate functionality for targeted systems and devices.

001-01 Title Stability

Test Steps

Sign in to an Xbox profile.
Launch the title.
Navigate all areas of the title, including but not limited to:
- Gameplay
- Menus and features
- Downloadable content (DLC)
Using a new Xbox profile with no previous save data, repeat steps 1-3 while disconnected from Xbox services.

Expected Result
Title instability refers to any state where user input is not recognized, or the user is blocked from progressing due to a software crash without any user notification.

Pass Examples

The title is stable.
The title does not cause unintended loss of user data.

Fail Examples

The title crashes, becomes unresponsive, or causes a console reboot.
The title causes the loss of user data.
A non-interactive pause or static screen is presented lasting over twenty seconds.
The title contains a loading screen which is more than two minutes with no indication of progress.
The title contains a loading screen which is more than three minutes with a progress indicator.

001-02 Title Stability After Suspending

Test Steps

Sign into an Xbox profile.
Launch the title and progress into gameplay.
At various points during the title, suspend the title using xbapp suspend [PFN].
Wait at least 30 seconds for the title to fully suspend and for the suspension to interrupt any HTTP request.
After the title has successfully suspended, return to the title by selecting the tile from Home.
Verify that the title resumes without issue and that the user can continue with their save progress made from their last save point.
Continue to the next save point, save the game, and return to the main menu.
Reload the save made in step 7 and make sure all progress is still present.
Repeat steps 3-8 throughout the title.

Expected Result
Title instability refers to any state where user input is not recognized, or the user is blocked from progressing due to a software crash without any user notification. Additionally, users must not lose any save progress after returning to gameplay.

Pass Examples

The title is stable.
The title does not cause unintended loss of user data.
The game returns from a suspended state and the user is able to immediately continue from their last gameplay location.
The game returns from a suspended state and the user is prompted whether they want to resume from their last gameplay location.
The game returns from a suspended state and the game returns to a previous menu or initial interactive state, however the user is able to load their last save location.
After suspending during online gameplay that requires online service connectivity, the game returns from a suspended state and has returned the user to a previous menu or initial interactive state.
The package execution state is 'Package execution state: 4 (terminated)' as a result of the system terminating the title (typically the result of connected storage de-synchronization). Resume behavior is not expected as the title will be launched from a terminated state. The execution state can be observed by running xbapp query <Package Full Name> via the command line.

Fail Examples

The package execution state is 'Package execution state: 0 (unknown)' as a result of a failure to suspend. The execution state can be observed by running xbapp query <Package Full Name> via the command line.
The game returns from a suspended state and the package execution state is 'Package execution state: 0 (unknown)'. The execution state can be observed by running xbapp query <Package Full Name> via the command line.
The game returns from a suspended state then reboots back to the initial boot sequence.
The user is unable to re-establish a connection with the partner-hosted service.

001-03 Title Stability After Connected Standby

Configuration:
One console with the following configuration:

Instant sign-in enabled in Settings -> Account -> Sign-in, security & passkey -> Instant sign-in -> Use Instant sign-in.
Standby set in Settings -> General -> Sleep mode & startup -> Standby.

Test Steps

Enable the Instant-on setting and the Instant sign-in settings on the console (see Configuration).
Sign into an Xbox profile with the console set as a user's home console and with a license to the title.
Launch the title, sign into a profile and progress into gameplay.
Enter connected standby by pressing the power button on the console and waiting for the power button to stop blinking.
Resume from standby using the power button on the console.
Sign into the same Xbox profile as in Step 1 using auto sign in.
Re-launch the title and continue the title where the user left off.
Continue to the next save point, save the game, and return to the main menu.
Reload the save made in step 8 and make sure all progress is still present.
Repeat steps 3-9 throughout the title.

Pass Examples

The game returns from connected standby and the user is able to immediately continue from their last gameplay location.
The game returns from connected standby and the user is prompted whether they want to resume from their last gameplay location.
The game returns from connected standby and the game returns to a previous menu or initial interactive state, however the user is able to load their last save location.
After entering connected standby during online gameplay that requires online service connectivity, the game returns from connected standby and has returned the user to a previous menu or initial interactive state.
The package execution state is 'Package execution state: 4 (terminated)' as a result of the system terminating the title (typically the result of connected storage de-synchronization). Resume behavior is not expected as the title will be launched from a terminated state. The execution state can be observed by running xbapp query <Package Full Name> via the command line.

Fail Examples

The package execution state is 'Package execution state: 0 (unknown)' as a result of a failure to suspend. The execution state can be observed by running xbapp query <Package Full Name> via the command line.
The game returns from connected standby and the package execution state is 'Package execution state: 0 (unknown)'. The execution state can be observed by running xbapp query <Package Full Name> via the command line.
The game returns from connected standby then reboots back to the initial boot sequence.
The user is unable to re-establish a connection with the partner-hosted service.

XR-003: Title Quality for Submission *

Titles must be functionally complete, testable and meet Xbox console quality standards when they are submitted for certification.

Functionally Complete and Testable:
The title submission must include all client code, submission artifacts, and downloadable content. Partner services must be available and properly configured for testing and certification. Titles must package cleanly with no failures using the current version of Submission Validator when submitted to Microsoft, and they must include Submission Validator logs with their submission.

Xbox Quality Standards:
Games on Xbox consoles must function correctly across game modes in a variety of scenarios to meet player needs.

Title Integrity: Users must be able to complete all game modes and the title must provide a consistently playable experience for players. A playable experience varies per title, but generally means no severe drops in frame rate, no freezes, impasses, bugs causing major progression hindrances, or graphical corruptions.
Options and Settings: Game Settings, such as options, controls, and languages are applied correctly when updated in game and after terminating and launching the title again. Default console settings are respected where appropriate.
Navigation and Content Availability: There are no dead ends in content, the game menus can be navigated and all content is available (where appropriate).
Supports players with low and high friend counts: experiences remain stable and function when a player has no friends or a large number of friends. Typically, a large number of friends can cause issues in areas with stats posting/retrieval
Gameplay functions with the allowed number of local or online multiplayer players: Using supported modes, the gameplay modes function using the supported mix of local or online players
Save Game Compatibility: Save games and/or player progress continue to function following content updates. Additionally, permanent save data loss must not occur when loading an updated save with the base disc version.
Suspend and Resume: Title progress is preserved when resuming from connected standby or suspension.

003-02 Title Integrity

Test Steps

Sign into an Xbox profile.
Launch the title.
Navigate through all menus and sub-menus, review all types of media and/or features, or enter and complete all game modes.
- Games: Navigate, interact and complete all menu UI, extra content, single player modes, and multiplayer modes, including any additional features. Test in offline, online, split-screen, and system link modes, if applicable. Test multiplayer game modes with the maximum number of players whenever possible.
- Apps: Navigate and interact with all different types of media content, including any additional features.

Expected Result
All titles must provide users with a reliable, fair, consistent, and complete Xbox entertainment experience.

Pass Examples

The title can be completed in all modes.

Fail Examples

The title crashes at the end of a given level.
A particular mode cannot be completed if the user has already completed a different mode.

003-03 Options

Test Steps

Sign in to an Xbox profile.
Launch the title.
- Set various options across the test team such that every available value is tested for each option setting.
- This must cover options both within the title and on any system settings that can be observed while the title is running.
Check that all settings and options within the title's menus are correctly reflected in the end-user experience (for example, brightness, contrast, audio volume, difficulty, and so on).
Terminate the title and then ensure that all settings and options persist after re-launching the title.
Have the test team change their option settings in all areas of the title, and verify that these are accurately reflected throughout the title.

Expected Result
All option settings within a title must work as expected and options and settings values must persist after re-launching the title.

Pass Examples

With the in-game language option set to Dutch, the title uses only Dutch subtitles.

Fail Examples

If the user inverts the horizontal or vertical camera controls with the pause menu, the camera controls do not change in-game.
Any options values set during gameplay are reset to default after terminating and re-launching the title.

003-04 Language Support

Test Steps

Sign in to an Xbox profile.
Launch the title.
Navigate to the console's language settings and set the language to match that of the console locale being used.
Taking each in turn, ensure that the title boots correctly and exhibits the correct localization for each supported language in the title.
Ensure that all game-critical text that is essential for progression within the title is legible.

Expected Result
Titles must boot correctly in all language settings, and they must exhibit the correct localization for all supported languages in-game. In areas where text for supported languages is displayed, the text must remain legible regardless of the display setup.

Pass Examples

All localization displays correctly in all languages.
Launching the title with the console set to an unsupported language results in only English text being displayed.

Fail Examples

German localization is shown as French.
Significant localization issues are found when the console is set to German.
Launching the title with the console set to an unsupported language results in no text or null characters being displayed.

Test Steps

Sign in to an Xbox profile.
Launch the title.
Navigate through all menu and option screens (front-end, in-game, and other areas) with the controller, ensuring that all the navigation buttons function as expected.
- If button labels or command prompts are displayed within any menu UI, verify that each command can be issued correctly.
Repeat Step 3 with natural user interface (NUI), if supported and the sensor is connected and enabled.
Repeat Step 3 with voice user interface (VUI), if supported and the sensor is connected and enabled.
- If additional VUI commands other than the default commands are available for use, verify that all VUI commands are accurate in all supported languages.

Expected Result
Navigation commands must function as expected.

Pass Examples

All areas of the title can be navigated as expected.

Fail Examples

When entering certain menus, the title displays imagery associated with a button on the controller that has no action when pressed.

003-07 Leaderboards

Test Steps

Sign in to an Xbox profile.
Launch the title.
Console A and B: Sign in to profiles that are friends with each other.
Console A: Navigate to an area of the title where leaderboard posting is possible (only if leaderboards are supported by the title).
- Testers must check both in-game leaderboards and leaderboards displayed in the system.
Meeting the minimum requirements necessary, perform all steps in order to post to a leaderboard.
Console A: Once the scores have been posted, verify that the statistics are posted to the leaderboards correctly and that the statistics can be sorted using the filters provided.
Console B: Navigate to the leaderboards menu and verify that the statistics for Console A are correctly posted to the leaderboards and that the statistics can be sorted using the filters provided.
Repeat Steps 2-7 for all game modes.
Consoles A and B: Where competitive co-op gameplay across Xbox is possible, repeat Steps 2-7 for each game mode.
Where single-console multiplayer split-screen gameplay across more than one Xbox profile is possible, ensure that one of the following occurs:
- Users are able to post to each leaderboard.
- At least the lead profile is able to post a score to each leaderboard.
- Where the title indicates that both users are able to post a score to the leaderboards, scores are correctly registered for each of the participants.

Expected Result
Titles must allow a user to post statistics to all available leaderboards and sort those leaderboards using the filters provided.

Pass Examples

All leaderboards can be posted to successfully.

Fail Examples

The title stops responding while navigating from leaderboard A to leaderboard B.
Users cannot post to specific leaderboards.

003-08 Low or High Friend Count

Test Steps

Sign in to an Xbox profile.
Sign in using a profile that has 100 friends.
Launch the title.
Perform the following actions where applicable:
- View all available leaderboards and use all filter options.
- View a friend's gamercard.
- View a friend's rich-presence information.
- Invite a friend to a game session and play until completion.
Repeat Step 4 using an account that has zero friends (if supported, use a "Recent Players" list to verify Steps 4).
Repeat Step 4 using a profile that has more than 100 friends.
Report any instance of negative behavior.

Expected Result
Title functionality should not be adversely affected by the number of friends a profile contains in its friends list.

Pass Examples

Both minimum and maximum friend counts have no negative impact on the title.

Fail Examples

When using an Xbox enabled profile that has zero friends, if the user enters the leaderboards and views the "Friends Only" filter, a message similar to "Error. Not connected to Xbox." is incorrectly displayed.
Any attempt to view a friend's leaderboard results in a blank page. Toggling the filter away from "Friends" then displays an error message similar to: "Failed to read Leaderboard stats".
When using a gamer profile with over 100 friends and creating a private match, the title does not provide access to the user's friends list when entering a multiplayer mode.

003-14 Local Multiple Players

Test Steps

Establish the maximum number of users per console that the title supports.
Consoles A and B: Connect the relevant number of controllers for the maximum number of users per console.
Sign in to Xbox profiles.
Launch the title.
Console A: Create an Xbox multiplayer game session with enough slots to allow the maximum number of users on both consoles to join.
Console B: Find the multiplayer game session hosted by console A.
Verify that all users are able to join the multiplayer game session.
Console A: Launch the game session and verify the following:
- All users can enter gameplay.
- There is no slowdown.
- There are no graphical issues.
- There are no sound issues.
- There is no negative gameplay experience.
- All users are able to complete the game session.

Expected Result
Title must allow the maximum number of users per console to play in all Xbox supported game modes without error.

Pass Examples

With two players on a single console, there is no negative impact to the frame rate.

Fail Examples

The Xbox game session displays graphical and audio slowdown when any of the participating consoles reaches the maximum number of players.

003-16 Save-Game Compatibility

Test Steps

Sign in to an Xbox profile.
Launch the base title without a connection to the Xbox network.
Enter gameplay and proceed far enough to save game progress in each mode (such as game progress, options and settings, avatar creation, and so on).
Reboot the title and verify that you can load and resume the game-save progress from Step 3.
Connect to Xbox services and download the content update for the base title.
With the content update applied, verify that you can still load and resume the game-save progress made in Step 3.
Reboot the title, start a new game, and proceed far enough to save game progress again.
Exit and uninstall the title.
Launch the base title without a connection to the Xbox network.
Verify that one of the following occurs:
- You can load and resume the game-save progress without error.
- The title displays a message indicating that game-save progress cannot be used without a content update from the Xbox network.
- The title does not display the game save made in 6.
Reboot the title and connect to the Xbox network to receive the content update.
With the content update applied, verify that you can still load and resume the game-save progress.

Expected Result
A content-updated version of a title must be able to successfully load a game save created using the non-content-updated version of the title.

Pass Examples

All saves can be loaded successfully by a content-updated version of a title.
When launching the base version to load an updated save, the user is notified of missing content and given a reason why the save file could not be loaded, or the saves made in the content-updated version are not visible in the base version.

Fail Examples

The content-updated version of the title is unable to load a game save that was made during Step 3.
The base version of the title crashes when loading a save made with the content-updated version of the title.

003-17 Headset State Change

Test Steps

Enable Windows Sonic for Headphones as your Headset format under Xbox Audio Settings.
Attach a pair of headphones to the controller or attach a pair of headphones wirelessly to the Xbox.
Boot the title and progress into gameplay.
Verify audio is heard through TV and headphones.
Unplug headphones, verify audio returns after a short amount of time.
Re-plug headphones, verify audio is heard through TV and Headphones.
Repeat steps 5-6 throughout the title.

Expected Result
Audio continues to be heard without issue.

Pass Examples

Audio returns without issue whenever the headset is removed.
Audio returns without issue when headset is connected.

Fail Examples

Audio is no longer heard after the headset state changes.
Audio is distorted or corrupt after the headset state changes.

Note

For reference: Comparison of Xbox One Software Development Kit and Microsoft Game Development Kit Audio API

003-18 Headset State Change after Suspend

Test Steps

Enable Windows Sonic for Headphones as your Headset format under Xbox Audio Settings.
Attach a pair of headphones to the controller or attach a pair of headphones wirelessly to the Xbox.
Boot the title and progress into gameplay.
Verify audio is heard through TV and headphones.
Suspend the title naturally.
Unplug the headphones.
Resume the title and verify audio is heard through TV.
Re-plug the headphones and verify audio is heard through TV and Headphones.
Repeat steps 5-8 throughout the title.

Expected Result
Audio continues to be heard without issue.

Pass Examples

Audio returns without issue whenever the headset is removed.
Audio returns without issue when the headset is connected.

Fail Examples

Audio is no longer heard after the headset state changes.
Audio is distorted or corrupt after the headset state changes.

Note

For reference: Comparison of Xbox One Software Development Kit and Microsoft Game Development Kit Audio API

003-19 Headset State Change after Connected Standby

Configuration:
One console with the following configuration:

Instant sign-in enabled in Settings -> Account -> Sign-in, security & passkey -> Instant sign-in -> Use Instant sign-in.
Standby set in Settings -> General -> Sleep mode & startup -> Standby.

Test Steps

Sign into an Xbox profile with the console set as a user's home console and with a license to the title.
Enable Windows Sonic for Headphones as your Headset format under Xbox Audio Settings.
Attach a pair of headphones to the controller or attach a pair of headphones wirelessly to the Xbox.
Boot the title and progress into gameplay.
Verify audio is heard through TV and headphones.
Put the console into Connected Standby.
Unplug headphones.
Turn the console back on and resume the game.
Verify audio is heard through TV.
Re-plug headphones, verify audio is heard through TV and Headphones.
Repeat steps 4-11 throughout the title.

Expected Result
Audio continues to be heard without issue.

Pass Examples

Audio returns without issue whenever the headset is removed.
Audio returns without issue when the headset is connected.

Fail Examples

Audio is no longer heard after the headset state changes.
Audio is distorted or corrupt after the headset state changes.

Note

For reference: Comparison of Xbox One Software Development Kit and Microsoft Game Development Kit Audio API

XR-130: Xbox Console Families and Generations *

All game titles targeting a console generation must support the entire family of devices for that generation.

Xbox One games not using Smart Delivery function by default on Xbox Series X|S in compatibility mode. Games using Smart Delivery must work properly when running in compatibility mode on Xbox Series X|S.

To maintain consistency across console generations, games must:

Support navigation via gamepad input. Titles may require additional peripherals for use with prior approval.
Ensure that saved games work across console types within the generation.
Ensure that online players are not segmented based on console type within the generation.
Ensure that identical game modes are offered across console types within the generation.
Between generations (Xbox One and Xbox Series X|S), games which share the same TitleID must:
- Support game save roaming for content available on both generations (XR-052: User State and Title-Save Location, Roaming and Dependencies).
- Though not required, it is recommended that scenarios in which multiplayer, cooperative or competitive, experiences are supported offer at least one shared matchmaking hopper and allow for cross generation invite/join for shared content experiences.

130-01 Controller Input

Tools Needed

1 Xbox One
1 Xbox One S
1 Xbox One X
1 Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)

Test Steps

Sign into an Xbox profile.
Launch the title.
Navigate all areas of the title and verify the title accepts navigation via controller input in each area.
Repeat all steps above across all generations of devices.

Expected Result
The title supports navigation via a controller in all areas of the title and doesn't feature compulsory scenarios for other input devices, such as a keyboard/mouse. Titles may require additional peripherals for use with prior approval.

Pass Examples

The title accepts input from a controller in all areas of the title.

Fail Examples

The title accepts input from only a keyboard and/or mouse in certain areas of the title.

130-02 Save Game Roaming

Tools Needed

1 Xbox One
1 Xbox One S
1 Xbox One X
1 Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)

Test Steps

Sign into an Xbox profile on device A and launch the title.
Begin gameplay and make save progress (if possible, create a settings save by changing or adding a new setting configuration).
Exit the title.
Sign in on a different device from the same generation with the same profile used in Step 1.
Launch the same title from Step 1 and verify that all saved games and any settings and/or configuration files can be accessed and loaded correctly and they don't have any dependencies on a specific same generation device.
Repeat all steps above across the same generation of devices.
For games which share the same TitleID across generations (Xbox One and Xbox Series X), repeat steps 1-4 for content available on both generations.

Expected Result
Save games must work in their entirety across the same generation and save games must work in their entirety for games that share the same TitleID across generations (Xbox One and Xbox Series X) for content available on both generations.

Pass Examples

A game save made on an Xbox One S works on an Xbox One and Xbox One X, and vice versa across the whole family of Xbox One devices.
A game save must work for games that share the same TitleID across generations (Xbox One and Xbox Series X) for content available on both generations.

Fail Examples

A game save made in one generation (Xbox One or Xbox Series X) does not fully load across all device types in that generation.
A game save does not fully load for games that share the same TitleID across generations (Xbox One and Xbox Series X) for content available on both generations.

130-03 Online Segmentation

Tools Needed

1 Xbox One
1 Xbox One S
1 Xbox One X
1 Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)

Test Steps

Sign into an Xbox profile and launch the title on all device types in the same generation.
Complete an Xbox network multiplayer game session featuring all devices.
Repeat step 2 across all Xbox network multiplayer modes supported by the title.

Expected Result
Xbox network players must be able to join other Xbox network players irrespective of which console type is being used from the same generation.

Pass Examples

All consoles from the same generation of devices are able play against each other in multiplayer gameplay.

Fail Examples

Xbox network players are segmented within the same generation based on their Xbox One console type.

130-04 Featured Game Modes

Tools Needed

1 Xbox One
1 Xbox One S
1 Xbox One X
1 Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)

Test Steps

Sign into an Xbox profile and launch the title.
Locate an access all featured game modes.
Repeat all steps above across the same generation of devices and ensure all game modes are identical on each device.

Expected Result
Identical game modes must be offered across the same generation of devices.

Pass Examples

All consoles from the same generation of devices provide the same set of identical game modes.

Fail Examples

One or more consoles from same generation of devices provides different game modes based on their same generation console type.

130-05 Compatibility Mode

Tools Needed

1 Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)

Test Steps

For Xbox One titles, sign into an Xbox profile and launch the title.
Play through the title and ensure that the title performs as expected in compatibility mode.
Look to identify any areas where game performance, visuals, or audio is noticeably inferior between Xbox Series X to Xbox One X.
- Check all different resolution outputs for performance issues.
- Check Auto HDR with an HDR compatible screen.
Repeat Step 3 but this time look to identify any areas where game performance, visuals, or audio is noticeably inferior on the Xbox Series S to Xbox One S.
Ensure multiplayer fidelity between Xbox Series X|S devices and also between Xbox One and Xbox Series X|S devices (where supported).
- Check matchmaking.
- Check invites in both directions.
- Check joining via the shell in both directions.
Ensure entering and returning from a suspend state works as expected.
Ensure all game saves persist after a reboot of the console.
Ensure roaming saves between Xbox One (any part of the family) to Xbox Series X|S (any part of the family) and back again functions.

Expected Result
Xbox One games not supporting Smart Delivery must run without functional or performance issues on Xbox Series X|S.

Pass Examples

The title has no performance issues when running on Xbox Series X|S.
The title has no functional issues when running on Xbox Series X|S.
The title can correctly enter, play, and finish all multiplayer modes when running between Xbox Series consoles, including when playing multiplayer between Xbox One and Xbox Series.
The title correctly supports suspend and resume when running on Xbox Series X|S consoles.
The user's game saves made on Xbox Series X|S consoles persist after a full title reboot.
The user's game save(s) created on Xbox One can be roamed to Xbox Series X|S and all progress is still present. Roaming the same game save(s) back to Xbox One also retains all progress.

Fail Examples

The title has performance issues when running on Xbox Series X|S.
The title has functional issues when running on Xbox Series X|S.
The user cannot enter, play, or finish multiplayer in all modes when running between Xbox Series consoles, or when playing multiplayer between Xbox One and Xbox Series.
The title does not correctly suspend and resume when running on Xbox Series X|S consoles.
The user's game save(s), or part of the game save, made on Xbox Series X|S consoles do not persist after a full title reboot.
The user's game save(s) created on Xbox One cannot be roamed to Xbox Series X|S without progress being lost. Roaming the same game save(s) back to Xbox One also loses some/all progress.

XR-131: Display Mode Support for Game DVR and Screenshots *

Titles must ensure that Game DVR and screenshots work properly across display modes and types. Titles that display in HDR do this by rendering both the SDR and HDR swap chains, because the SDR swap chain is used for SDR screenshots, broadcasting, and Game DVR.

131-01 Game DVR and Screenshots

Tools Needed

1 Xbox One S
1 Xbox One X
1 Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)
1 4k/HDR Display

Test Steps

Sign in to an Xbox One S and Xbox Series S console set to 1080p with an HDR display attached and HDR output configured in the console's settings.
Launch the title.
Disable HDR in the console settings while the title is still running.
Return to the title and validate there are no defects in the displayed graphics.
Repeat steps 1-4 in 4K on an Xbox One X and Xbox Series X.

Expected Result
No graphical defects are displayed when the HDR/4K output is switched to SDR.

Pass Examples

There are no black screens, no black bars and no obvious visual defects.

Fail Examples

The SDR image is significantly lighter or darker than the HDR image.
The SDR image is smaller than the HDR image.
Significant black bars or borders are displayed on the SDR image.

XR-022: Official Naming Standards *

Titles must use the naming standards defined in the latest release of the terminology list for Xbox console and/or Xbox network features.

On Xbox consoles, titles must not display images or refer to components of the console system or components of peripherals using terms that are not specifically included in the terminology list.

022-01 Official Naming Standards

Test Steps

Launch the title.
Visit all areas of the title.
Navigate all menus and sub-menus.
Change all available settings and options.
If the title supports saves, save and load all possible game types.
Watch all cinematics.
Note all text and images shown.

Expected Result
All text adheres to the most recent terminology list. Images must not display components of the console system or components of peripherals using terms that are not specifically included in the terminology list.

Pass Examples
None

Fail Examples

The title uses a proprietary term or image from a competitive platform.
A title refers to a component of the console system or component of a peripheral using any term that is not included in the terminology list.

XR-074: Loss of Connectivity to Xbox and Partner Services *

Titles must gracefully handle errors with Xbox and partner services connectivity. Titles must honor the retry policies set by Xbox when attempting to retry a request to the Xbox service after a failure has occurred. Titles must appropriately manage messaging the user when services are unavailable. If a partner service is not available, the game must not indicate that there is an issue with the Xbox network. Titles must not crash or hang if network services are slowed or intermittently available.

074-01 WAN Disconnection to Xbox Services

Test Steps

Sign in to an Xbox profile.
While performing the following actions, disconnect the WAN network (If using an Ethernet switch/hub disconnect the uplink cable from the network device. If the device is connected via Wifi, disconnect the uplink cable from the wireless access point) connection:
- Creating a new save point.
- Loading a save point.
- Reaching an auto-save point.
- Enumerating a list of saved games.
- Searching for and joining an online session.
- Attempting to create an online session.
- Viewing a leaderboard (if applicable).
- Playing offline.

Expected Result
In the event that the console is unable to reach Xbox services, the title should respond with a user-friendly error message.

Pass Examples

Title displays error message indicating loss of network connection to Xbox services.
Title does not display an error message while playing a local game mode that does not require Xbox services.
A title with RequireXboxLive in AppX manifest suspends and then terminates when connectivity is lost.

Fail Examples

User is unable to complete a non-online Xbox game session.
Title goes into an unresponsive or unstable state.

074-02 Direct Disconnection

Test Steps

Sign in to an Xbox profile.
Launch the title.
While performing the following actions in the title, pull network cable from the device, or power off the WAP or wireless router:
- Creating a new save point.
- Loading a save point.
- Reaching an auto-save point.
- Enumerating a list of saved games.
- Searching for and joining an online session.
- Attempting to create an online session.
- Viewing a leaderboard (if applicable).
- Playing offline.

Expected Result
In the event the device loses connection to Xbox services, the title should respond with a user-friendly error message.

Pass Examples

The title displays a user-friendly message while in online game mode.
The title does not interrupt gameplay during offline game mode.
A title with RequireXboxLive in AppX manifest suspends and then terminates when connectivity is lost.

Fail Examples

An error message is displayed during offline game mode.
The user is able to view online menus or view buffered media after the network goes offline.

074-03 Suspend Disconnection to Xbox Services

Configuration
This test case only applies to consoles. Install the title and use xbapp list from the GDK to return the package full name (PFN) for the title.

Test Steps

Sign in to an Xbox profile and launch the title.
While on the main menu or front-end menu:
- Suspend the title by running xbapp suspend [PFN], or wait 30 seconds for the title to fully suspend naturally and for the suspension to interrupt any HTTP request.
- Resume the title.
Repeat Steps 2-4 from the following areas if supported:
- During a single-player game session.
- During an online multiplayer session.
- While in a pre-game multiplayer lobby.
- While viewing an online leaderboard.
- During video or audio playback.

Expected Result
In the event that the console is unable to reach Xbox services after being suspended, the title must reactivate successfully, handle the situation gracefully, and respond with a user-friendly error message where appropriate.

Pass Examples

During an online Xbox multiplayer session, the title displays an error message indicating loss of network connection to Xbox services.
The title does not display an error message while playing a local game mode that does not require Xbox services.

Fail Examples

The user is unable to complete a non-online Xbox game session.
The title goes into an unresponsive or unstable state.
The title displays a misleading or incorrect error message after resuming.

074-04 Xbox Service Re-connection During Suspend

Configuration
This test case only applies to consoles. Install the title and use xbapp list from the GDK to return the package full name (PFN) for the title.

Test Steps

Sign into an Xbox profile and ensure the console is set to Home.
With no connection to the Xbox network but retaining a local network connection, launch the title.
While on the main menu or front-end menu:
- Suspend the title by running xbapp suspend [PFN], or wait 30 seconds for the title to suspend naturally and for the suspension to interrupt any HTTP request.
Wait at least 30+ seconds for the title to fully suspend and for the suspension to interrupt any HTTP request.
Reconnect the uplink cable and wait for the console to reconnect to the Xbox network.
Resume the title.
Repeat Steps 2-6 from the following additional areas if supported:
- During a single-player game session.
- Within a save/load menu before saving/loading a game.

Pass Examples

The user is able to resume the title and complete an offline Xbox game session without interruption.
The title remains stable and does not crash.

Fail Examples

The user is unable to complete a non-online Xbox game session.
The title goes into an unresponsive or unstable state.
The title displays a misleading or incorrect error message after resuming.

074-05 Constant Low Bandwidth

Tools Needed:
xbstress.exe from the GDK/XDK.

Configuration
Network simulation is controlled by the command-line stress tool xbstress.exe. This tool configures various console stressors, including network simulation. For networking purposes xbstress.exe controls a specialized driver on the Xbox device, which drops packets, injects latency, and limits throughput. xbstress.exe has three pre-configured simulation profiles that allow you to easily simulate important networking scenarios: minimum, average, and excellent. The minimum profile maps to this XR.

Test Steps

Using XBStress minimum profile, throttle connectivity to Xbox device's minimum operating requirements.
Perform title-related online actions, including but not limited to:
- Navigating all menus.
- Playing an online game session.

Expected Result
Titles must not crash or cause user data loss when user's internet connection drops below 192 Kbps.

Pass Examples

User-friendly message is displayed indicating possible impact to online play due to low bandwidth.
Title does not crash and does not cause a loss of user data.

Fail Examples

Title crashes or causes user data loss.

074-06 Variable Low Bandwidth

Tools Needed
xbstress.exe from the GDK/XDK.

Test Steps

Disable all network restrictions in xbstress.
Perform title-related online actions, including but not limited to:
- Navigating all menus.
- Playing an online game session.
While performing Step 2, enable xbstress' minimum profile.

Expected Result
Titles must not crash or cause user data loss when user's internet connection drops below 192 Kbps.

Pass Examples

User-friendly message is displayed indicating possible impact to online play due to low bandwidth.
Title does not crash and does not cause a loss of user data.

Fail Examples

Title crashes or causes user data loss.

074-07 Dynamic Connectivity Loss

Tools Needed

For console, xbstress.exe from the GDK/XDK.
For Windows 10, Fiddler Classic.

Configuration:
For Xbox devices, network simulation is controlled by the command-line stress tool xbstress.exe. xbstress.exe allows the user to block a list of domain names and IPs, this test is performed with a provided list of addresses to block non-Microsoft traffic.

Test Steps

Sign in to an Xbox profile.
Launch the title.
Access non-Microsoft online feature.
If testing on Xbox consoles, create a broken network channel with xbstress for non-Microsoft traffic using the command: xbstress set channel=0 network=broken addresses=[semicolon delimited list of addresses]
Start the network simulation with xbstress simulate network=channels.
If testing on Windows 10, use fiddler to emulate downtime.

Expected Result
Title should gracefully handle disconnections to non-Microsoft service.

Pass Examples

Title does not hang or crash upon loss of connectivity to the partner-hosted service.

Fail Examples

Error displayed implies issues with Microsoft service.
Non-descriptive error message is displayed.
Title crashes, becomes unstable, or causes console reboot.

074-08 Pre-Launch Downtime

Tools Needed

For console, xbstress.exe from the GDK/XDK.
For Windows 10, Fiddler Classic.

Configuration:
For consoles network simulation can be set by the command-line stress tool _xbstress.exe. xbstress.exe allows the user to block a list of domain names and IPs. This test is performed with a provided list of addresses to block non-Microsoft traffic.

Test Steps

If testing on Xbox devices, create a broken network channel with xbstress for non-Microsoft traffic using the command: xbstress set channel=0 network=broken addresses=[semicolon delimited list of addresses].
Start the network simulation with xbstress simulate network=channels.
If testing on Windows 10, use fiddler to emulate downtime.
Sign in to an Xbox profile.
Launch the title.
Access non-Microsoft online feature.

Expected Result Titles should provide a user-friendly error message indicating that there is a problem reaching the non-Microsoft service and should allow an opportunity to retry connection.

Pass Examples

Title does not hang or crash upon loss of connectivity to the partner-hosted service.

Fail Examples

Error displayed implies issues with Microsoft service.
Non-descriptive error message is displayed.
Title crashes, becomes unstable, or causes console reboot.

XR-132: Service Access Limitations *

Titles which exceed title and user based limitswhen calling Xbox network services or do not adhere to Xbox network service retry policies may be subjected to rate limiting, which may result in service interruption or deprecation. Failure to adhere to the specified limits may block a title from release, and in-production issues with released titles may result in Xbox network services suspension up to and including title removal.

132-01 Service Access Limitations

Tools Needed

For Windows 10, Xbox Series X|S or any GDK-based titles, Fiddler Classic.
For Xbox consoles, Fiddler Classic or XblTraceAnalyzer.exe (from the GDK)
Xbox services Trace Analyzer to parse the output files from XblTraceAnalyzer.exe and/or Fiddler

Test Steps

Using Fiddler Classic

Prior to launching the title, start Fiddler Classic and ensure it is configured to capture network traffic from the console or Windows 10 PC (wherever the title in question is running from).
With Fiddler Classic running and capturing network traffic, launch the title and proceed to move through all areas, including, but not limited to, the following:
- Create a game save, reboot the console and load the game save
- Change rich presence states in quick succession (if possible)
- Unlock and view achievements
- Post to all leaderboards and view all leaderboards using all filters
- View in-game Friends List (including a friend with presence blocked) and move between pages rapidly
- Earn and view a Hero Stat
- Match-make into all online modes, including being unable to find an available session (if possible) and generate voice traffic
- Create, save and share a game clip
- Access the in-game store (if applicable)
Once testing has concluded, save the Fiddler capture to a local directory.
In the GDK command prompt, run xbltraceAnalyzer -data filepath -outputdir filepath.
Open the output directory from step 4 and open the 'index' file (select 'Allow blocked content' if prompted).

Using xbtrace.exe
xbtrace.exe cannot start until the title is launched, but it should be started as quickly as possible in order to capture any Xbox service calls the title makes during start up. Due to this, the preferred method for capturing title traffic is Fiddler Classic as it can be started prior to launching the title.

With the title running, run xbtrace start xboxliveservices and proceed to move through all areas of the title, including, but not limited to, the following:
- Create a game save, reboot the console and load the game save
- Change rich presence states in quick succession (if possible)
- Unlock and view achievements
- Post to all leaderboards and view all leaderboards using all filters
- View in-game Friends List (including a friend with presence blocked) and move between pages rapidly
- Earn and view a Hero Stat
- Match-make into all online modes, including being unable to find an available session (if possible) and generate voice traffic
- Create, save and share a game clip
- Access the in-game store (if applicable)
Once test has concluded, run xbtrace stop twice.
Browse your console's files and in SystemScratch > xbtrace you will find the csv. Check the time stamp to make sure it registers the time you stopped recording. Copy it locally.
In the XDK command prompt, run Xbltraceanalyzer -data filepath -outputdir filepath.
Open the output directory from step 4 and open the 'index' file (select 'Allow blocked content' if prompted).

Expected Result
Games must not display any serious warnings in their Trace Analyzer output results. Titles must ensure they keep their service calls to Xbox endpoints below the specified burst and sustain limits.

Pass Examples

The title does not exceed the sustain limit when calling Xbox services.

Fail Examples

The title exceeds the sustain limit (limit at which rate limiting takes effect) by 10x. For example, if the sustained limit at which Fine Grain Rate Limiting takes effect is set to 300 calls in 300 seconds, titles at or above 3000 calls in 300 seconds will fail.

132-02 Game Event Limitations

Test Steps

Install the title and with the title running, proceed to navigate through all areas of the title, including, but not limited to, the following:
- Create a game save, reboot the console and load the game save
- Change rich presence states in quick succession (if possible)
- Unlock and view achievements
- Post to all leaderboards and view all leaderboards using all filters
- View in-game Friends List (including a friend with presence blocked) and move between pages rapidly
- Earn and view a Hero Stat
- Match-make into all online modes, including being unable to find an available session (if possible) and generate voice traffic
- Create, save and share a game clip
- Access the in-game store (if applicable)
During test, observe the title to see if the Game Event Limitations system toast appears.

Expected Result
Games must not trigger the Game Event Limitations system toast.

Pass Examples

The title does not trigger the Game Event Limitations system toast.

Fail Examples

The title triggers the Game Event Limitations system toast.

XR-133: Local Storage Write Limitations *

Titles which use local storage must not exceed 1 GiB of total writes to persistent local storage or temporary storage in a 5 minute increment of time.

For more information on local storage on Xbox consoles with the GDK, read the Local Storage section

133-01 Local Storage Write Limitations

Test Steps

Install the title and with the title running, proceed to navigate through all areas of the title, including, but not limited to, the following:
- Create a game save, reboot the console and load the game save
- Play all game modes and unlock/view achievements
During test, observe the title to see if the Local Storage Write Limitations system toast appears.

Expected Result
Games must not trigger the Local Storage Write Limitations system toast.

Pass Examples

The title does not trigger the Local Storage Write Limitations system toast.

Fail Examples

The title triggers the Local Storage Write Limitations system toast.

Online Safety and Privacy

The requirements in this category pertain to protecting the safety and privacy of users.

XR-013: Linking Microsoft Accounts with Publisher Accounts *

On Xbox, titles that use partner-hosted services or accounts that require credentials must support all Xbox users and offer to link that account with the user's Microsoft account. Outside of Xbox consoles, titles can choose to allow account linking to support their game experience.

If publisher account sign in is enabled within the title, the following rules apply:

Publisher Account Sign In

Accommodate All Users
If a publisher account sign in is required for game features (single player, multiplayer, cross network gameplay, leader boards), sign in and sign up must support all user types, ages, and regions where the game title is offered and where those features are allowed by local/regional laws irrespective of age rating.
- A game publisher may choose not to support a particular region, age, etc. for their publisher account. If a region, age group, or other group of players cannot create or sign into an account the title cannot require those users to sign in with an account for game features.
- If a particular account setting is not supported in a title-based sign-up experience (e.g., age or region) the title must gracefully handle by providing messaging to sign up on an external site or mobile optimized experience where that user is supported.
Gain Consent and Provide Terms for Account Information Usage
Titles must request to use and gain consent to use information from the player's Microsoft account to auto populate sign up/account creation experiences. Users must be provided with all applicable terms of use, privacy and other policies within the title (or a notice with a link to such information) during a publisher account creation process.
Disclose Requirements
If a publisher account is required for gameplay or additional features, it must be disclosed in the title's product description and any physical packaging including any restrictions such as age. In title, the game must define the reason and use of the publisher account. If a publisher account limits or restricts the experience for child accounts, it is suggested to add this text to the store details page for buyer awareness:

Certain features of the game, including online multiplayer, communication and other online features, may not be accessible by Xbox child accounts. At Xbox, a child means players under the age of 13, unless local laws specify differently.

Publisher Account/Microsoft Account Linking

Authentication using the Xbox Secure Token Service (XSTS)
XSTS tokens must be used to provide identity information for authentication when linking the user's publisher account to the user's Microsoft account. For more information about XSTS token authentication see Xbox services authentication for title servicesOtorisasi diperlukan.
Gain Consent and Provide Choice
Users must be notified of the account linking of the user's publisher account to the user's Microsoft account. The user must be given the choice to opt-out if linking their accounts. Users must have the ability to de-link accounts.
Accommodate All Users
If a publisher account sign in is required for game features (Single player, multiplayer, cross network gameplay, leader boards), sign in and sign up must support all user types, ages, and regions where the game title is offered and where those features are allowed by local/regional laws irrespective of age rating.

Note

Publishers may implement additional fraud prevention mechanisms such as two-factor authentication interrupts when a linked account signs in from a new device for the first time. This behavior is not a violation of this XR.

013-01 Linking Microsoft Accounts with Publisher Accounts

Test Steps

Verify the title supports or requires non-Xbox accounts or login for services or functionality.
Using a newly created Xbox profile, use the publisher provided service account or login to enter non-Xbox account credentials during initial setup.
Verify the title allows the user to view the terms of use in the app or informs the user how to view the terms of use, prior to completing the account linking process.
Verify that the user is not prompted to re-enter their non-Xbox account credentials in any location.
Sign out and sign back in while the title is running.
Repeat Step [4].
Terminate and reactivate the title using the same profile.
Repeat Step [4].
Terminate the title.
Verify that the title does not store non-Xbox account credentials locally by deleting any saved files that may have been created by the title.
Reactivate the title and repeat Step [4].
On a different console, launch the title using the same profile and repeat Step [4].
Verify the user can unlink their Xbox profile from the non-Xbox account.
Repeat steps [1]-[13] with an Xbox child account (under the age of 13) that falls within the games' age rating.

Expected Result
Titles must allow publisher accounts to be created for all users who fall within the games' age rating. The user should only have to provide their credentials once and allows the user to view the terms of use, or informs the user how to view the terms of use, prior to completing the account linking process. Users are provided with a mechanism to unlink their Xbox profile from their non-Xbox account.

Pass Examples

The title never asks the user to re-enter their non-Xbox account or login credentials at any point after they have initially entered them and the title provides a notification of the terms of use both during the linking process and for as long as the accounts are linked.
The title allows publisher accounts to be created for all users who fall within the games' age rating.

Fail Examples

The title requires the user to enter their non-Xbox account or login credentials every time the title is launched.
The title requires the user to enter their non-Xbox account or login credentials when running the title from another console.
The title does not provide a method for viewing the terms of use during the account linking process.
The title does not provide a method for unlinking their Xbox profile from their non-Xbox account.
The title does not allow publisher accounts to be created for all users who fall within the games' age rating.

XR-014: Player Data and Personal Information *

Game publishers are solely responsible for collecting and processing end user data in accordance with applicable law especially when the user is a child.

Additionally, when a title has information about a player either acquired from Xbox or from their relationship with the player directly (such as a website or mobile app), titles must not display to other players:

Information that could be used to cause financial damage to a user (such as Social Security or credit card numbers).
Information that divulges a user's address beyond country/region.
Information that would allow a user to impersonate another user online, such as account credentials.

Handling Child Data
When collecting data from accounts in the Child or Teen Age Group, titles may only request personal data necessary to verify age or obtain parental consent.

Definitions
Address is any information that can identify a user's location to the level of city or town. This includes, but is not limited to, the following:

Physical address
Mailing address
Billing address
ZIP code
IP address or related information
Geographical location information

014-01 Personal Information

Test Steps

Visit all areas of the title, including all possible Xbox multiplayer sessions.
Visit all areas where content might be saved or otherwise sent across the Xbox network, or to a title server.

Expected Result
Titles must never display personal information about another user as detailed in the body of the XR.

Pass Examples

The title displays and shares country of residence information with a user on another console.
The title uses the user's IP address to define the user's general location (no more specific than state or country/region) and displays that location to other users on the leaderboards.

Fail Examples

The title transmits and shares a user's personal information with users on other consoles. Examples: Email address, location (anything more specific than state/country/region), name, date of birth, profile passcode, secret question, password(s), credit card details.

014-02 Data Collection

Test Steps

Launch the title using a Child or Teen account.
Visit all areas of the title, including all possible single and Xbox multiplayer game modes.
Check to see what data is being requested from the user.

Expected Result
Titles must not request data from a Child or Teen user beyond what is needed for age verification or to acquire parental consent (such as an email address for the parent).

Pass Examples

The title does not request any data from the Child or Teen user.
The title requests the birth date of the user and states that this is needed to verify age.
The title requests an email address for a parent so they can provide parental consent.

Fail Examples

The title asks for data that could be used for purposes other than verifying age or acquiring consent from a parent.
The title does not state what the requested data is needed for, such as asking for a parent’s email address but not saying why.

XR-015: Managing Player Communication *

Titles must not transmit user data or allow communication over Xbox when the user's privacy settings do not allow it.

Titles meet this XR by retrieving data from Xbox services. If the title uses its own services, it must check the user's privacy permissions at the beginning of a session or when a new user joins the session. For user-initiated scenarios outside of sessions, titles meet this requirement by checking privacy prior to displaying the user's data and before performing the action. The following list of privacy settings is available for titles to check:

Permission name	Description
CommunicateUsingText	Check whether or not the user can send a message with text content to the target user.
CommunicateUsingVoice	Check whether or not the user can communicate using voice with the target user.

During the gameplay session, titles which offer communication between Xbox and non-Xbox players must offer the ability to mute any non-Xbox players for the duration of the session.

015-01 User Communication

Configuration:

Create a set of profiles with "Others can communicate with voice, text or invites" to Everyone, Friends and Blocked.
For titles that support communication outside of Xbox, create a set of profiles with "You can communicate outside of Xbox with voice & text" to Allow, In-game friends and Blocked.

Note

The difference between the "Allow" and "In-game friends" friends options are that "Allow" means you can talk to everyone cross network (including players you meet in random matchmaking). "In-game friends" are people you've explicitly chosen to play with by adding them to an in-game friends list.

Test Steps

On Device 1, sign in to a profile that has been configured with the specific set of permissions per the Configuration.
On Device 2, sign in to a profile that has no communication restrictions.
On both devices, launch the title and attempt to communicate using text, voice (both via Kinect and via the headset), and video in every location supported and attempt to send multiplayer game invites.
Repeat Steps 1-3 for all profiles from the Configuration step.

Expected Result
Titles must check the Xbox service for a user's permissions regarding privacy and online safety-related actions and must not transmit user data or allow communication over Xbox when the user's privacy & online safety settings do not allow it.

Pass Examples

The title prevents the user from communicating via voice and text over Xbox when that specific method of communication is configured to be blocked.
The title prevents the user from communicating via voice and text outside of Xbox when that specific method of communication is configured to be blocked.
The title prevents the user from receiving multiplayer game invites on Xbox when that is blocked.

Fail Examples

The user is able to communicate via voice and text over Xbox when that specific method of communication is configured to be blocked.
The user is able to communicate via voice and text outside of Xbox when that specific method of communication is configured to be blocked.
The title allows the user to receive multiplayer game invites on Xbox when that is blocked.

015-02 Muting Support

Test Steps

As user A, mute user B.
Have both users join an Xbox multiplayer session.
Attempt to send voice communication from user B to user A.
Ensure that user A is unable to receive any voice communication from user B.

Expected Result
User A must not be able to hear communication from user B.

Pass Examples

Voice communication from the muted user cannot be heard by the user who initiated the mute.

Fail Examples

Voice communication from the muted user can be heard by the user who initiated the mute.

015-03 Blocked Users

Test Steps

As user A, block user B.
Have both users join an Xbox multiplayer session.
Attempt to send voice and written communication from user B to user A.
Attempt to send a multiplayer game invite from user B to user A.
Ensure that user A is unable to receive any communication or multiplayer game invites from user B.

Expected Result
User A must not be able to hear or see communication from user B. User A must not receive multiplayer game invites from User B.

Pass Examples

Communication from the blocked user cannot be seen or heard by the user who initiated the block.
Multiplayer game invitations from the blocked user are not received by the user who initiated the block.

Fail Examples

Communication from the blocked user can be seen or heard by the user who initiated the block.
Multiplayer game invitations from the blocked user are received by the user who initiated the block.

XR-017: Title Ratings *

Title Ratings for Xbox

This white paper focuses on two essential concepts as they pertain to content classifications and restrictions on Xbox consoles:

Rating: Specifies the age level for which different types of content are deemed appropriate by different regions' ratings boards.
Parental controls: A profile setting on Xbox consoles that defines the highest rating level of content that a user can play or view within an application.

017-01 Age Rating Validation

Important

For digital only titles or for testing without green discs please instead refer to test case BVT 000-13.

Configuration:

The title must be a disc submission and test discs must be available to run Test Steps #2 and #3.
- Final (Base/Content Update) - Certificates are required for all locales that require a certificate.
- Out of Scope/No Testing required - DLC, in-game content, titles that cannot launch without a connection to Xbox Live services.
The Submission Materials (Certificates)
Title's age ratings as declared in Microsoft Partner Center

Test Steps

Perform a comparison of the ratings values in Microsoft Partner Center against the ratings certificates supplied in the title's submission materials, and vice versa. This is done to make sure that each ratings value has a corresponding certificate and that each certificate is accounted for in Partner Center.
- All ratings values in Partner Center should have a matching certificate. If any do not, this possibly highlights a mistake and must therefore be escalated.
TEST DISCS REQUIRED - Insert the disc media into a dedicated offline console set to RETAIL and install the title, ensuring that the console is not connected to Xbox Live services at any point during test.
For each ratings body supported by the title: set the offline console to one Location/Country governed by that ratings body within the console Settings, sign into an Xbox profile with the corresponding age restriction enabled, and launch the title to verify that:
- The system challenges the user if the profile's age rating value is set lower than the title's age rating certificate.
- The system does not challenge the user and the title boots beyond the first legal/license screen if the profile's age rating value is equal to the title's age rating certificate.

Expected Result
With a console Location matching each of the supported age-rating regions of the title:

The title must challenge the user when launched with a console age rating value that is set lower than the title's age rating certificate value.
The title must boot without challenging the user when launched with an age rating value that is set equal to the title's age rating certificate value.

XR-018: User-Generated Content *

User generated content is content that users contribute to an app or product and can be viewed or accessed by other users in an online state. If your product contains UGC, you must:

Publish and make available to users a product terms of service and/or content guidelines for User Generated Content either in game or on a title's website.
Provide a means for users to report inappropriate or harmful content within the product to the developer for review and removal/disablement if in violation of content guidelines and/or implement a method for proactive detection of inappropriate or harmful UGC (for example, text filtering).
Titles must remove/disable UGC when requested by Microsoft.
Gracefully handle scenarios in which a user does not have access to UGC in game.
Titles integrated with 3rd party mod platforms must integrate with the product's report / complaint API if available and must moderate content if required by respective 3rd party contracts. Titles integrated with 3rd party mod platforms must present a disclaimer, dialog, or visual cue to users if the content is not sourced from the developer.

018-01 Reporting Inappropriate Content and UGC Text-String Verification

Test Steps

Identify any areas of the title where text can be entered between non Xbox friends and is then viewable by users on another device.
Verify the title provides a way to report other users' inappropriate content to the title or Microsoft.
If there is no way to report inappropriate content, in each area, enter a string, sub string, etc. that is in the published list of banned words.
- Enter the banned word directly (i.e. "BannedWord").
- Enter a banned word with another non-banned word separated by a space i.e. ("Good BannedWord").
If the title allows UGC to be created in an offline state, e.g. character names, disconnect the device from the network, enter banned word combinations and reconnect to the network.
Verify that the inappropriate string is not visible to any other user on another device.
Repeat Steps 3-5 in each language supported by the title and using banned words from the matching locale.

Expected Result
The title must provide a way for users to report other users' inappropriate content; or inappropriate language must either be blocked with an error message, or have the offending words replaced/masked with an inoffensive substitute.

Pass Examples

User entered text messaging which is shared real time in game, such as a lobby or in game text overlay, or only between friends is not filtered.
The title provides a way for users to report other users' inappropriate content to the title or Microsoft.
The title prevents posting of inappropriate language and notifies the user of the reason the posting failed.
The title replaces any inappropriate terms with alternative words or characters (such as [BLOCKED] or [!$%and£$]).
Offensive strings are visible to users on the local console but are not transmitted to other non-Xbox friends beyond the local console.

Fail Examples

The title does not provide a way for users to report other users' inappropriate content and allows inappropriate strings to be visible to non-Xbox friends on another console.
The title allows the user to circumvent the title's inappropriate content filter by creating UGC in an offline state.

Content Packages and Updates

The requirements in this category specify how Xbox One game titles must be packaged and how they must interact with add-on content packages.

XR-034: Streaming Install Initial Play Marker *

Titles which include an initial play marker must provide a gameplay experience when launched from the initial play marker.

For more information on Streaming Install or Intelligent Delivery with the GDK, read the Streaming Install and Intelligent Delivery overview.

034-01 Streaming Installation

Test Steps

Sign in to an Xbox profile.
Install the title and launch it after the initial play marker has finished installing.
Attempt to enter all areas of the title before it has finished the full installation.

Expected Result
Initial play marker installation must provide a gameplay experience (such as a tutorial, play of the first level or a quick multiplayer match in one game mode).

Pass Examples

The title provides a gameplay experience when launched from the initial play marker (such as a tutorial, play of the first level or a quick multiplayer match in one game mode).

Fail Examples

After the initial play marker is installed, the title does not provide a gameplay experience. Failing experiences include:
- Just showing a progress bar
- Playing videos and/or a sequence of images
- Only providing access to the Main Menu
- Any other non-interactive experience

XR-129: Intelligent Delivery Content Management *

Titles that support intelligent delivery must handle scenarios gracefully when content that is not currently installed is needed. Titles can accomplish this by calling PackageInstallChunksAsync in the GDK or AddChunkSpecifiersAsync in the XDK when additional content needs to be installed from disc or the Xbox network.

For more information on Streaming Install or Intelligent Delivery with the GDK, read the Streaming Install and Intelligent Delivery overview

129-01 Intelligent Delivery of Language Packs

Tools Needed:

1 Xbox One
1 Xbox One S
1 Xbox One X
1 Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)

Test Steps

Set Xbox One console to a supported language.
Install the title.
Launch the title.
Navigate the title and ensure the experience matches that of the console selected language.
If the title offers an in-game menu option to switch languages, select each language to install each of those language chunks.
Repeat steps 1-5 for all supported languages.
Repeat steps 1-6 on all generations of devices.

Expected Result
The expected language packs are installed as expected.

Pass Examples

The title installs the expected language pack based on the console language setting.
Selecting a different language from a menu option installs the correct language pack.
The title remains stable and does not crash or become un-responsive.

Fail Examples

The title does not install the expected language pack based on the console language setting.
Selecting a different language from a menu option does not install the correct language pack.
The title crashes or becomes un-responsive.

129-02 Intelligent Delivery of Device specific Content

Tools Needed:

1 Xbox One
1 Xbox One S
1 Xbox One X
1 Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)

Test Steps

Set Xbox One console to a supported language.
Install title.
Launch the title.
Navigate the title and ensure only Xbox One specific content is installed.
Repeat steps 1-4 on all generations of devices and ensure all generation specific content is installed.
Repeat steps 1-5 for all supported languages.

Expected Result
The expected device specific content is installed as expected.

Pass Examples

The title installs the expected device specific content.
The title remains stable and does not crash or become un-responsive.

Fail Examples

The title does not install the expected device specific content.
The title crashes or becomes un-responsive.

129-03 Migration of Device Specific Content

Tools Needed:

1 Xbox One
1 Xbox One S
1 Xbox One X
1 Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)

Test Steps

Xbox One Console: Set Xbox One console to a supported language.
Xbox One Console: Install title to an external USB device.
Xbox One Console: Launch the title.
Xbox One Console: Navigate the title and ensure only Xbox One specific content is installed.
Move the USB device to an Xbox One X console
Xbox One X Console: Take the update to install Xbox One X specific content.
Xbox One X Console: Launch the title and ensure the title gracefully handles the install of additional Xbox One X content.
Move the USB device back to an Xbox One console.
Xbox One Console: Navigate the title and ensure the title gracefully handles both platform content being installed.
Repeat steps 5-9 on an Xbox One Series X.

Expected Result
The expected device specific content is installed as expected.

Pass Examples

The title installs the expected device specific content.
The title remains stable and does not crash or become un-responsive.

Fail Examples

The title crashes or becomes un-responsive.

129-04 Intelligent Delivery of On-Demand Content

Tools Needed:

1 Xbox One
1 Xbox One S
1 Xbox One X
1 Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)

Test Steps

Set Xbox One console to a supported language.
Install title.
Launch the title.
Install all on-demand content.
Repeat steps 1-4 for all supported languages.
Repeat steps 1-5 on all generations of devices.

Expected Result
The on-demand content is installed as expected.

Pass Examples

The title installs the on-demand content as expected.
The title remains stable and does not crash or become un-responsive.

Fail Examples

The title does not install the on-demand content as expected.
The title crashes or becomes un-responsive.

129-05 Features and Recipes

Tools Needed:

1 Xbox One
1 Xbox One S
1 Xbox One X
1 Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)

Test Steps

Install the base title without any optional content associated with Features and Recipes.
Navigate to all areas of the title, attempt to access content not installed and ensure the title remains stable.
For each Feature exposed in the system UI install the Feature and attempt to access it within the title and ensure the title remains stable.
For each Feature not exposed in the system UI install the Feature view via the in title UI option and ensure the title remains stable.
For each Recipe, ensure the user owns any related store entitlements and perform a fresh install.
Ensure that any Features contained within the Recipe are installed and accessible within the title.

Expected Results
The title remains stable when optional content is not installed and the title allows access to optional content when installed.

Pass Examples

The title remains stable when optional content is not installed.
The title allows access to optional content when installed.

Fail Examples

The title crashes or becomes un-responsive when optional content is not installed.
The title does not allow access to optional content when installed.

XR-123: Installation/Unlock of Game Add-Ons or Consumables During Gameplay *

Titles that offer downloadable content (DLC) must allow users to download/unlock and use the content without having to terminate and relaunch the game.

For more information on accessing and enumerating DLC in game, read the Downloadable content (DLC) packages section

123-01 Installation/Unlock of Game Add-Ons or Consumables During Gameplay

Test Steps

Launch the title and proceed into active gameplay.
Initiate a game add-on or consumable purchase from the Xbox Store.
Allow the background download to complete.
Ensure that the user is able to continue with gameplay and the title is not affected by the background download completing.
Ensure that the content can be used without having to terminate and relaunch the game.
Repeat steps 1-5 with the download completing while the title is constrained.
Repeat steps 1-5 with the download completing while the title is suspended (wait 30+ seconds for the title to fully suspend and for the suspension to interrupt any HTTP request).
If the title supports an in-game store feature, repeat steps 1-5 using this feature to initiate an add-on or game download.

Expected Result
Titles that offer game add-ons or consumables must allow users to download/unlock and use the content without having to terminate and relaunch the game.

Pass Examples

The user is able to download and use the content without having to terminate and relaunch the game.
The title prompts a user to return to a menu through an in-game prompt to load the new DLC.

Fail Examples

The user must terminate and re-launch the game in order to use the content.

123-02 Installation/Unlock of Game Add-Ons or Consumables as Part of Main Game Package During Streaming Install

Test Steps

Validate that the title supports game add-on or consumable.
Install game add-on or consumable of each type ahead of the full game's installation.
Begin installing the main game package and launch from the initial play marker (if a play marker is supported).
Attempt to use the DLC before the title finishes installing.

Expected Result
The user should be able to see that they have access to the game add-on or consumable, and if they try to play it, the title must either allow use or inform the user that the title must fully install before the DLC can be used.

Pass Examples

The user can see they have access to the content.
If the user tries to play the content, they are notified the title is still installing.

Fail Examples

The content is not visible.
The content is visible but no reason is given when the user tries to play the content.

XR-037: Dependencies on Content Packages *

Purchase of add-on content (durable or consumable) must not be required for users to complete any of the main features or content of the base game. Optional content packages must not have dependencies on other optional content packages. That is, a user must not be required to download additional content packages in order to use a content package. Game saves with unique content tied to add-on content must still load on the base game or provide clear messaging explaining why it cannot be loaded.

037-01 No Content Package Save-Game Dependencies for Base Title

Test Steps

Sign in to an Xbox profile and launch the title.
Attempt to access all features and content of the base title. verify that the user is not required to download any add-on content.
Download an available content package that can be used within the title.
Load and use the content package, progressing far enough to create a content-based game save.
Return to Home and delete the content package.
Launch the title again.
Ensure that the game save can be loaded successfully, and that gameplay can continue, or that the user is clearly informed why it cannot continue.
Messaging must be clear and inform the user specifically how to troubleshoot the issue.
Repeat Steps 1-8 with all other supported content packages.

Expected Result
Users must be able to complete any of the main features and/or content of the base title without needing to purchase add-on content. Titles must function correctly, or clearly inform the user why they cannot function correctly, after a user deletes a content package.

Pass Examples

The user is able to complete all features and content included with the base title without needing to purchase add-on content. All aspects of the title can be played without issue after the user deletes a content package.
After creating a save within an area provided by the content package and then subsequently deleting the content package, the game clearly messages the user indicating that content x needs to be installed to load the game save. Titles can also query to see if the user has an entitlement to that content and either:
- Prompt the user to download the specific content if already owned.
- Prompt the user for potential purchase of that content if not owned.

Fail Examples

The user is forced to purchase add-on content in order to complete features or content included in the base title. After the user downloads content package 1 and content package 2 during Step 3, the ability to use content package 2 in-game is lost if content package 1 is then deleted.
If a content save game dependency exists and the content is not installed, the game does not clearly message the user indicating that the content needs to be installed to load the game save.

037-02 No Dependencies on Other Content Packages

Test Steps

Sign in to an Xbox profile.
Launch the title.
Download a single piece of add-on content that the title supports.
Attempt to use the content within the title.
Verify that the user is not required to download additional content in order to make use of the content from step 3.
Exit the title and delete the content from Step 3.
Repeat Steps 2-6 for each piece of content supported by the title.

Expected Result
Users must not be required to download additional content packages in order to use a content package. Content packages must be usable in their own right.

Pass Examples

The title does not require the user to download additional content in order to use a separate content package.

Fail Examples

A user is required to download additional content in order to use a separate content package.

037-03 DLC Dependency

Test Steps

Sign in to an Xbox profile.
Download downloadable content (DLC) for the title.
Progress into gameplay and save progress using the DLC.
Exit title.
Remove DLC from console.
Launch the title and attempt to access saved progress.

Expected Result
Title gracefully handles the presence of a game save that was created with DLC if that DLC is no longer installed.

Pass Examples

User is able to load his or her saved progress and interact with the title without issue.
User is notified that specific DLC is required to access his or her saved game.

Fail Examples

Title becomes unusable when the DLC is not present.
User is unable to access saved progress and does not receive notification as to the reason.

037-04 Multiplayer DLC

Test Steps

Sign in to an Xbox profile.
Launch the title.
Console A: Download all available downloadable content that is usable in multiplayer gameplay.
Console A: Host an Xbox game session using the downloadable content (levels, characters, cars, tracks, and so on).
Console B: Attempt to join the game session created by Console A using all possible methods.
If it is not possible to join the game session, verify that clear indication is given explaining or easily inferring why it is not possible to join.
Repeat Steps 3-6 for all game modes.
Repeat Steps 3-6 with Console B as the host.

Expected Result
Titles that support downloadable content required for multiplayer gameplay must provide a clear indication to users who do not have the downloadable content installed.

Pass Examples

Users are given proper messaging when attempting to join sessions with DLC requirements if they do not meet the requirements and are provided information on how to resolve the issue (download, re-download, etc.).
Through the use of icons and / or other on-screen elements, users are given clear notification when attempting to join sessions with DLC requirements if they do not meet the requirements and are provided, or can easily infer, information on how to resolve the issue (download, re-download, etc.).
Users who meet the DLC requirements for a multiplayer match are able to join the sessions and play.

Fail Examples

Users who do not meet the DLC requirements of a multiplayer session are not given clear visual indication of the DLC requirement and how to resolve it.
Users who meet DLC requirements of a multiplayer session are not able to join together.

Purchasing from in-game stores and from the Microsoft Store

The requirements in this category specify how purchases are to be made from in-game stores and the Microsoft Store. For policies on pricing, metadata, and offers, see the Game Publishing Guide.

XR-036: In-Title Pricing Information *

Any real-world currency prices displayed within a title, including but not limited to any promotional or subscription-based discounts, must be sourced from the Xbox catalog.

For more information on in game commerce with the GDK, see Commerce.

036-01 Content Price Verification

Test Steps

Sign in to an Xbox profile.
Launch the title.
Access all areas of the title where prices are displayed.
Verify that the prices displayed match the prices in the Xbox catalog.
Terminate the title and reconfigure the Language, Language Region and Location system settings for the next supported distribution region.
Repeat Steps 1-4 for all supported distribution regions.

Expected Result
The prices displayed for content in-title should match the prices in the Xbox catalog for the same content.

Pass Examples

The prices displayed in-title are consistent with the prices in the Xbox catalog.

Fail Examples

The prices displayed in-title are different from the prices in the Xbox catalog.

User Profiles

The requirements in this category apply to how a game interacts with the Xbox user models, profiles, and saving user data.

XR-112: Establishing a User and Controller During Initial Activation and Resume *

Titles must establish one or more active users to function as the primary user or users in the title, and handle the user or users when resuming from suspended and constrained modes. Titles do this with the GDK by using either the Simplified or Advanced User Model.

GDK Simplified User Model Titles

The Simplified User Model in the GDK handles default user acquisition on behalf of the title. The title is still responsible to ensure that a controller is assigned to the user and use that controller for game input. If no controller is assigned to the default user, the title should use XUserFindControllerForUserWithUiAsync to engage the system dialog to select a controller and begin accepting input from the player.

GDK Advanced User Model, ERA, and UWP Multiple User Applications

On initial activation games can choose to determine the initial user based on their game design and preference using either the user who launched the title or by explicitly prompting for a user.

The title must indicate the active user(s) before the first profile-related action (such as saving progress or settings) is taken on that user's profile.

All Microsoft Game Development Kit (GDK) titles using the advanced user model, ERA, and UWP Multiple User Application (MUA) titles must provide an entry point to the account picker to change the active user.

When a title is resumed from suspension or constrained mode, the title must validate the user/controller pairing and react accordingly by resuming the prior user's session or acquiring a new user or users.

Note

The following table shows which test cases for XR-112 apply to your title if using the GDK Simplified User Model or the GDK Advanced User Model, ERA and UWP Multiple User Applications.

Test Cases	Applicable to GDK Simplified User Model	Applicable to GDK Advanced User Model, ERA and UWP MUA
112-02 Initial User and Controller	No	Yes
112-03 No signed in User	No	Yes
112-04 Active User Indication	Yes	Yes
112-05 Access to Account Picker	No	Yes
112-06 Handling Profile Change	No	Yes
112-07 User Change During Constrained Mode	No	Yes
112-08 User Change During Suspension	No	Yes

112-02 Initial User and Controller

Test Steps

Sign into Profile A and launch the title.
Verify the active user can control the title.
Repeat step 1 with no signed in profile and verify the title prompts to establish an active user.
Establish the active user and verify the user can control the title.

Expected Result
Titles must set the active user to the controller/user pairing which launched the title, or show an engagement prompt to identify the controller and user, or display the account picker to sign in.

Pass Examples

The title sets the active user to the controller/user pairing which launched the title.
The title shows an engagement prompt to identify the controller and user.
The title displays the account picker to sign in.

Fail Examples

The title does not allow the user to control the title with the first controller used.
The title does not prompt the user to establish an active user when launched with no user signed in.

112-03 No Signed-In User

Test Steps

Verify that no users are signed in.
Launch the title and enter every mode that supports the saving of user data.
Validate that each mode offers the user the opportunity to sign in before any data loss occurs.
Cancel the opportunity to sign in, and verify that the title provides a warning indicating that progress will not be saved.

Expected Result
Titles must offer users the opportunity to sign in if the title is in a mode that would normally save user data or game state. Titles must notify users that their progress will not be saved if they continue with gameplay without signing in

Pass Examples

A user who is not signed in is prompted to sign in when accessing a title mode that would normally save user data or game state.
The user is notified that progress will not be saved if he or she continues in mode without signing in.

Fail Examples

While in a mode that normally saves user data or game state, users are not notified that progress will not be saved if they continue in that mode without signing in.
Users are notified that they will not be able to save their progress after data loss has already occurred.

112-04 Active User Indication

Test Steps

Sign into a profile that has not seen the title before and has no associated save data.
Launch the title.
Verify that the title identifies the active user within the UI prior to performing any profile-related actions. Examples of "profile-related action" include altering a user's saved game or preferences, saving data to the user's profile, awarding achievements, writing statistics for a user, or any other local or cloud usage or manipulation of user data or state.
Create a save.
Re-launch the title and verify that the title identifies the active user within the UI prior to performing any profile-related actions.
Disconnect from the Xbox network.
Re-launch the title and verify that the title identifies the active user within the UI prior to performing any profile-related actions.

Expected Result
Titles must indicate the current user context prior to the first profile-related action.

Pass Examples

The title displays the user's gamertag and/or gamerpic within the title before performing any profile-related actions.
A title that does not use user profiles does not indicate the active user.
A title displays multiple active users for game modes that support multiple users.

Fail Examples

The title does not indicate the active user of the title prior to performing profile-related actions.

112-05 Access to Account Picker

Test Steps

Sign into a profile and launch the title.
Confirm that the title allows the active user to access the account picker in the title and select a different profile.

Expected Result
Titles must allow users to access the account picker in the title to change the active user.

Pass Examples

The title allows the user to access the account picker in the title.

Fail Examples

The title does not allow the user access to the account picker in the title.

112-06 Handling Profile Change

Test Steps

Sign into a profile and launch the title.
Access the account picker and select a different profile.
Verify that the title reacts appropriately and switches the context of the active user to the new profile.
Repeat steps 1-4 for every location in the title where there is access to the account picker.

Expected Result
Titles must allow users to seamlessly change to another user's context.

Pass Examples

The title notifies the user that changing the active user could result in data loss and prompts the user for confirmation prior to proceeding to the account picker.
The title updates appropriately to the context of the new active user.

Fail Examples

The title does not appropriately update to the context of the new active user.

112-07 User Change During Constrained Mode

Configuration:
Use xbapp list in the GDK to return the application package full name (PFN) for the title.

Test Steps

Sign in profile A and launch the title.
At various locations within the title, press the Xbox button and select 'Home' to constrain the title.
Verify the title has entered a constrained state by running xbapp query [PFN].
While the title is constrained, sign out of Profile A and sign into profile B.
Resume the title by selecting the tile from Home.
Verify that the title reacts accordingly to the new active user.

Expected Result
When a title is resumed from constrained mode the title must verify if all previously engaged users are still signed into the console.

Pass Examples

An application automatically switches the active user context to Profile B upon resuming.
A game title automatically removes Profile A from the title or reestablishes a new user and uses that new user's state for gameplay.

Fail Examples

Titles do not update to remove profile A from the context as the active user.
A game continues to use Profile A's state for gameplay after a new profile is selected.

112-08 User Change During Suspension

Configuration:
Use xbapp list in the GDK to return the application package full name (PFN) for the title.

Test Steps

Sign in Profile A and launch the title.
At various locations within the title suspend the title using xbapp suspend [PFN].
Wait at least 30 seconds for the title to fully suspend and for the suspension to interrupt any HTTP request.
Verify the title has entered a suspended state by running xbapp query [PFN].
While the title is suspended, sign out of profile A and sign into profile B.
Resume the title by selecting the tile from Home.
Verify that the title reacts accordingly to the new active user.
Enter gameplay with the new active user and verify the user is able to make progress.

Expected Result
When a title is resumed from suspension, the title must verify if all previously engaged users are still signed into the console.

Pass Examples

An application automatically switches the active user context to profile B upon resuming.
A game title automatically removes profile A from the title or reestablishes a new user and uses that new user's state for gameplay.

Fail Examples

Titles do not update to remove profile A from the context as the active user.
A game continues to use profile A's state for gameplay after a new profile is selected.

XR-115: Addition and Removal of Users or Controllers During Gameplay *

Titles which support multiple users must respond to the addition and removal of users or scenarios in which an active player has no controller assigned or a controller loss during gameplay as follows:

Controller Addition:
After titles have selected or have been provided the initial user and controller, titles can optionally accept input from other controllers. Titles which support multiplayer experiences should consider how an additional player or controller is added into game play and is bound to a user with XUserAddAsync. For example, 'Press A to join' or illustrating a controller silhouette on a player select screen.

Controller Removal:
If the player's controller that is driving gameplay is removed during gameplay, titles must allow reestablishment of a new active controller (for example, "Press A to continue" or receiving a ControllerPairingChanged in ERA or XUserDeviceAssociationChangedCallback event in the GDK for the active user with a valid controller). Titles can also invoke system UX using XUserFindControllerForUserWithUiAsync to prompt the user to pair a controller to their user and return to gameplay.

User Addition:
When using ERA or UWP, if a new user signs in, the title can add the user to the title if the title supports a multiuser experience, but the title must not automatically switch active users to the new user or interrupt the active users' experience based on a new signed-in user event.

When using the GDK (using either Simplified or Advanced User Models), users are only added when the title calls XUserAddAsync.

Primary User Removal:
For titles using ERA or the GDK advanced user model, if the primary user is signed out (via the guide, SPOP or other means), the title must either remove the player from the game or reestablish a user and active controller.

For titles using the GDK Simplified User Model, the primary player being removed will result in the title being suspended at the system level.

In all scenarios, titles handle removal/closure by placing their game in a good state. This includes writing to connected storage, notifying any relevant MPSD sessions that the user has left, and bringing the user to an appropriate place for sign-in if a new user has also not been added.

Additional/Secondary User Removal:
Titles can handle this event in their discretion, usually by removing the player from game play immediately or prompting the player to rejoin in the context of the multiplayer experience being used.

Note

The following table shows which test cases for XR-115 apply to your title if using the GDK Simplified User Model or the GDK Advanced User Model, ERA and UWP Multiple User Applications.

Test Cases	Applicable to GDK Simplified User Model	Applicable to GDK Advanced User Model, ERA and UWP MUA
115-01 Addition of Users	No	Yes
115-02 Removal of Controllers	Yes	Yes
115-03 Removal of Users	No	Yes

115-01 Addition of Users only applies to ERA and UWP Multiple User Applications. With the GDK, titles are only able to see those users that they have intentionally added. Users added via the shell are unknown to the title.

115-01 Addition of Users

Test Steps

Sign into Profile A and ensure no other profiles are signed in.
Launch the title and progress into gameplay.
At various points during the title's use, connect a second controller and sign into Profile B.
Profile B attempts to provide controller input to the title.

Expected Result
ERA or UWP MUA titles must not automatically interrupt the active user's experience.

Pass Examples

Titles do not automatically switch active users to the new user or interrupt the active user's experience.
Game titles may choose to allow Profile B to control the title depending upon the current context.

Fail Examples

The title immediately switches context to Profile B as the active user.

115-02 Removal of Controllers

Test Steps

Sign into a profile and launch the title.
At various points during the title's use, remove the batteries from the controller.
Replace the batteries in the controller and verify that the user can continue to use the title.
Repeat Steps 1-3 but connect a second controller rather than replacing the batteries.

Expected Result
Titles must respond to the removal and addition of controllers correctly.

Pass Examples

The active user should be able to continue using the title following the removal or addition of a controller.
The user is prompted to re-establish a new active controller (for example, "Press A to continue" or by invoking the system UX).

Fail Examples

Users are unable to continue using a title following the removal of a controller.

115-03 Removal of Users

Test Steps

Sign into Profile A and ensure no other profiles are signed in.
Launch the title and progress into gameplay.
At various points during the title's use, sign out of Profile A.
Verify that the title either invokes the account picker or returns the user to the front end.
Where possible, interact with the title in the following ways:
- Sign into Profile A and ensure that the title does not further interrupt the user's experience.
- Sign into Profile B and ensure that the title updates to the context of the new user.

Expected Result
The title must either remove the player from the game or re-establish a user and active controller. If the player is removed from the game, the title should be left in a good state. This includes writing to connected storage, notifying any relevant MPSD sessions that the user has left, and bringing the user to an appropriate place for sign-in if a new user has also not been added.

Pass Examples

The title removes the player from the game and returns to the front end.
The title allows the user to re-establish a new user and correctly updates to the relevant user context.

Fail Examples

The title fails to react to the change in user state.
The title continues to use Profile A's user state after a new profile is selected.

XR-045: Xbox network and Account Privileges *

Xbox network provides users with an expected level of privacy and online safety for themselves and their children. In order to deliver on that promise, titles must check the Xbox network service for privileges to complete certain actions on the Xbox network service or in a title experience.

While privilege checking and adherence applies to all accounts, it's important to note the experience and expectations for child accounts specifically. For child accounts, restrictions on certain activities may be blocked due to age-based defaults and/or configurations by the child's family organizer (parent or guardian). Children cannot make changes themselves, however, with certain activities it is possible and expected the title invokes the necessary system UI to allow young players to request an exception via an approval flow for that associated activity. In such circumstances, for instance, a young player may be blocked from multiplayer globally, but the family parent or guardian could approve multiplayer for the specific title via the system UI; then the child would and should be able to access this game mode for that specific title.

Activity	ID	Privilege Name	Notes
Playing in a multiplayer game session	254	`XPRIVILEGE_MULTIPLAYER_SESSIONS`	Allows a user to join online multiplayer gameplay sessions with real-world users (not bots) in scenarios such as: Synchronous player-vs-player gameplay in the same session, asynchronous turn-based gameplay, Team-based gameplay, User-initiated matchmaking, Sending or accepting invitations, Join-in-progress sessions. Note this privilege does not pertain to local multiplayer games run on the same device.
Playing in a cross-network game play session	185	`AuthPrivileges.CrossNetworkPlay`	Allows a user to participate in a gameplay session with other real-world players who are not signed into Xbox services in scenarios such as: Synchronous player-vs-player gameplay in the same session, asynchronous turn-based gameplay, Team-based gameplay, User-initiated matchmaking, Sending or accepting invitations, Join-in-progress sessions.
Communication with anyone	252	`XPRIVILEGE_COMMUNICATIONS`	Allows a user to communicate with any other Xbox network users through voice or text.
Shared gaming sessions	189	`XPRIVILEGE_SESSIONS`	Allows a user to participate in connected single-player experiences in shared environments or in scenarios where a title is a hybrid free to play and paid multiplayer title and uses this privilege to gate those experiences Xbox consoles. Single player experiences must not have any features covered under privilege 252 or 254 (Communications and Multiplayer, respectively). Use of this privilege is a title capability that requires platform approval.
User-generated content (UGC)	247	`XPRIVILEGE_USER_CREATED_CONTENT`	Allows a user to see other users' UGC online, download other users' UGC, or share their own UGC online. This does not restrict usage of previously downloaded UGC.
Sharing to a social network	220	`XPRIVILEGE_SOCIAL_NETWORK_SHARING`	Xbox consoles Only: Allows a user to share information, including game progress, Kinect-generated content, game clips, and so on outside of the Xbox network.

Free to play titles, demos, or betas can be configured to allow multiplayer gameplay (ID 254) for players who are not Game Pass subscribers. This is done via a service side configuration and can be initiated by contacting your Microsoft representative. These titles must continue to check for the multiplayer game privilege to ensure that parental controls and player choices are respected.

045-01 Respect User Privileges

Test Steps

Sign in to an Xbox profile and launch the title.
For each of the privileges identified in the XR Remarks, identify if the title supports the associated activity.
For each possible setting of each applicable privilege identified in step 2, perform the following:
- Exit the title and change the user's settings for the privilege.
- Restart the console.
- Sign into the same profile and launch the title.
- Visit all relevant areas of the title, use all title features relevant to the privilege and verify that the title respects the user's current privilege setting.
- Attempt to access all offline and online areas using a Silver Xbox profile.

Expected Result
Titles must honor the user's privilege settings.

Pass Examples

The title respects the user's privilege settings.
The title treats a partial-allow privilege setting as if the privilege is disabled / disallowed (e.g. when the User-generated content (UGC) privilege is set to Friends Only, the title behaves as if the privilege is set to Blocked).
For titles using the XDK, the title invokes the system UI to alert the user of any privilege conflicts (titles must use the Store::Product::CheckPrivilegeAsync API). When the system UI cannot be invoked (privileges 252, 189, 247) the title shows an informative message to let the user know they cannot participate.
For titles using the GDK, the title invokes the system UI to alert the user of any privilege conflicts (titles must use the XUserCheckPrivilege and XUserResolvePrivilegeWithUiAsync APIs). When the system UI cannot be invoked (privileges 252, 189, 247) the title shows an informative message to let the user know they cannot participate.
For titles using XSAPI, the title shows an informative message to let the user know they cannot participate.

Fail Examples

The title persists a user's privilege settings and does not reflect the user's actual privileges after they have been changed.
The title treats a partial-allow privilege setting as if the privilege is set to its least restrictive setting (e.g. when the User-generated content (UGC) privilege is set to Friends Only, the title behaves as if the privilege is set to Allowed).
For titles using the XDK or GDK, the title uses in-game messaging to alert the user of any privilege conflicts and does not display the System UI.
For titles using XSAPI, the title does not show an informative message to let the user know they cannot participate.

045-02 Respect User Privileges - Xbox Family

Test Setup and Configuration

Xbox Family which includes the following Microsoft accounts:
Adult (greater than 18 years) designated as Organizer.
Child (less than 13 years) with the Child Default privilege settings:

Activity	Child Default Privilege Setting
You can join multiplayer games	Block
You can join cross-network play	Block
You can communicate with voice, text, or invites	Friends
You can communicate outside of Xbox network with voice & text	Block
You can see and upload community creations	Block
You can share outside of Xbox	Block

References and Links

Test Steps

Sign into the adult and child Microsoft accounts and launch the title with the child account.
For each of the privileges identified in the XR Remarks, identify if the title supports the associated activity.
For each possible setting of each applicable privilege identified in step 2, perform the following:
- Verify the associated activity is allowed/not-allowed based on the account privileges. For example: he title supports multiplayer, and the child account has the multiplayer privilege blocked. Verify the title blocks all multiplayer activity for the child and the parental permission prompts (system TCUI) are displayed when the child attempts to participate in multiplayer activities.
- Exit the title and change the user's child's privilege settings for the privilege activities the title supports; going from blocked to allowed. For example: changing multiplayer or user generated content from blocked to allowed.
- Restart the console.
- Sign into the same profile and launch the title.
- Visit all relevant areas of the title, use all title features relevant to the privilege and verify that the title respects the user's current privilege setting. For example: the title supports multiplayer. The child was blocked but now has been granted multiplayer. The title properly allows the child to access multiplayer game mode(s).
Repeat steps 2-3 with a parent account not signed into the console.

Expected Results
Titles must respect all Xbox Family member's privilege settings.

Pass Examples

The title respects a child's privilege settings.
The title allows a child to participate in an activity when the privilege for that activity is allowed.
The title does not allow a child to participate in an activity when the privilege for that activity is blocked.
The title allows a child to participate in an activity that is blocked after permission for that activity is allowed by the parent (via the parental permission UI).
The title does not allow a child to participate in an activity that is blocked and permission for that activity is not allowed by the parent (via the parental permission UI).
The title treats a partial-allow privilege setting as if the privilege is disabled / disallowed (e.g. when the User-generated content (UGC) privilege is set to Friends Only, the title behaves as if the privilege is set to Blocked).
For titles using the XDK, the title invokes the system UI to alert the user of any privilege conflicts (titles must use the Store::Product::CheckPrivilegeAsync API). When the system UI cannot be invoked (privileges 252, 189, 247) the title shows an informative message to let the user know they cannot participate.
For titles using the GDK, the title invokes the system UI to alert the user of any privilege conflicts (titles must use the XUserCheckPrivilege and XUserResolvePrivilegeWithUiAsync APIs). When the system UI cannot be invoked (privileges 252, 189, 247) the title shows an informative message to let the user know they cannot participate.
For titles using XSAPI, the title shows an informative message to let the user know they cannot participate.

Fail Examples

The title does not respect the child's privilege settings.
- Example: The title supports multiplayer and allows the child with multiplayer blocked to access multiplayer game modes.
The title does not invoke the proper UI to alert and inform the child of privilege conflicts.
- Example: The title supports multiplayer, but the child is never prompted for parental permission when the privilege is blocked.
The title allows a child to participate in an activity when the privilege for that activity is blocked.
The title does not allow a child to participate in an activity when the privilege for that activity is allowed.
The title allows a child to participate in an activity that is blocked and permission for that activity is not allowed by the parent (via the parental permission UI).
The title does not allow a child to participate in an activity that is blocked and permission for that activity is allowed by the parent (via the parental permission UI).
The title persists a user's privilege settings and does not reflect the user's actual privileges after they have been changed.
- Example: The title supports multiplayer. The child account has multiplayer blocked but is granted permission by the parent through the system UI. The title continues to block multiplayer even though the privilege has been granted.
The title treats a partial-allow privilege setting as if the privilege is set to its least restrictive setting. For Example: When the user-generated content (UGC) privilege is set to Friends Only, the title behaves as if the privilege is set to Allowed.
For titles using the XDK, the title does not invoke the system UI to alert the user of any privilege conflicts (titles must use the Store::Product::CheckPrivilegeAsync API). When the system UI cannot be invoked (privileges 252, 189, 247) the title does not show an informative message to let the user know they cannot participate.
For titles using the GDK, the title does not invoke the system UI to alert the user of any privilege conflicts (titles must use the XUserCheckPrivilege and XUserResolvePrivilegeWithUiAsync APIs). When the system UI cannot be invoked (privileges 252, 189, 247) the title does not show an informative message to let the user know they cannot participate.
For titles using XSAPI, the title does not show an informative message to let the user know they cannot participate.

XR-046: Display Name and Gamerpic *

On Xbox consoles, titles must use the gamertag as their primary display name.

Based on design choice titles can choose between the player's modern gamertag or their classic gamertag. Modern gamertag is available in the GDK and classic gamertag is available in both ERA and the GDK.

On non-console platforms, while not required, we recommend you use the Xbox network player's gamertag in the appropriate locations within the game title's experience.

The gamertag must be displayed correctly in the title based on the gamertag type used:

Modern Gamertag
Display all 16 characters of the unique modern gamertag, which includes up to 12 characters of the modern gamertag, followed by # and the suffix number (if present). For example: Major Nelson (no suffix present) or Major Nelson#881. If modern gamertags are used, all Unicode character ranges available for modern gamertags must be supported. For more modern gamertag information and best practices visit the GDK development documentation article 'Overview of modern gamertags'.

Classic Gamertag
Correctly display all 15 characters of the classic gamertag. Classic gamertags include only ASCII characters a-z, A-Z, 0-9, comma (,), and space (ASCII character 0x20). For example: Major Nelson

In the GDK these items are returned using the XUserGetGamertag API. In ERA the gamertag is obtained using the GetUserProfileAsync API.

046-01 Display Name and Gamerpic

Tools Needed

XblTestAccountGui.exe from the GDK

Preparation
Create four test accounts for each of the following names and change the gamertag using XblTestAccountGui.exe for each test account to the following:

สฐ众нь컴퓨
आथाώঙぁヺ
øÜêþЯЂў
gttest1

Test Steps

Locate and view where gamertags are displayed within the title.
Check to see how the users' gamertag is displayed in all areas identified in Step [1].
If the title displays users' pictures, verify that the correct Microsoft account picture or gamerpic appears for each account.

Expected Result
The user's gamertag must be displayed correctly.

Pass Examples

The gamertag correctly shows the Unicode characters (including the auto-generated suffix) when using Modern Gamertag.
The gamertag is correctly shown when using Classic Gamertag.

Fail Examples

The gamertag is not rendered at all because the Unicode characters are shown as blank characters.
The gamertag is not correctly shown when using Classic Gamertag.

XR-047: User-Profile Access *

Titles must give users the option to access other Xbox network users' gamercards wherever users' display names are enumerated.

047-01 User-Profile Access

Test Steps

Devices 1 and 2: Boot the title.
Devices 1 and 2: Sign in to an Xbox profile.
Device 1: Set up an Xbox multiplayer game session.
Device 2: Find and join the game session created by console 1.
Verify the following after device 2 has joined the game session:

From the pre-game lobby, access another Xbox user's gamercard by selecting the user's gamertag.
During gameplay, attempt to access another Xbox user's gamercard by selecting the user's gamertag. (This may or may not be possible, depending on the title.)
From the post-game statistics screen, access another Xbox user's gamercard by selecting the user's gamertag.
From the leaderboards area, access another user's Xbox gamercard by selecting the user's gamertag.
Find any other area where gamertags are listed, and attempt to access another Xbox user's gamercard by selecting the user's gamertag.

Expected Result
It is expected that the user will be able to view the other Xbox user's gamercard information.

Pass Examples

A user is able to access another Xbox user's gamercard in all locations where gamertags are displayed and UI navigation is enabled.

Fail Examples

A user is unable to access another Xbox user's gamercard in any location where gamertags are displayed and UI navigation is enabled.

XR-048: Profile Settings Usage *

The Xbox network is the source of truth for Xbox user profile information. To support this, titles must not store users’ information sourced from the Xbox network, such as profile data, preferences, or gamertags, beyond a locally stored cache intended to support scenarios of network disconnection. Any offline caches must be updated upon the next available connection to the service.

048-01 Profile Settings Usage

Configuration

2 Xbox devices

Test Steps

Select a profile and create a save.
Change user profile data, including updating a gamertag or account name.
Boot the title and load the save made in Step [2].
Verify that the user-profile data visible during gameplay have changed and are not stored in the save game.
Verify that any reference to the gamertag (created automatically by the title) has been updated. This includes any reference on server-hosted functionality as well as any reference within the title.
Boot the title on a second device and verify the updated gamertag is displayed correctly.

Expected Result
User-profile data must not be stored. For instance, if the title uses the gamertag in-game (like in a welcome message) or on a non-Xbox server (such as naming uploaded data), it must not persist if the user changes their gamertag. This does not apply if the user has manually entered the gamertag.

Pass Examples

User-profile data and preference settings are updated in all displays after they have been changed.

Fail Examples

The title does not display the user's updated gamertag or Microsoft account name either within the title or on Xbox Home for locally stored save data such as replays, saves, options, maps, and teams.
The title does not update a user's gamertag for persistent posts, such as game clips, replays, leaderboards, or other custom posts, such as messages, bulletin posts, user challenges, costumes, themes, livery, tournaments, and league. Note: This applies to both new and previously created posts.
The title stores the user's gamertag for the user's saved data, such as replays, saves, options, maps, and teams, resulting in the save data becoming unusable if the user changes their gamertag or account name.

XR-052: User State and Title-Save Location, Roaming and Dependencies *

Titles must associate progress, saved state, preferences, achievements, and other rewards with the user(s) who have recorded that progress, chosen the preferences, or earned the rewards. Titles accomplish this by properly handling user-change notifications. Titles must avoid saving state for users who are no longer signed in. Game save data must not have any dependencies on shared content or local storage.

For games that use the same TitleID across platforms, devices and/or console generations, game save progress must roam when the user is signed into the Xbox network as follows:

Within the same platform (Xbox consoles).
Within devices on the same platform (e.g., Xbox One and Xbox One S).
Across generations in the device platform (e.g., Xbox One and Xbox Series X|S).
Across PCs in the Windows platform (e.g., between two different PCs).
Across PCs in the Windows platform and Xbox console platforms, (e.g., Windows and Xbox Series X|S) game save roaming is not required but is recommended to support the player's experience.
For non-Microsoft platforms (e.g., iOS, Android, Switch, PlayStation®) game save roaming is not required but is recommended to support the player's experience.

Note

The following table shows which test cases apply to your title if using the GDK Simplified User Model or the GDK Advanced User Model, ERA and UWP Multiple User Applications. Refer to XR-112 for additional details regarding the use of the Simplified User Model versus the Advanced User Model.

Test Cases	Applicable to GDK Simplified User Model	Applicable to GDK Advanced User Model, ERA and UWP MUA
052-01 User Sign-In and Sign-Out	No	Yes
052-02 User Change During Suspended or Terminated State	No	Yes
052-05 Correct User Association	Yes	Yes
052-06 Cloud Storage: Roaming	Yes	Yes

Configuration:
This test case only applies to console. For Xbox devices, the xbuser command-line utility can be used to test users being signed in or out at anytime.

xbuser signin /i:\<user ID> [/p:password]
xbuser signin /e:\<email> [/p:password]
xbuser signout /i:\<user ID> [/p:password]
xbuser signout /e:\<email> [/p:password]

Test Steps

Ensure that Profile A and Profile B have set the console to Home.
Ensure that Profile A has save data including game progress and user preferences.
Ensure that Profile B does not have any save data.
Sign into Profile A and launch the title. Ensure all save data and preferences have been preserved by visiting all areas of the title, including but not limited to:
- Single-player or multiplayer game sessions.
- Menus.
- Video or audio playback.
Sign out of Profile A and sign into Profile B.
Verify that the title correctly updates the user progress, saved state, preferences, achievements, or other awards of Profile B by revisiting all areas of the title validated in step 4.
Begin gameplay to create save progress, and alter user preferences for Profile B.
Terminate and re-launch the title and verify that the save data from step 7 is reflected accurately.
Sign out of Profile B.
Delete save data 'Everywhere' from Profile A and repeat steps 4-8.

Expected Result
Changes to the primary user should be treated appropriately by the title.

Pass Examples

User progress, saved state, preferences, achievements, or other awards are associated with the correct user following a user change.

Fail Examples

The title incorrectly associates user progress, saved state, preferences, achievements, or other awards with a user following a user change.
The title continues to award save data to the first user.
A new user can alter a prior user's save data, state or profile after they have signed out.

052-02 User Change During Suspended or Terminated State

Configuration:
This test case only applies to console. To test process lifetime management (PLM) state transitions, these commands are useful in the GDK:

xbapp suspend [package full name]
xbapp resume [package full name]

Note: If you prefer working with a GUI instead of the command prompt, consider using Xbox One Manager. It is a desktop application that allows you to manage users and test PLM events on your console as well as other common tasks.

Test Steps

Sign in to a profile and launch the title.
Visit all areas of the title, including but not limited to:
- Single-player or multiplayer game sessions
- Menus
- Video or audio playback
Suspend the title by running xbapp suspend [package full name].
Wait at least 30 seconds for the title to fully suspend and for the suspension to interrupt any HTTP request.
Sign out the primary user and sign in as a different user.
Launch the title using the new user and attempt to continue from the previous user's location.
Repeat Steps 1-6 for all areas of the title.
Repeat Steps 1-7 but terminating the title rather than suspending it.

Expected Result
Changes to the primary user should be treated appropriately by the title.

Pass Examples

The title state upon launching with a different user is contextually appropriate for the type of title.
User progress, saved state, preferences, achievements, or other awards are associated with the correct user following a user change.

Fail Examples

The title incorrectly associates user progress, saved state, preferences, achievements, or other awards with a user following a user change.
The title continues to award save data to the first user.
A new user can alter a prior user's save data, state or profile after they have signed out.

052-05 Correct User Association

Test Steps

Sign in to a profile and Launch the title.
Progress into gameplay and save game progress.
Terminate the title.
Sign out of the profile from Step 1 and sign in to a new profile.
Launch the title and attempt to access saved progress.

Expected Result
Progress saved for the original user must not be visible/accessible to the new profile.

Pass Examples

Only saved progress associated with the new profile in step 4 is shown in step 5.

Fail Examples

The title allows a new profile to load a different profile's saved progress.

052-06 Cloud Storage: Roaming

Devices Needed:

Xbox One
Xbox One S
Xbox One X
Xbox Series X Dev Kit (using Xbox Series X|S retail console mode)
2 PCs

Test Steps

Sign in to an Xbox profile on device A and launch the title.
Begin gameplay and make save progress (if possible, create a settings save by changing or adding a new setting configuration).
Exit the title.
Sign in on a second device from the same platform/generation (e.g., Xbox Series S and Xbox Series X, Xbox One and Xbox One S and a second PC) that was used in Step 1 with the same profile used in Step 1.
- Launch the same title from Step 1 and verify that all saved games and any settings and/or configuration files can be accessed and loaded correctly and they don't have any dependencies on shared content.
For games using the same TitleID on the same platform across generations (e.g., Xbox One and Xbox Series X|S), repeat step 4.
For PC games using the same TitleID on the Windows platform, repeat step 4.
If supported, for games using the same TitleID across platforms (e.g., Windows and Xbox Series X|S):
- Launch the same title from Step 1 on the other supported platforms and verify that all saved games and any settings and/or configuration files can be accessed and loaded correctly and they don't have any dependencies on shared content.

Expected Result
Title-save progress must be associated with a user profile and must roam between like devices/platforms when the user is signed into Xbox services. For games using the same TitleID on the same platform across generations, game save data must roam between these platforms. For PC games using the same TitleID on the Windows platform, game save data must roam between different PCs. Game save data must not have any dependencies on shared content.

Pass Examples

Game saves and associated settings files can be downloaded successfully on a second console on the same console platform/generation (e.g., Xbox Series S and Xbox Series X or Xbox One and Xbox One S).
Game saves and associated settings files can be downloaded successfully on a second PC on the Windows platform.
For console games that share the same TitleID on the same platform across generations (e.g. Xbox One and Xbox Series X|S), saves and associated settings files can be roamed between these devices.
Game save data does not have any dependencies on shared content.

Fail Examples

Game saves and associated settings files cannot be downloaded successfully on a second console on the same platform/generation (e.g., Xbox Series S and Xbox Series X or Xbox One and Xbox One S).
Game saves and associated settings files cannot be downloaded successfully on a second PC on the Windows platform.
For console games that share the same TitleID on the same platform across generations (e.g. Xbox One and Xbox Series X|S), saves and associated settings files cannot be roamed between these devices.
The saves in the cloud are not recognized by the title on first launch, and through no user interaction, are subsequently overwritten on the second device.
Game save data has dependencies on shared content.

Achievements and Awards

The following requirements apply to titles that offer achievements on the Xbox network. All games targeting Xbox consoles are required to have Achievements and meet the following requirements. Demos are not allowed to have achievements; however, they have the option of supporting Hero Stats.

XR-055: Achievements and Gamerscore *

Titles must provide the required number (minimum and maximum) of achievements and their associated gamerscore at launch. Titles are permitted to add achievements or gamerscore at any time after launch, with or without corresponding new content, but they cannot exceed title-based or calendar-based limits.

A single achievement cannot exceed 200 gamerscore and all achievements in the title must be achievable.

Unlocking achievements in the base game or a content update must represent a thorough exploration of or engagement with game content.

Item	Launch	Semi-annual additions	Lifetime limit
Minimum achievements	10	0	10
Maximum achievements	100	100	500
Gamerscore	1000	1000	5000

Note

"Semi-annual" means January-June, July-December. Base game achievements and Gamerscore do not count towards the semi-annual limits.

055-01 Achievements

Test Steps

Review the amount of gamerscore and total number of achievements supported by the title.
Play through the title and attempt to gain as many achievements as possible.
Repeat step 2 after resuming from connected-standby.
Repeat step 2 while disconnected from Xbox services.

Expected Result
All achievements unlock according to their criteria and the maximum possible Gamerscore for the base game's launch is 1000G spread between 10-100 achievements. All achievements represent a thorough exploration of or engagement with game content.

Pass Examples

All achievements can be gained.
Achievements unlock as per their criteria.
All achievements represent a thorough exploration of or engagement with game content.
The launch version of the game has 1000 gamerscore spread across 10-100 achievements.

Fail Examples

An achievement doesn't unlock when the criteria has been met.
An achievement unlocks before the criteria has been met.
Achievements do not represent a thorough exploration of or engagement with game content.
All achievements can be unlocked within a few minutes of starting the game.
Achievements can be unlocked without any (or minimal) user input unless required as part of the core gameplay loop.
The launch version of the game does not have 1000G.
The launch version of the game has more or fewer than 10-100 achievements.
Achievements do not unlock after resuming from connected-standby.
A single achievement exceeds 200 gamerscore.
Achievements do not unlock after reconnection to Xbox services.

XR-057: Unlocking Achievements *

Titles must provide a way for a user to earn all achievements defined by the base title without being required to purchase additional in-title content.

Achievements must be unlocked through in-game actions, gameplay, and/or experiences.

Titles must not provide players alternative options that unlock achievements directly without corresponding gameplay activity. A non-exhaustive list of disallowed options:

A real-money purchase
In-game cheat codes, consoles, or menu options

These options may be used to reduce the difficulty of the gameplay required to unlock achievements.

057-01 No Additional Purchases Required for Base Achievements

Test Steps

Review the achievement descriptions on the base title.
Verify that they do not require additional purchases or content.
Gain all achievements.

Expected Result
All achievements can be gained without being required to purchase additional in-title content.

Pass Examples

All achievements can be gained without being required to purchase additional in-title content.
No achievements require additional in-title content.

Fail Examples

The user is required to purchase additional in-title content to unlock an achievement defined by the base title.

Multiplayer Sessions

The requirements in this category pertain to game titles that provide multiplayer sessions on Xbox. Xbox offers a consistent and simple way to find multiplayer sessions and to fine-tune the parameters used to find those sessions.

XR-064: Joinable Game Sessions and Online Play *

On Xbox consoles, titles that offer joinable game sessions must enable joinability through the Xbox shell interface.

Titles that offer cross platform multiplayer with Xbox consoles from PC devices using Xbox sign in must also enable joins through the Game Bar experience.

064-01 Joining a Game Session from Outside the Game

Configuration:

2 Xbox Profiles
Device 1 Profile A - Friends with Profile B
Device 2 Profile B - Friends with Profile A

Test Steps

Using Profile A, create a joinable game session.
Using Profile B not running the title, access the Friends List via the Xbox shell interface and verify that the Profile A is listed as joinable.
- It is possible that some games may only support private multiplayer sessions and therefore not appear as joinable for Profile B, in which case please jump to step 6.
Profile B join Profile A's game.
Confirm that both profiles are placed into the game experience together.
Repeat steps 1-4 with Profile B while the title is in a suspended state.
- Wait at least 30 seconds for the title to fully suspend and for the suspension to interrupt any HTTP request.
Repeat steps 1-5 but this time, instead of Profile B joining through the Friends List, have Profile A send a game invite via the system shell to Profile B and make sure Profile B can receive, accept, and join Profile A.

Expected Result
User B must be able to join user A's game and progress into the game experience together. For games that only support private multiplayer sessions and therefore do not appear as joinable for Profile B, it is acceptable for invites to be the only mechanism to join Profile A. For multiplayer game sessions that only support joining the session via matchmaking (e.g. ranked matches), it is acceptable to not support joining via the Xbox shell interface. For titles that support cross-platform multiplayer, users must be able to join between an Xbox One Console and PC.

Pass Examples

Both profiles are placed into the game experience together.
User B is able to join user A's game and progress into the game experience together.
User A does not appear as joinable in the Friends List via the Xbox shell interface because the game only supports private multiplayer sessions, however user A can send user B a game invitation via the system shell.
User A does not appear as joinable and is unable to send game invites via the Xbox shell interface whilst participating in a session that only supports joining via matchmaking (e.g. ranked matches).

Fail Examples

User B is not able to successfully join User A's game and is not placed in the game experience.
User A does not appear as joinable in the Friends List via the Xbox shell interface because the game only supports private multiplayer sessions, and user A cannot send user B a game invitation via the system shell.

064-02 Joining a Game Session from the Same Game

Configuration

2 Xbox Profiles
Device 1 Profile A - Friends with Profile B
Device 2 Profile B - Friends with Profile A

Test Steps

Using Profile A, launch the title and create a joinable game session within the title.
Using Profile B, launch the same title and enter some experience within the title.
Using Profile B, access the Friends List via the Xbox shell interface and select to join Profile A's game.
- It is possible that some games may only support private multiplayer sessions and therefore do not appear as joinable for Profile B, in which case please jump to step 5.
Confirm that both profiles are placed into the game experience together.
Repeat steps 1-4 but this time instead of Profile B joining through the Friends List via the Xbox shell interface, have Profile A send a game invite via the system shell to Profile B and make sure Profile B can receive, accept, and join Profile A.

Pass Examples

Both profiles are placed into the game experience together.
User B is able to join user A's game and progress into the game experience together.
User A does not appear as joinable in the Friends List via the Xbox shell interface because the game only supports private multiplayer sessions, however user A can send user B a game invitation via the system shell.
User A does not appear as joinable and is unable to send game invites via the Xbox shell interface whilst participating in a session that only supports joining via matchmaking (e.g. ranked matches).

Fail Examples

User B is not able to successfully join User A's game and is not placed in the game experience.
User A does not appear as joinable in the Friends List via the Xbox shell interface because the game only supports private multiplayer sessions, and user A cannot send user B a game invitation via the system shell.

064-05 Non-Joinable Game

Configuration

3 Xbox profiles each signed into a different device
Device 1 Profile A - Friends with Profiles B & C
Device 2 Profile B - Friends with Profile A
Device 3 Profile C - Friends with Profile A

Test Steps

Using Profile A, launch the title and create a joinable game session.
Using Profile A, invite profiles B and C to the game.
Using Profile A, enter a game session so there is only one remaining slot after A joins.
Using Profile B, accept the invite.
Confirm Profiles A & B are playing together.
Using Profile C, accept the invite and attempt to join the game session.

Expected Result
Profile C is asked to wait until the next opportunity to jump in or Profile C is messaged the reason for the failure to join the game session.

Pass Examples

Profile C is asked to wait until the next opportunity to jump in.
Profile C is messaged the reason for the failure to join the game session.

Fail Examples

Profile C is not asked to wait until the next opportunity to jump in and Profile C is not messaged for the failure to join.

XR-067: Maintaining Multiplayer Session State *

On Xbox consoles, titles with online multiplayer functionality must maintain session-state information on the Xbox network. Titles do this through the Xbox Multiplayer Session Directory (MPSD) or if a title has their own multiplayer session state functionality, they may choose to instead record player interactions using the Multiplayer Activity Recent Player feature.

On devices other than Xbox consoles, titles which offer cross platform multiplayer with Xbox consoles must maintain session-state information in the Xbox Multiplayer Session Directory (MPSD). If they have their own session state functionality, they may choose to instead record player interactions using the Multiplayer Activity Recent Player feature.

067-01 Maintaining Session State

Test Steps

Sign into an Xbox profile and launch the title on multiple devices.
Complete an Xbox game session with all players.
Return Home and view the Recent Players list to verify that all players from the game session are included.
Repeat steps 1-3 several more times but this time using new accounts each time.
Repeat steps 1-4 but this time have one or more player(s) leave during gameplay and ensure their profile(s) still appear in the Recent Players list during step 2.

Expected Result
Users must be able to review all players from each and every recently played game session.

Pass Examples

All profiles are included in the device's Recent Players list.

Fail Examples

Not all the profiles are included in the device's Recent Players list.
Users who quit during multiplayer gameplay do not appear in the Recent Players list.

XR-070: Friends Lists *

Titles must use the Xbox network friends list as the primary list of friends. Titles must obtain the friends list from Xbox APIs and must not store the friends list in a permanent nature on game servers.

Titles can display a secondary list of friends from a central title account for players not on the Xbox network or not on the user's Xbox network friends list. Based on design, titles may create a blended friends list experience containing both Xbox network and publisher account friends in a central location; iconography or other clarifying marks must be used to disambiguate Xbox friends from those on other networks.

For information on using the friends list using the GDK, read the People System (Friends List) overview

070-01 Xbox Friends List

Test Steps

Locate any lists of people that are displayed within the title and verify they contain the Xbox network Friends list.
If the title supports a blended friends list containing both Xbox network and publisher account friends, verify they are disambiguated with iconography or other clarifying marks.

Expected Result
Titles must use the Xbox network Friends list as the primary list of friends using Xbox APIs and must not store them in a permanent nature on game servers. The title must disambiguate friends when showing a blended friends list containing both Xbox network and publisher account friends.

Pass Examples

The title uses the Xbox network Friends list as the primary list of friends using Xbox APIs.
The title has an alternate list of people, such as recent players or guild members, who are not positioned as the user's core list.
The title displays a friends list that is filtered to show only friends who have played the title, and, in some situations, to show only friends who are currently online or are currently online and active in the title.
The title displays a blended friends list containing both Xbox network and publisher account friends and disambiguates them with iconography or other clarifying marks.

Fail Examples

The title does not use Xbox APIs to display a list of friends.
The title stores the friends list in a permanent nature on game servers.
The title displays a blended friends list containing both Xbox network and publisher account friends and does not disambiguate them.

XR-124: Game Invitations *

Games that support joinable multiplayer experiences must allow players to send game invitations using the Xbox network platform from within the game to other Xbox network users, including scenarios where cross network players are present.

For information on game invites using the GDK, read the Invites overview.

124-01 Game Invitations

Configuration

2 Xbox profiles each signed into a different device
Device 1 profile A - friends with profile B
Device 2 profile B - friends with profile A

Test Steps

Sign Users A and B into their respective devices.
Both users launch the title.
User A create a game session, locate the in-game option to send invitations, and verify that it matches the required terminology.
User A send a game invite to User B.
Profile B accepts an invite from each of the following areas to join Profile A's game session.
- Anywhere from the initial boot sequence to the initial interactive state
- The main menu (if featured)
- During single player gameplay (if featured)
- During multiplayer gameplay (if featured)
- While the title is in a suspended state on the main menu (if featured and wait at least 30 seconds for the title to fully suspend and for the suspension to interrupt any HTTP request)
- While the title is in a suspended state during single player gameplay (if featured and wait at least 30 seconds for the title to fully suspend and for the suspension to interrupt any HTTP request)
- While the title is in a constrained state on the main menu (if featured)
- While the title is in a constrained state during any gameplay (if featured)
Confirm that both profiles are placed into the game experience together after each invite.

Expected Result
Games that support joinable multiplayer experiences must allow players to send game invitations from within the game to other Xbox users.

Games must use the required terminology for the Invite button.

Profile B should be able to join the sessions hosted by profile A via invites.

Note it is ok for the game to restrict who can send invites to the session (i.e. just team captains in a team game).

The title is not required to take a confirmation of destructive actions approach to this situation. Because the title cannot stop the invitation or join action from being taken, it is not required to ask for confirmation, even if the action will have a destructive effect on the title.

For titles that support cross-platform multiplayer, users must be able to join sessions via invites between an Xbox One Console and PC.

Pass Examples

The title contains an invite button for joinable sessions that uses the correct terminology.
The Player does not receive a confirmation of destructive action message when accepting a game invitation while in-game.
The invite completes but the session cannot be started/launched when required DLC is not present on the console. This is clearly messaged to the player.
Only the host of the game session can send invitations, if it is clear who the host is.

Fail Examples

The title does not contain an invite button in joinable sessions or does not use the correct terminology for the option.
The title provides multiplayer game sessions on Xbox and does not contain any game modes that support game invitations.
After accepting a game invitation the active player is not taken into the game session to which they were invited.
The invite does not complete when required DLC is not present on the console. This is not messaged to the player.

Betas and Game Previews

The requirements in this category apply only to titles classified as betas or Game Previews. For other store policies and for program-specific definitions of open and closed betas, size limitations, duration, pricing, metadata, and offers, reach out to your Microsoft contacts.

Beta and Game Preview titles are subject to a subset of the XRs presented in this document. The scope of this subset is detailed in the Xbox Requirements for Game Previews and Betas page.

XR-117: Beta/Game Preview Notification *

Titles that are in beta stage must have a splash screen or message that is displayed within the experience, after it is launched but before gameplay or application usage, communicating that:

The title is beta/pre-release software.
Some platform features might not work correctly.
Some game features might not work correctly and might crash.

The notification must also outline the support boundaries for the title.

117-01 Beta/Game Preview Notification to Users

Test Steps

Sign in to an Xbox profile and launch the title.
Verify that prior to the user being able to participate in gameplay or application usage that the a message is displayed communicating at a minimum:
- The title is beta/pre-release software.
- Some platform features might not work correctly.
- Some game features might not work correctly and might crash.
- The notification must also outline the support boundaries for the title.

Expected Result
Titles must communicate to users that the title is a beta/pre-release and might not function entirely as expected.

Pass Examples

The user is notified of the title's beta/pre-release status prior to the user being able to engage with functionality within the title.

Fail Examples

The title does not display a message notifying the user of the title's beta/pre-release status.
The user is able to access title functionality prior to seeing a notification from the title regarding beta/pre-release status.

BVTs: Pre-certification testing of the build

The following tests are used to check a title's readiness for Xbox Certification testing.

BVT-01 Build Stability

Test Steps

Launch the title, navigate all menus and enter gameplay
Attempt to reproduce stability issues found while performing other BVTs

Expected Result
The title must not have stability issues or long load times that would block full XR testing of the title.

BVT-02 Matchmaking

Test Steps

Console 1: Select the most basic Xbox game mode and host an Xbox game session.
Console 2: Join Console 1's Xbox game session using quick match. (Repeat this step until the minimum number of consoles has joined in order to start the game session.)
Console 1 and 2: Start and complete the Xbox game session.
Verify matchmaking works and users can enter gameplay in all other supported game modes.

Expected Result
Console 2 should always be able to locate and join Console 1's game session. Both consoles should be able to complete the Xbox game session without being disconnected or encountering stability issues.

BVT-03 DLC

Test Steps

Verify that the downloadable content submitted with the game is downloadable using Xbox Store or an in-game mechanic.
Once downloaded, verify that the content can be easily identified in the game. (A detailed downloadable content description provided with the submission materials helps the certification team to find the downloadable content.)

Expected Result
The downloadable content submitted with the title must be downloadable using Xbox Store or an in-game UI and once downloaded, should be easily identifiable in the game.

BVT-05 Languages

Test Steps

Via the Xbox device Settings application, set the language to English.
Progress into the title.
Verify that the title:
- Does not crash or enter an unresponsive state.
- Does not output any debug on screen.
- Implements localization in all intended areas.
Repeat steps 1-4 for all languages supported by the title.

Expected Result
The title contains all supported languages. The title should also not contain stability issues or debug that are language specific.

BVT-07 Basic Configuration

Test Steps

Launch the title and ensure all BVT feature checks do not require changes to the consoles settings such as Time/Date to work.
Verify that a workaround is not required to reach the main menu of the title.

Expected Result
Basic functionality is expected to be working when a title is entering Certification.

BVT-08 Xbox Store Availability

Tools Needed:

Game published to your devloper sandbox.
Game published to the CERT and CERT.DEBUG sandboxes.

Test Steps

Publish game to your developer sandbox.
Install the title from the Store.
Launch title and enter gameplay.

Important

When submitting to Certification, publish the game to the CERT and CERT.DEBUG sandboxes.

Expected Result
Titles must be able to be installed from the CERT and CERT.DEBUG sandboxes.

BVT-09 Conditions for Resubmission

Test Steps

Reproduce all issues logged as CFRs in the most recent Certification report for the title.
Verify all issues logged as CFRs have been fixed. Any of the issues that reproduce must have an approved exception.

Expected Result
Issues marked as CFR in previous reports must be fixed unless an exception has been granted.

Reach out to your Microsoft contancts for the steps to file Exceptions.

BVT-10 Version Check

Test Steps

Install the title.
Enter My games & apps, highlight the title, press the Menu button and select 'Manage game and add-ons'.
Select File info.
Compare the FullName of the installed product with the Package name listed in the submission documents/kick-off mail.

Expected Result
The FullName of the installed XVC matches exactly with what is documented in the kick-off mail/submission documents.

BVT-12 Partner-Hosted Services

Test Steps

Sign into an Xbox profile and launch the title.
Verify all partner-hosted services are accessible.

Expected Result
All partner-hosted services are configured for testing and all features dependent on them are accessible.

BVT-13 Age Rating Validation

Configuration:

Title must be Final (Base or Content Update).
- Final (Base/Content Update) - Certificates are required for all locales that require a certificate.
- Out of Scope - DLC, In game Content - no testing required.
Submission Materials are available for review.
Access to the product age ratings in Microsoft Partner Center.

Test Steps

Verify the following documents/information is available:
- Submission Validator log for the submission's XVC.
- Age rating declarations in Partner Center.
- Age Rating certificates.
Open the Submission Validator log file and ensure that no warnings or failures for the <component>Manifest-Ratings</component> test are displayed.
- For all titles certified after May 11, 2020: A ratings element must not be present within the AppxManifest.
- For titles certified prior to May 11, 2020: A ratings element is allowed to be present within the AppxManifest.
Open Partner Center to review the product's age rating information
- For each value displayed verify a corresponding rating certificate has been provided which matches the age rating exactly.

Expected Result

All these files must be supplied and must be relevant to this submission type.
All ratings must have a corresponding certificate supplied.
Base final submissions in certification after May 11, 2020, must not have an age ratings element defined in the AppxManifest.
Content updates for titles certified before May 11, 2020, must not add or remove ratings from the AppxManifest except to completely remove the ratings element.

BVT-14 UWP Service Config Validation

Configuration

Title must be a UWP submission.

Test Steps

Sign into an Xbox profile that has not previously accessed the title.
Launch the title.
Ensure that the user is prompted to accept the Xbox account permissions.
At the main menu or front-end menu, run the following command xbdir "XS:\Program Files\WindowsApps\{XVC}\" and search for the 'xboxservices.config' file.

Expected Result
The title's service config must be configured for test.

Pass Examples

The title contains a service config file and new users are prompted to accept the Xbox account permissions.

Fail Examples

A service config file is not present.
A service config file is present but is 0 bytes.
New users are not prompted to accept the Xbox account permissions.

BVT-15 Intelligent Delivery

Test Steps

Obtain the XVC for the title and generate a Chunkinfo.xml file using the packageutil chunkinfo [XVC] > chunkinfo.xml command.
Using the generated chunkinfo.xml establish whether the title supports intelligent Delivery.
If Intelligent Delivery is supported, begin a fresh installation for one of each of the following using the xbapp install /[Chunk Parameter] [XVC] command:
- Language Packs using the parameter /Languages= (switch to another supported language chunk and download an additional Language Pack using the either the system settings or in-title language option)
- Device Specific Content using the parameter /Devices=
- Content Type using the parameter /ContentTypes=
- On Demand Content using the parameter /Tags=

Expected Result
The title correctly installs the expected Intelligent Delivery chunk and no adverse effects are encountered.

Changes in this Release

Date	Version of the document	Description of changes
October 1, 2024	13.1	XR-001 Title Stability: Updated the requirement to Microsoft Store policy 10.1.2. This aligns with the Microsoft Store policy for title stability. Update to XR-046 Display Name and Gamerpic. The four test strings used to verify gamertags display correctly have been updated. The new strings are: สฐ众нь컴퓨 आथाώঙぁヺ øÜêþЯЂў gttest1 Test case 048-01 Profile Settings Usage: Added test step 6 to verify updated gamertags on a second device. Updated "Xbox Live" to "Xbox network".

Bagikan melalui

Certification Tested Xbox Requirements for Xbox Console Games

Introduction

Base Requirements

XR-001: Title Stability *

001-01 Title Stability

001-02 Title Stability After Suspending

001-03 Title Stability After Connected Standby

XR-003: Title Quality for Submission *

003-02 Title Integrity

003-03 Options

003-04 Language Support

003-05 Navigation

003-07 Leaderboards

003-08 Low or High Friend Count

003-14 Local Multiple Players

003-16 Save-Game Compatibility

003-17 Headset State Change

003-18 Headset State Change after Suspend

003-19 Headset State Change after Connected Standby

XR-130: Xbox Console Families and Generations *

130-01 Controller Input

130-02 Save Game Roaming

130-03 Online Segmentation

130-04 Featured Game Modes

130-05 Compatibility Mode

XR-131: Display Mode Support for Game DVR and Screenshots *

131-01 Game DVR and Screenshots

XR-022: Official Naming Standards *

022-01 Official Naming Standards

XR-074: Loss of Connectivity to Xbox and Partner Services *

074-01 WAN Disconnection to Xbox Services

074-02 Direct Disconnection

074-03 Suspend Disconnection to Xbox Services

074-04 Xbox Service Re-connection During Suspend

074-05 Constant Low Bandwidth

074-06 Variable Low Bandwidth

074-07 Dynamic Connectivity Loss

074-08 Pre-Launch Downtime

XR-132: Service Access Limitations *

132-01 Service Access Limitations

132-02 Game Event Limitations

XR-133: Local Storage Write Limitations *

133-01 Local Storage Write Limitations

Online Safety and Privacy

XR-013: Linking Microsoft Accounts with Publisher Accounts *

013-01 Linking Microsoft Accounts with Publisher Accounts

XR-014: Player Data and Personal Information *

014-01 Personal Information

014-02 Data Collection

XR-015: Managing Player Communication *

015-01 User Communication

015-02 Muting Support

015-03 Blocked Users

XR-017: Title Ratings *

017-01 Age Rating Validation

XR-018: User-Generated Content *

018-01 Reporting Inappropriate Content and UGC Text-String Verification

Content Packages and Updates

XR-034: Streaming Install Initial Play Marker *

034-01 Streaming Installation

XR-129: Intelligent Delivery Content Management *

129-01 Intelligent Delivery of Language Packs

129-02 Intelligent Delivery of Device specific Content

129-03 Migration of Device Specific Content

129-04 Intelligent Delivery of On-Demand Content

129-05 Features and Recipes

XR-123: Installation/Unlock of Game Add-Ons or Consumables During Gameplay *

123-01 Installation/Unlock of Game Add-Ons or Consumables During Gameplay

123-02 Installation/Unlock of Game Add-Ons or Consumables as Part of Main Game Package During Streaming Install

XR-037: Dependencies on Content Packages *

037-01 No Content Package Save-Game Dependencies for Base Title

037-02 No Dependencies on Other Content Packages

037-03 DLC Dependency

037-04 Multiplayer DLC

Purchasing from in-game stores and from the Microsoft Store

XR-036: In-Title Pricing Information *

036-01 Content Price Verification

User Profiles

XR-112: Establishing a User and Controller During Initial Activation and Resume *