Ping spoof

[UserLoser]

i was talking to brew in case you failed to notice.

Oops

[squeegee]

o NUUUUUUUUUUUUUUUUUU!!!!!!!!!!!!!!!!!!!!!!

[brew]

What l2k-shadow said to me made absolutely no sense. Why would I not know what an unsigned integer is and then say something about it... ? 
My point was that, even though blizzard (most likely) intended the ping value to be unsigned, but since the sheer number of bots which interpret the ping as a signed integer is so great, and also nowhere does blizzard show the actual value of the ping, it should be a signed value. For consistency's sake, i believe userloser should have said "-2 ping". I'M SO SORRY you all got flustered for me pointing out that just about everybody inteprets the ping as a signed value where userloser said otherwise.

[squeegee]

because you do that often

[Kp]

You all missed my point. ping is supposed to be a signed 32 bit long.

Without any of us having seen the specification, we've just kind of treated it that way.  There's not really a way to know for sure, other than calling Blizz and saying, "wtf?"

That's not entirely true.  Recall that real clients control the number of lag bars shown based on the value in the latency field.  To do that, the client must compare the latency field to certain predefined values to decide whether to use 0, 1, 2, 3, 4, 5, or 6 bars.  By examining the jump instruction used for that comparison, you can tell whether the corresponding source code was treating that field as signed or unsigned.  It is reasonable to guess that the field had the same signedness throughout the code, so if it was signed in the comparison, Blizzard probably wrote "int latency;" in their definition.  If you want to cheat, just check how many bars someone with -1 latency has.  If they show up as 6 bars, then the -1 is being treated as unsigned, and 600 < 4294967295, so it goes with 6 bars.  If they have no bars, then the -1 is being treated as signed, and -1 < 16, so the client chooses to show no bars.  The 16 and 600 are from memory, they may be off slightly.

[Barabajagal]

-1 = 6 bars = Unsigned.

[MyndFyre]

-1 = 6 bars = Unsigned.

Uhh, the very nature of it being "-1" precludes it from being "unsigned."

[Barabajagal]

... I'm using -1 because that's what everyone calls it. The clients handle it as an unsigned value, though.

[Barabajagal]

Well, I finally got around to it and waited 11 hours. Got a ping of 40,000,000 on East. I guess I'll have to remove that limit from my bot. Yay spoofing.