question

Usually the matchmaking process allocates a game server according to the queue’s config. Integrating matchmaking with local server, including spinning server instances, returning server ips & ports back to the Matchmaking flow, etc., is rather complex. It is better to test matchmaking and local multiplayer server separately, then deploy the build on PlayFab.

The information passed to the game server from matchmaking process contains:

• SessionId - The SessionId for the server will be equal to the MatchId for the match.
• InitialPlayers - This value is set to the list of members in the match. The list of players can be read in the game by using the GSDK.

• You could refer to https://docs.microsoft.com/en-gb/gaming/playfab/features/multiplayer/matchmaking/multiplayer-servers#information-passed-to-the-game-server for more detail.

Following this document: Locally debugging game servers and integration with PlayFab, there should be a MultiplayerSettings.json file in the local debugging toolset. The parameters that matchmaking passes to the server can be modified in “SessionConfig” property of this file to test the local server. This helps you debug your local server in the same context as the one allocated by Matchmaking on the cloud.