08-18-2005, 04:18 PM
Gnollguy,Aug 18 2005, 05:21 AM Wrote:It's possible. However my client clock was rock solid on my old motherboard that was replaced in late March early April, and I was hit with the charge bug on that system as well. But yeah it is a client and server positioning issue and likely hood of them being related are high in my mind as well.
The devs have also acknowledged that there is a charge bug as well. I think they claimed it was fixed in 1.6 (I'll have to dig through the warrior forums again) and I haven't actually been hit with it in 1.6 that I recall.
Still working on my test methods. They would be easier for me if I were running WoW on a *nix box. :)
[right][snapback]86466[/snapback][/right]
This might be a little bit simpler. Perhaps the packets you're sending are timestamped by your machine. Since the server compares it's time to your timestamp, it tries to speed you up to match you accelerated clock. That seems oversimplified, but I'm sure the principle lies in there somewhere.
It would stand to reason, based on how I've seen them deal with hacks in the past, that all the packets are timestamped, but the game is only designed to account for hour differences, IE time zones. Small differences, in terms of seconds also don't matter. There's also a built in detection system against packet thieves, that would send too many, or too few packets to the server, essentially causing you to warp around. But I don't think it was designed to account for larger differences inbetween the two extremes.
Just a thought. I can't figure out any other reasoning why your system clock would change your gameplay, unless the server relied on information it was sent about your system time.
Turambar - Fury Warrior - Twisting Nether
NenyaAdamant - Shadow Priest - Proudmoore
Lum - Shadow Priest - Stormrage
TheLuminaire.net
NenyaAdamant - Shadow Priest - Proudmoore
Lum - Shadow Priest - Stormrage
TheLuminaire.net