Minecraft anticheat guide
Minecraft Cheat Glossary: KillAura, Reach, Scaffold and More
A plain A-Z glossary of Minecraft cheat names, including KillAura, Reach, Scaffold, Timer, and Velocity, with the signals staff may see for each.
What do the common Minecraft cheat names mean?
Minecraft cheat names describe what a modified client does: aim for the player, attack on its own, reach farther than vanilla allows, place blocks automatically, and so on. Most names describe one behavior, but players use them loosely, so one name can mean different things on different servers. The table below gives a plain definition for each term and the signal a staff member might see in logs or alerts.
A-Z glossary of cheat terms
Each definition is a working description, not a technical specification. A signal in the last column is a reason to review a fight, not proof that a player cheated.
| Term | What it does | What staff may see |
|---|---|---|
| AimBot | Moves the player's view toward a target automatically. | Rotation snaps or steady locks onto one entity across ticks. |
| AutoClicker | Sends attack or use clicks without the player clicking. | Click intervals that are too regular or too fast for the player's input. |
| AutoTotem | Re-equips a Totem of Undying in the offhand after it is used. | Offhand swaps that happen within a few ticks of a totem pop. |
| Blink | Holds outgoing packets, then sends them in a burst. | Gaps in movement or combat packets followed by a burst of stacked updates. |
| Criticals | Fakes the falling state needed for a critical hit. | Critical hit results with no matching fall distance or ground-state change. |
| Elytra abuse | Uses elytra flight to aim, reposition, or time hits unfairly. | Hits during glide with aim lock, firework timing, or motion that does not match the flight path. |
| Fastbreak / Nuker | Breaks blocks faster than the tool allows, or breaks many blocks at once. | Break times shorter than the tool rules allow, or several blocks broken in one tick. |
| Hitbox | Enlarges the area where an entity can be hit. | Hits that land on points outside the target's normal body box. |
| KillAura | Attacks nearby entities automatically, often across several targets. | Hits on targets the player never faced, or fast switching between several targets. |
| Reach | Hits entities from farther away than vanilla survival range. | Hit distance from the player's eye position that is larger than the vanilla limit. |
| Scaffold | Places blocks under the player automatically, often while moving. | Placements on a timing or angle pattern that a human would not produce. |
| Speed / Fly | Moves faster than allowed, or moves without gravity or ground contact. | Horizontal speed or vertical movement that the normal game rules do not allow. |
| Timer | Speeds up or slows down the client's tick rate. | Packet cadence that is faster or more regular than the normal tick rate. |
| TriggerBot | Attacks automatically when the crosshair is on an entity. | Attacks that land at the exact moment a target enters the crosshair. |
| Velocity / AntiKnockback | Reduces or cancels the knockback a hit should cause. | Little or no movement after a hit, when the server sent a knockback update. |
Which names does the FairPlay reference cover?
FairPlay's check reference lists check families for AimBot, AutoClicker, KillAura, Scaffold, FastBreak, Elytra, Hitbox, AutoTotem, Criticals, and Timer. Those names appear in the reference, so their check families are documented there.
The reference does not name separate checks for Velocity, Blink, TriggerBot, or Speed and Fly. FairPlay focuses on combat and related player actions rather than general Fly or Speed. Treat those rows as outside FairPlay's documented scope unless the current reference says otherwise.
How to read a cheat term in an alert
An alert names a check, not a verdict. Use the term as a starting point for review, then compare the alert against the fight, the player's ping, and the server's own rules.
What we have not verified
This glossary does not rank cheat names by danger, and it makes no claim about detection rates or false positive rates for any term. The signals in the table are things to review, and the definitions describe behavior in general terms. Check your server's exact version and plugins in staging before you rely on any signal for enforcement.
FAQ
Is a KillAura alert the same as a Reach alert?
No. KillAura is about who the player attacks and when, while Reach is about how far away a hit lands. A single fight can trigger both, so review the target list and the hit distances separately.
Why does the glossary list Velocity and Blink without a FairPlay check?
The FairPlay check reference does not name separate checks for those terms, so this glossary does not attribute them to FairPlay. Look at the current reference for the checks your version exposes.
Can a legitimate player trigger a Timer or AutoClicker signal?
Yes, possibly. Lag spikes, unusual input devices, and client settings can make packet cadence or click timing look irregular. That is why the review steps ask you to check ping and context first.