​

XR-045: XBOX Network and Account Privileges

​

FMA scenario severities

​

045-01 Respect User Privileges

• These scenarios are laid out as the [name of the privilege] as shown in the XBOX settings, and the [privilege setting] tested. For example, [Others can communicate with voice, text, or invites][Block].
• [Windows] Titles aren’t required to show system level error messaging, but must contain all the relevant information within their in-title messaging to highlight the privilege conflict.
• ‘Cross-play’ is defined to mean network to network (for example, XBOX network and PlayStation) and not Platform to Platform (XBOX Series and Windows).
• At a high level, UGC can include (but isn’t limited to):
  • Player-customizable text fields, for example: player nicknames and bio info, character names, weapon names, clan tags, and text posted on signs/boards.
  • Player-created or uploaded images, videos, and GIFs.
  • Player-created maps, terrains, worlds, player emblems, textures, models, assets, liveries, skins, drawings, sounds, and character behaviors: emotes, animated gestures or actions, body part physics.
  • Player-created in-game photos, videos, and GIFs (excludes content uploaded to the XBOX network, for example XBOX Screenshots and Game clips).
  • Note — titles that implement in-game capture features with limited editing capabilities or player customization (for example, photo filters, cropping, resizing, and similar features) and are less likely to produce objectionable content might qualify for exemption.
• Examples of what isn’t considered UGC:
  • Prefabricated in-game player responses governed by the developer (for example, “Hi” or “GG”).
  • Player avatar emotes designed by the developer.
  • Recordings or ‘ghosts’ of a player’s game activity.
  • Scenarios where players can minimally customize developer created and vetted content within strictly established parameters. For example, players changing the color or size of a player emblem isn’t UGC. However, allowing players to layer multiple emblems could result in an unintended outcome and is considered UGC.
• Text-based UGC also needs to adhere to XR-018 standards.
• In-title custom messaging can be implemented to invoke after, but not instead of, system UI messaging (for example, two messages might show — system UI and then in-title).
• System UI error messaging is required for all titles that didn’t pass certification as of June 1, 2017. All new titles submitted after that date must adhere to this requirement. Titles certified before June 1, 2017, including new or derivative SKUs based on a parent title certified before that date, may continue to use in-title custom messaging or no messaging unless otherwise specified in a certification scenario.
• The ‘You can join cross-network play’ privilege is overwritten by the setting enabled for the ‘Others can communicate with voice, text, or invites’ privilege.
• When the ‘See content other people make’ privilege is blocked, the title must not allow the user to access another user’s UGC. Appropriate error messaging must be displayed as requirement for a pass.
• The user might be unable to access unrelated online areas (Leaderboards) when the ‘You can join multiplayer games’ privilege is blocked.
• [You can see and upload community creations] Custom usernames and clan/squad/guild names must adhere to XR-018, however aren’t required to be obfuscated with the privilege blocked.

​

045-02 Respect User Privileges — XBOX Family

• No current FMA Notes to consider.