Bad ping

[Prodigy]

It has been a long time since I've worked with battle.net, but wasn't there a packet that was sent to the client and the client responded to, that determined the user's latency? It'd be logical to respond to this as fast as possible to obtain the fastest latency possible. If I recall you could ignore this packet completely and that'd result in the -1 latency.

Like I said, it has been awhile. Maybe it's no longer this way?

Not responding causes 0 ping I believe. But I am already responding to the packet as fast as my connection can. It's not even going through my parser; it's going straight from arrival back to the socket.


edit--

'Okay, so I guess it comes down to 0x51. I am responding to 0x25 as soon as I get it, so that's not the problem. But... when i slow down the build of 0x51 (if I pause it before I send it) I get horrible ping time. I'm at a complete loss right now... Blah.

Not responding to 0x25 gives you a -1ms ping.

Also, last time I had troubles with high pings using local hashing was because my computer wasn't fast enough so it would take ages to build the 0x51 response thus giving me a high ping.
My 2 cents.