I'm not sure if such a ping estimate would really be useful. That would also require the masterserver to ping all the servers. From the heartbeat https requests you probably don't get useful info about the ping.
16:46
There is at least a serverlist.json which stores the ips from the masterserver
16:47
The serverinfo from each server would be too outdated when it's loaded from a file. Maybe the name but everything else would not be useful anymore
@redix such a ping would give you an idea how far the server is and the heartbeat from the server can include a timestamp, atomic clocks are fairly accurate and modern cpus don't drift that much
17:03
but yes it could be wildly inaccurate as that's not how routing works
on a different topic, where I wanted to change the field of view based on player ping(edited)
19:34
generating a new token for every new communication also seems bad, would need to have a server per IP limit, as people would be able to fake request a registration forcing the server to generate tons of tokens making is kind of the single point of failure(edited)
How do you know so many things about a protocol that doesn't exist yet?
@Learath2 if you layout a concept of anything you try to understand the pros and cons in order to improve your concept, this is normal business planning
@Assa well yes, but we didn't even lay out anything about the http master server protocol, besides the 2 PoCs ever made and only one of those are public
~ (edited)