Rubber Banding / Speed Hacking - A Special (Unplanned) DevChat - 10/14/09 2am EST

[odwill]

This is something that is not going away but it isn't just put up on TC and forgotten.

Originally Posted by cRush

The future:
We have already outlined a new algorithm that should hopefully correct for lag, while still keeping speed hacking ineffective. We are testing it internally to make sure it doesn't make the situation worse before pushing it to TC. If it tests well internally, we will move it to TC where we hope it will hold up. If it doesn't, we will reinstate the old protection, and try again.

Taken from here.


Can we please stop doing this? -->>>

[Colt-556]

Originally Posted by odwill

Can we please stop doing this? -->>>

Depends, is the fixed version on the TC? Is everyone still suffering from a broken anti-hack? If so, then no, we can't stop. As I have said, if it's being worked on, GREAT, but until it's ready remove this broken one. There's no excuse to keep it up and make the ENTIRE community suffering, the very process of testing itself suffering from this. It aint like you have to worry about people speed-hacking in the time before the revised version is finished. Cuz even if they do, two words (or is it three?) DATABASE WIPE. So the hackers getting a couple days/weeks of freedom really doesn't matter, since in the end everything we do will be wiped. However in that time everyone else will be able to move normally. I have yet to see any sort of justification to keep the broken code on the server until the revised code is finished.