hanno capito che c'era un BUG nel calcolo del PING
e l'hanno fixato su AA3.0.8 
(su AA2 c'era già da 3 anni sto bug)
(su AA2 c'era già da 3 anni sto bug)
[programmer]
The internal latency calculation didn't change. This value is converted to an unsigned 8-bit number (range 0-255) for optimized network transmission (needed by all of the other clients for display) thus the number has to be divided by 4 to transmit (max = 1020ms displayed). The client's display needed to be multiplied by 4 to restore and display the correct value (it wasn't). This error was discovered and changed in 3.0.8. Anything above 255*4 (1020) is capped (assume not playable at this latency so display above 1020ms is irrevelant). The previously displayed value (< 3.0.really amounted to a latency index as it wasn't tied to any specific time unit.
[/programmer]
Hopefully this clears up the ping calculation.















