Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Ping Pong allows for a very easy and simplified version of testing your ping on EE.
Ping Pong works by testing how fast you can send and recieve a "b" message, (just to stay on the safe side).
Once your ping has been tested, you can see the number, and use it as you wish.
You could use this to see how fast your upload speed should be (your ms for placing blocks).
Well, If you feel like testing your ping today or any other time, you can easily just download Ping Pong - The Ping Tester.
Offline
Does this have functionality for sending more than just a single message?
Obviously a single message isn't that reliable, since your latency can easily vary 10 ms (tested with 100 pings to the player.io website a couple times), meaning a single ping gives no guarantee it's your actual average, worst or best.
Offline
If you're testing latency using packet return times, you won't be very accurate. As discussed in a certain thread you may have got this bot idea from, incoming packet "latency" varies by more than 0.1s, so if you're giving receive times to the millisecond I will crucify you. Even an average with much greater than 0.1s precision won't be that useful, as it's just an average.
Do note that I tested that precision using purple switches ("ps") [and no lag], so it may be different for blocks. Do your own tests, but remember that the results are only accurate for you.
Can you ping PlayerIO servers, and get some results that way?
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
Personal opinion: precision below 1ms is pretty useless. A human can't really notice below 8-16ms (60Hz) anyway.
Offline
The `time` message may be of more use...
github.com/Tunous/EverybodyEditsProtocol#sm-time
and github.com/Tunous/EverybodyEditsProtocol#rm-time
Offline
[ Started around 1734488808.6425 - Generated in 0.039 seconds, 18 queries executed - Memory usage: 1.44 MiB (Peak: 1.56 MiB) ]