Clean Slate Glitch?

@Stereo

Checking monster's HP is pretty linear, it goes from X to 0. Checking attack counts is a bit trickier IMO, as you need to identify the period where someone attacks frequently. It is analogous to the picking the highest sum sub-array from a given array. IIRC the best cost of that is nlog(n).

Just bin it into 10 second intervals, then if 4 in a row add up to more than 60 attacks (or whatever applies to the class), disconnect them. Each time you hit the 10 second mark, subtract the oldest bin from the running total, set it to 0, and start filling it again. It's only a couple operations more than doing b++ every attack.

Even if you're lagging, you disconnect after ~30 seconds anyway, so there's no way to accidentally lag and then send 70+ attacks at once.


The real problem on wz edits is how little the client actually verifies. I mean a couple patches ago people were patching the wrong map info, and it didn't even realise. There's just a version ID in the file, and if it's right then it's good to go. If it actually checked that each number it pulled was matching the server's (eg. send a packet describing the numbers of each skill the first time you use it after logging in) then it would make it a lot harder for people to edit the WZ files and get away with it. Spoofing encrypted packets is not as easy as editing the right bytes in a local file.