A frequent multiplayer scenario is that you have:
- some measure of skill (e.g. Elo-score)
- a match-making queue that matches based on that value
While there's a number of ways to store information per player in PlayFab, using a Statistics value seems like the best solution, since that exposes the value in leaderboards.
When configuring a matchmaking rule and setting Attribute Source to Player Entity, it would be great if we could reference that Statistics value. Matchmaking attributes are currently limited to Player Objects, however.
A workaround to get the best of both worlds (leaderboard-indexed value and matchmaking rule support) is to modify the cloudscript methods to always store the value both as a Statistics and Player Objects value, of course. Based on our experience, however, this substantially increases processing duration, often nudging the call to over 1000ms, leading to parts of the call not being executed (sometimes desyncing the values as a consequence).
There does not seem to be an optimal solution to this issue yet. Thus, it'd be great if Statistics values could be exposed to the matchmaker.