Anti-Knockback and Velocity Cheats in Minecraft Explained

What do anti-knockback and velocity cheats do?

An anti-knockback cheat reduces or cancels the movement a hit should push a player with. When the server sends a velocity update after a hit, a cheating client ignores it or applies only part of it. The player keeps their position in the fight and gains an advantage in the exchange.

Staff spot this by comparing the velocity the server sent with the movement the client reported afterward. A large gap between those two is the signal to review.

What does knockback cheating look like?

Knockback is a sequence, so the signal is in the order and size of the movement after a hit. The table compares a normal recovery with a pattern that deserves review. A single hit rarely settles the question, so look across several hits in the same fight.

Why does custom knockback complicate the review?

Custom knockback changes the baseline. A server that tunes knockback below or above vanilla will show smaller or larger displacement for legitimate players. Vanilla numbers then flag honest players, and a cheat can hide inside a profile that looks unusual anyway.

Read the custom knockback article for the full effect on other checks. For velocity review, record the knockback profile version next to every alert, so you compare each flag with the profile that was active at the time. A profile tuned for heavier knockback also shifts which movement counts as normal, so compare samples against that profile's own data. Several fights under the same profile give a better baseline than one fight.

How should staff review a velocity alert?

Use a fixed sequence so reviews stay consistent. Each step narrows the cause before you enforce anything. Keep the same order for every alert so two reviewers reach comparable findings.

• Record the knockback profile version and the server version active during the alert.
• Pull the velocity updates and movement samples for the flagged hits, with timestamps.
• Check transaction and acknowledgement order, because a late update can look like a cancelled one.
• Check ping, water, cobwebs, ladders, and teleport corrections that change displacement on their own.
• Repeat the comparison on a legitimate test client with the same knockback profile, then decide whether the pattern holds.

How do knockback cheats differ from lag and teleports?

Lag and teleport corrections also change displacement, so they are the most common source of confusion. A correction usually arrives as a server-side position reset with a visible jump. A velocity cheat shows a smooth path that ignores the expected push.

Vertical knockback is the easiest signal to misread. Stairs, slabs, and low ceilings can block a lift, so check the block layout before you count a missing lift as a signal.

Ping also shifts when the client reports movement, so compare samples from the same time window. If the displacement gap closes when the player's latency drops, lag is the more likely cause than an ignored update.

What we have not verified

This article does not claim that any anticheat detects anti-knockback or velocity cheats accurately. It makes no statement about detection rates, false positive rates, or the thresholds any check uses. Thresholds depend on the server's knockback profile, so set them from your own staged observations rather than from another server. Re-test after each server update, because knockback handling can change across versions. The table is a review aid, and no single row is a threshold.