It basically goes berserk. Once a second.

I've rewritten it with roughly the one frame (17-25ms)+/-a frame of the main loop precision in time (with no accounting for jitter.) but when testing the original detection code I could basically zip around at 2-3x the default rate and have no alert triggers as long as I kept my update rate low. 

I'm wondering why it's triggering at all right now. 

Meridian59 <notifications@github.com> wrote:

>In kod/object/active/holder/nomoveon/battler/player/user.kod:
>
>> @@ -2902,18 +2902,7 @@ messages: > % got a move packet, then adjust for last movement time. > % Also make sure we don't go too far negative. > piMovesCounter = (piMovesCounter + 1) - iDelta; > - piMovesCounter = bound(piMovesCounter,-MOVEMENT_DELTA_LAG_THRESHOLD,$); > - > - % Check for cheating by sending more move packets than allowed. 
>
>While I agree that this check may have a lot of false positives, it certainly does detect some speedhacking. Can you say more about why you're deleting it? Is it triggering a lot in your tests?
>
>—
>Reply to this email directly or view it on GitHub.￼
>