[4.1.0a] Speedhack - NOPing jump now causing a d/c?

[Tanaris4]

Is anyone else having this problem now? There was a jump you could simply patch within CMovement_Execute (the first jump) and speedhack would be enabled.

Now, whenever I do this (on OS X), it's an instant disconnect.

Was just checking if this was occurring for windows users as well.

Thanks!

[DarkLinux]

Take a big guess, lols...

[Xelper]

Yes it effects Windows too, this post is all speculation but here are my thoughts:

Blizzard enabled a change with the server restarts on Tuesday that is causing this to disconnect, no client patch necessary. This was done the week before to instance servers. It could also be they just flipped some switch server side that enables new movement code client side, but id bet its probably server side at this point. Maybe they opted for disconnects at this point rather than bans since they aren't sure if it will only stop speed hackers or if it may be triggered by other things, and they would feel pretty silly if they started banning normal users. I'd imagine playing around with something as important (and complex) to the game as their movement code is going to move ahead with caution.

I'd proceed with caution, as unless this was a complete fluke and they were just optimizing their movement handling code they have shown their hand and are probably seeking server side detection and/or prevention.

[DrakeFish]

The fix is obviously server-side. They (finally) decided to do something when you send a negative amount in a Time Skipped packet. This speedhack was used by a lot of free multi-hacks that were just copying eachothers methods without really know how it worked (If you don't feel like I'm talking about yours then I'm probably not talking about yours ). I don't really get why it wasn't fixed before.

[DamonT]

The fix is obviously server-side. They (finally) decided to do something when you send a negative amount in a Time Skipped packet. This speedhack was used by a lot of free multi-hacks that were just copying eachothers methods without really know how it worked (If you don't feel like I'm talking about yours then I'm probably not talking about yours ). I don't really get why it wasn't fixed before.

They probably changed the skipped time datatype from long to unsigned long so it won't accept negative values anymore

[LogicWin]

They probably changed the skipped time datatype from long to unsigned long so it won't accept negative values anymore

Just a question, why would negative values to increase your speed? What would the negative value repentant then?

[namreeb]

The value is not a measurement of speed, but of a time offset between the client and the server. A negative value implies "back in time" aka faster speed.

[schlumpf]

They probably changed the skipped time datatype from long to unsigned long so it won't accept negative values anymore

How exactly should this work? int -1 as uint is max uint. If they do it, they would just check if its <0. If they'd change the datatype, there wont be negative numbers anymore they can check against.

[Norus]

Just a question, why would negative values to increase your speed? What would the negative value repentant then?

http://www.mmowned.com/forums/world-...ml#post2076263