Valhalla Legends Archive

I wanna know how to program a spoof, There are bots out there that spoof a 0ms lag such as shadow chat, and hacks out there that spoof 56kers at 1green and 2green, So how would i go about finding out were to look to spoof lag, what would be an easy way to program it, and also, if anyone is fimiluar w/ the fake player hack, how the hell did he spoof a player in there, oh well any ideas ty
                             BTW, New name on b.net is FrYDaYs uswest

Neglect a reply to SID_PING and b.net will assign you a ping of -1.

The first SID_PING, that is.

spoofing to 0ms if fairly easy just gotta know how to send &h25 correctly

Quote from: ddxonline on May 17, 2003, 01:14 AMThere are hacks out there that spoof 56kers at 1green and 2green.

I didn't need a spoof hack to make my lag 1 or 2 green when I was on a 56k modem. I actually had a decent service provider. The idea that "56kers lag" isn't always true; my modem handled 8 players in StarCraft just fine.

Try using the same modem to dial up an Israeli ISP and then playing with USA people on USEast.

Edit: Actually, do this with a different modem, one that only works under Windows 98.

*sigh* DSL owns.

Is it really that easy? I thought it had to do with how fast you reply to packet 0x25...

Edited.

It seems that you can send value for SID_PING, instead of just 0x0?

Yes, any value works

Quote from: Tuberload on June 04, 2003, 07:40 PM
Is it really that easy? I thought it had to do with how fast you reply to packet 0x25...

technicly, it does. battle.net calculates ping as the time in miliseconds between when it sends 0x25 and when it recieves 0x25. it sends 0x25 when it finishes parsing 0x50, so if 0x25 is in its buffer already, it will parse it immediately and calculate 0ms between when it sent 0x25 and parsed 0x25.
it's not really a spoof, imo; it's a pseudo-ping.

also, -1 to gosu for giving away the answer

Quote from: Camel on June 05, 2003, 04:57 PM

Quote from: Tuberload on June 04, 2003, 07:40 PM
Is it really that easy? I thought it had to do with how fast you reply to packet 0x25...

technicly, it does. battle.net calculates ping as the time in miliseconds between when it sends 0x25 and when it recieves 0x25. it sends 0x25 when it finishes parsing 0x50, so if 0x25 is in its buffer already, it will parse it immediately and calculate 0ms between when it sent 0x25 and parsed 0x25.
it's not really a spoof, imo; it's a pseudo-ping.

also, -1 to gosu for giving away the answer

gosu didn't, _____ did...

Quote from: laurion on June 06, 2003, 05:28 AM

Quote from: Camel on June 05, 2003, 04:57 PM

Quote from: Tuberload on June 04, 2003, 07:40 PM
Is it really that easy? I thought it had to do with how fast you reply to packet 0x25...

technicly, it does. battle.net calculates ping as the time in miliseconds between when it sends 0x25 and when it recieves 0x25. it sends 0x25 when it finishes parsing 0x50, so if 0x25 is in its buffer already, it will parse it immediately and calculate 0ms between when it sent 0x25 and parsed 0x25.
it's not really a spoof, imo; it's a pseudo-ping.

also, -1 to gosu for giving away the answer

gosu didn't, _____ did...

well -1 to gosu for having the same icon as _____ then