Learn · modules
What Is No Fall in Minecraft? Module Explained
No Fall stops the server from registering fall damage on your character. Here's how packet cancellation, ground spoofing, and detection actually work.
What is No Fall?
No Fall is a Minecraft module that stops the server from ever registering fall damage on your character. Instead of letting the game's normal damage math run its course, it interferes with the server-side check that would otherwise decide you just ate twelve hearts off a cliff. Jump off a tower, bail out of a fight mid-air, drop straight down a mineshaft: none of it costs you health. It's a small piece of code doing a big job, and it's also one of the more casually detectable tricks in the utility-client toolbox, which is worth knowing before you lean on it.
How it works
The server tracks your vertical position constantly. When it detects a landing after a drop past a certain distance, it applies damage scaled to how far you fell. No Fall's whole job is interfering with that process before the damage lands.
There are three common ways it gets done:
Packet cancellation. The client simply withholds the movement packet the server would use to calculate the fall, so the server never gets the data it needs to charge you for it.
Ground spoofing. The client tells the server it's standing on solid ground when it isn't. No landing means no fall to register in the first place.
Predicted-state manipulation. The client quietly adjusts the position data it reports so the server's own fall-distance tracker never accumulates enough to cross the damage threshold.
Same goal, three different lies told to the server. Which one a client uses shapes how obvious it is.
Is it safe to use?
No, not in any absolute sense. No Fall is a client-side workaround for a server-side check, and that mismatch is exactly the kind of thing anticheats are built to look for. The server expects fall damage to follow from your tracked movement. When your reported position or state stops lining up with the damage that should have occurred, that gap is a plausible detection signal, and a reasonable anticheat will flag it.
Whether it actually gets caught depends on the server and the method. Packet cancellation and ground spoofing tend to leave more obvious traces in movement logs than subtler predicted-state approaches, but none of the three is invisible by default. Treat No Fall as use-at-own-risk, and expect a strict anticheat to catch it more often than a lenient one.
The trade-off
The upside is obvious: you survive falls that should kill you. The downside is equally obvious: you're creating a detectable gap between what you report and what should have happened. Anticheats run through movement logs looking for exactly this kind of discrepancy.
On servers with lax checks, No Fall might not get caught. On servers with active monitoring, it's one of the first things they flag. The safe assumption is that any server worth caring about is checking for it.
FAQ
It stops the server from registering fall damage on your character, so a drop that would normally hurt or kill you does nothing.
Three documented approaches: cancelling the movement packet, spoofing an on-ground state, or manipulating predicted position data so the fall tracker never accumulates enough to apply damage.
Yes. The server expects fall damage to follow from tracked vertical movement, and a mismatch between your reported state and expected damage is a signal anticheats can check for.
No. It's a general module concept that shows up across multiple clients, but the exact method varies by implementation.