We have properly set up backfill and matchmaking tickets but are not seeing backfill tickets take priority over regular matchmaking tickets. The documentation says
Backfill tickets are given priority during searching. This reduces fragmentation of the player base.
https://learn.microsoft.com/en-us/gaming/playfab/features/multiplayer/matchmaking/backfill-tickets
Is this guaranteed for all backfill tickets? We saw today that many players were put into a regular matchmaking ticket before the backfill ticket.
We specifically have the following rules. We are treating the server as a user as well.
1. RequireServer
- Type: Match total rule
- Attribute Source: User
- Attribute path: $.IsServer
- Min: 1
- Max: 1
2. Maximum Players
- Type: Match total rule
- Attribute Source: User
- Attribute path: $.IsPlayer
- Max: 10
- Expansion type: Custom
- Seconds between expansions: 10
- Min match total overrides: 10;9;8;7;6;5;4;3;2;1;0
One hunch is that adding the "0" in the "Min match total overrides" is making playfab disable that rule. But we're not sure.
Can we have clarification of the implementation of matchmaking for playfab?
- Can we guarantee that backfill tickets always have higher priority than regular matchmaking tickets and is that treated as a special case or is it just a weight somewhere in the matchmaking system?
- Any idea on how we can account for the regular matchmaking ticket having taken precedence in the example above?
- Would passing in "0" to the "Min match total overrides" be equivalent to passing "null"?
Thanks