Minecraft anticheat guide
Snap, Jolt and Reset Aimbot Checks Explained
What FairPlay's snap, jolt and reset aimbot checks read in rotation jumps, how legitimate flicks and respawns look, and how staff should review alerts.
What do snap, jolt and reset checks watch?
These six checks watch for sudden changes in view angle. A snap is a large turn that arrives in one or two updates. A jolt is a burst of outlier rate changes. A reset is a view change that happens when the target or the player's state changes. Together they answer one question: did the view jump in a way that human hands on a mouse rarely produce?
The family covers Head Spazz, Non Linear Rotation, Rate Jolt, Rotation Reset Continuity, Rotation Snap and Snap Lock. Each reads a different part of the same stream. Some look at one large move. Others look at how a run of moves behaves over a window, or at whether the view settled onto a point afterward.
An alert from this family is a statement about motion shape. Fast play can produce the same shape, so the alert is only a starting point.
Which cheat behavior do these checks look for?
The family targets a view that moves from one place to a target in an abrupt way and then holds still. Snap Lock is the clearest example in code terms. It watches for a peak in yaw movement followed by a settle onto an offset that stays steady. Rotation Snap looks at large single moves that do not match the player's recent motion.
Head Spazz looks for the opposite pattern, an unsteady view that jitters around a mean. Non Linear Rotation fits a simple relationship between yaw and pitch changes and flags runs where the relationship breaks in a repeated way. Rate Jolt counts outliers and duplicate rates in a window and reads a strong synchronized repetition as the signal.
Taken together, the family looks for a view that behaves like a controller rather than a hand. Staff should keep that wording in mind, because hands and controllers are not the only things that can move a view quickly.
Why do fast legitimate players trigger these checks?
A flick is a fast, deliberate turn to a new target, and skilled players use it constantly. A flick looks like a snap in the data. The snap checks are built around that overlap, so a clean flick followed by a clean hit is not a cheat pattern, even when the single move is large.
Several resets are normal game events. A respawn, a teleport, a vehicle exit or a forced view change from the server can move the view sharply. The reset check reads the view with the target and the state in mind, and it is designed to treat a view change tied to a teleport or respawn differently from one that happens in combat.
Lag is the other common cause. Late or bunched packets can make a smooth turn arrive as a jump. A player with a poor connection can produce a snap-shaped record without any input problem at all.
How should staff review a snap or jolt alert?
Look at the record before the jump, not only at the jump. A snap that follows a long quiet stretch is different from one that follows a hit, a teleport or a burst of lag. Check the timing of the alert against the combat log and any recording of the fight.
The table below sets out the usual context for each family member and the first question to answer. Use it as a checklist rather than a verdict.
| Check group | What the alert suggests | First question to answer |
|---|---|---|
| Rotation Snap and Snap Lock | A large move followed by a steady hold on an offset | Was the player flicking to a visible target in a recording? |
| Head Spazz | An unsteady view around a mean | Was the player moving the camera while sprinting or taking damage? |
| Non Linear Rotation and Rate Jolt | A repeated break in the expected motion pattern | Did lag or packet bunching occur in the same window? |
| Rotation Reset Continuity | A view change tied to a target or state change | Was there a respawn, teleport, vehicle exit or forced view change? |
What should you tune only in staging?
The snap family relies on timing windows, buffers and the size of moves that count as large. Each of those controls changes how often a flick or a respawn is read as a snap. Tune them only with a replay set that contains known flicks, known respawns and known lag, and keep the replay set unchanged between runs.
Teleport and reset handling should be tested against your own server features. If your server uses plugin teleports, custom spawn systems or vehicles, include those in the replay set, because a snap check that never saw them will treat them as new behavior.
What does a snap alert not establish?
A snap alert does not establish that a player used a particular tool. It establishes that the view moved in a way the family is written to flag. The same motion can come from a fast human, a laggy connection or a server-side view change, and the record alone does not always separate them.
Keep a note of your reasoning. Record whether a recording was available, whether lag was present, and whether a reset event happened. The note is what lets another reviewer follow your decision later.
FAQ
Is a flick the same thing as a snap?
In the data they look alike, which is why the family exists. A flick is a deliberate turn to a target. A snap check flags a large turn that does not fit the surrounding motion, so context decides the reading.
Why does a respawn sometimes trigger the reset check?
A respawn or forced view change moves the camera without any input from the player. The reset check reads those changes with the state in mind, so a respawn should be reviewed against the server's own events before any action.
What is the quickest way to rule out lag?
Compare the alert timestamp with the player's connection record for the same minute. Bunched packets or a stall right before the jump point to lag rather than input.