Is having a a "dummy" region selection rule the best practice if we use a single region?
My game, although realtime, isn't that latency sensitive (it's pseudo turn based), so I think it makes the most sense to just have a single region for deploying servers.
However, the dashboard forces me to use a region selection rule. I have come up with this 'dummy' region selection rule; is this the recommended approach for my use-case?
Best Answer
When testing without doing QoS, we just pass in a fake latency to the matchmaker, like
Latencies = { EastUs = 50}
Thanks - I'll try doing something similar, except also use this in production. I have a follow-up question but it's not necessarily related so I'll ask in a separate question :)
