This may come off as an unusual / unnatural request, but as I am coming from an alternative Open source platform, this is something that I didn’t consider an issue until now.
For example, It would be nice to be able to test the matchmaking flow completely on local machines and get all the local debugging advantage.
Hey, I understand the need, but this is not currently supported and not part of the roadmap. I’ve heard similar feedback though, so we’ll keep it in mind for future planning.
What’s the part that you would like to have locally the most? The Matchmaker itself (this would require that we work on an emulator), or the ability to use the Matchmaker without Game Server Hosting (to run everything but the Matchmaker locally, but still use the same calls to the current cloud-based Matchmaker)?
To me, either solution would be good. If the emulator can provide more debugging insight, that would be a better solution (e.g. if my client is getting back a MatchmakerPollingResult.MatchAssignmentError from the matchmaker, it would be good to have some more info provided by the matchmaker emulator).