Maybe we could instead have an API that tells us what the location will be of the server the client will connect to? Maybe we could have an API that estimates a player’s latency to a server given the server’s JobId?
4 Likes
If they have some other solution in mind that’s fair enough, though it’s been a long time coming.
Any kind of transparency that Roblox can give us on this would be greatly appreciated.
4 Likes
Agreed. As long as there is a solution in the near future then it would be great. It only creates more problems for Roblox not to have a built-in solution by themselves to combat this problem even though we have had different APIs to determine a server’s region (which now are extremely inaccurate).
1 Like
I talked with @SuperPat77 and some other matchmaking staff about this at RDC; unfortunately, the consensus was that it’s a privacy concern to allow this.
If you can get someone’s estimated ping to a server, and you’re able to narrow down where a given server is, you’d theoretically be able to narrow down a user’s approximate location by triangulating their position based off their ping to several different servers.
They did say they’re looking into other options though, including just exposing the server’s region
3 Likes
Localization Service exist but someone needs to make an API to get player region based on their country code