#Savage xr system requirements Pc

In addition to providing the Party network's roster, MPSD documents also drive many multiplayer experiences in the Xbox multiplayer ecosystem such as matchmaking, platform invites, recent player lists, and join-in-progress. For examples, see Mapping between Xbox Live User IDs and PlayFab Entity IDs. To achieve this, it is recommended that you store the session's list of Xbox Live users in an MPSD document and translate those Xbox Live users to PlayFab Entity IDs using the Xbox Live Helper library. To recognize Xbox users, you should build mappings between PlayFab Entity IDs and Xbox Live users. For cross-play scenarios, a PlayFab Entity not associated with an Xbox user may represent a user in another multiplayer ecosystem. The PlayFab Entity IDs associated with these objects should be matched with the Xbox users in the MPSD document to recognize which PlayFab Party objects represent Xbox users in the game session. PlayFab Party will advertise remote endpoints and chat controls as they come and go from Party networks. It relies on your game using the Multiplayer Session Directory service (MPSD) to maintain a roster and associate Party network activity with the users in the game session. PlayFab Party does not provide any sort of Xbox user roster. Maintaining a multiplayer session document Refer to the XR-045 technical documentation for further requirements outside the scope of PlayFab Party. For more information, see the documentation about respecting an Xbox Live user's privacy settings and permissions.īy properly making use of PlayFab Party and the Xbox Live Helper library, your game can entirely meet the requirements specified by XR-015 and can meet the relevant communication requirements specified by XR-045. PlayFab Party's Xbox Live Helper library indicates which set of chat permissions should be enabled to match the preferences and privileges of the Xbox Live users currently communicating in the Party session. For more information, see the documentation for chat permissions and muting. PlayFab Party uses an opt-in model of chat communication and, by default, restricts all communications between two chat controls to the set of communications which both participants have enabled. Aligning PlayFab Party with an Xbox Live user's chat settings and privileges The examples presented here will assume use of the Xbox Live Helper library. Use of this helper library is not required but is highly recommended and considered best practice. Honoring Xbox Live service retry policy and service access limitationsĪlongside the core PlayFab Party library, we offer an Xbox Live Helper library which is designed to help comply with Xbox Live policies and, by extension, XRs.

Supporting platform multiplayer join flows Keeping in sync with Xbox Live profile settings Use PlayFab Party invitations to restrict access to networks when cross-play is not allowed Respecting cross-network communication permissions for Xbox Live users Identifying players in a cross-network game session Here we describe best practices for PlayFab Party that will help you comply with these requirements.įor quick reference, refer to the following table which matches PlayFab Party scenarios to the XRs they address: ScenarioĪligning PlayFab Party with an Xbox Live user's chat settings and privileges

#Savage xr system requirements Pc

XRs interact and overlap with the policies that are required to make use of Xbox Live in your game on PC and other platforms. This set of requirements is listed in the Xbox Requirements (XRs for short). If your game is targeting Xbox consoles, it must adhere to a set of requirements to ensure consistent functionality and behavior when interacting with Xbox Live.