Why does getting matched with a backfilling ticket create a brand new match id? surely it should get the existing match ID for the match the backfill ticket was created for?
is it possible to get the existing match ID from somewhere? The server provider we are using which has an integration with playfab uses the match ID as the token to resolve server information from, which renders backfilling completely impossible with them if we get a new ID every single time we are backfilled in.
Answer by Sarah Zhang · Apr 03, 2020 at 08:21 AM
>> Why does getting matched with a backfilling ticket create a brand new match id? surely it should get the existing match ID for the match the backfill ticket was created for?
Yes, when the backfill ticket match with other tickets successfully, a new match Id will be created. Even if the players would connect to the existing server via the same server details, it’s still needed to create a new match Id to distinguish these two matchmaking operations.
>> is it possible to get the existing match ID from somewhere?
Only when you enable the multiplayer server allocation for this queue, it would be possible. Although PlayFab would create a new MatchId for the new matchmaking operation, backfill tickets do not trigger Multiplayer Server allocation. It means if you are using the PlayFab Multiplayer Sever2.0 and integrate it with Matchmaking, you can get the original MatchId from the game server. Because the server session’s SessionId is equal to the original MatchId, and it would not be changed to a new one when the server backfill tickets match other tickets successfully.
Could you please tell us are you using an external server provider? And what is your detailed application scenario? So we can try to give possible suggestions for you.