Idea

Markus Henschel avatar image
Markus Henschel suggested

Query deployed regions of a multiplayer server 2.0 build connected to a matchmaking queue from the client

When the client wants to join a match on a dedicated server hosted on playfab by multiplayer servers 2.0 it needs to supply latencies for regions so matchmaking can select the region with the best ping. Currently the client cannot know what regions a build is deployed to. So it has to have some list of regions compiled in so it can ping them. But if a new region is added the client has to be changed/redistributed.

It would theoretically be possible to allow the client to call the serer API but this would give the client more control than desired (it could start it's own servers!).

Currently the best option seems to be to write cloud script to allow the client to make a query of the regions of the build a matchmaking queue is using.

Since the region selection rule is mandatory when using multiplayer servers 2.0 with automatic allocation from matchmaking it would make a lot of sense to add a query to the matchmaking client API that gets the list of regions a build connected to a matchmaking queue is deployed to so the client can ping the right regions.

Matchmaking
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Comment

·
brandon@uprootstudios.com avatar image
brandon@uprootstudios.com commented

@Markus Henschel We use Title Data to hold a JSON list of our active regions. Every time the clients wants to use Matchmaking, we just send the latencies for the regions in the Title Data.

1 comment
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Markus Henschel avatar image Markus Henschel commented ·

Thanks. Sounds like another workaround that can be used. You then have to make sure the title data is always matching the actual deployment. This can be solved for sure but I think it would better if clients could query the information directly from the queue/build.

0 Likes 0 ·

Write a Comment

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Your Opinion Counts

Share your great idea, or help out by voting for other people's ideas.