Anti-Cheat Movement Validation Simulator

Player Behavior

Cheat intensity 0%

Detection sensitivity (z) 2.5σ

Anti-Cheat Status

✅ CLEAN

Trust score100

Anomaly z-score

0.00σ

Position error

0.00 u

Flags this session

Kicks

How it works

Every tick, the client reports a new position. The server never trusts it outright — it validates the move against the maximum speed the game rules allow, then feeds the result into a rolling anomaly detector:

maxΔ  = v_max · Δt · (1 + tolerance)
δ     = |pos_client − pos_server|
z     = (δ − mean(window)) / std(window)
flag  = δ > maxΔ  OR  z > threshold

The rolling mean and std are computed over the last ~40 ticks of movement deltas, so the detector adapts to normal jitter (lag, input noise) while still catching a step that stands out statistically — exactly the kind of per-tick movement validation and statistical outlier detection real server-authoritative anti-cheat systems run on player telemetry.

Each flagged tick decays a trust score: T ← T − k·max(0, z − threshold). Clean ticks let it recover slowly toward 100. If trust drops below 20, the session is flagged for review and, in this simulation, the player is kicked and trust resets.

Speed Hack — the client reports displacements several times larger than v_max allows every tick.
Teleport — the client occasionally reports an instantaneous jump to a random point, the classic "position desync" signature.
Server Reconciliation toggle — when ON, the server clamps the accepted position to maxΔ and snaps the client back (the red "rubber-band" line); when OFF, the server blindly trusts the client and the hack visibly succeeds — this is why authoritative servers, not client-reported state, are the baseline of real anti-cheat design.

Client-reported position Server-authoritative position

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.