Learn · modules
What Is Fake Lag in Minecraft? Packet Delay Explained
Fake Lag delays a player's movement packets and releases them in a burst, desyncing their position from the server. Here's how it works and why it's bannable.
What is Fake Lag in Minecraft?
Fake Lag is a combat module found in some Minecraft cheat clients that holds a player's outgoing movement packets instead of sending them on every tick, then releases the whole queue at once. A normal connection reports position constantly, so the server's copy of where a player stands tracks their real position closely. Fake Lag breaks that link on purpose: the player keeps walking and fighting normally on their own screen while the server is stuck holding an older position, and when the queue finally flushes, everyone else sees a stutter or a short teleport instead of smooth movement.
The appeal is the gap it creates. While packets are held, the server's position record falls behind reality, and attacks aimed at that old position miss the real you. When the burst lands, you snap back to where you actually are, and the desync closes.
How Fake Lag works
A vanilla client sends a movement packet roughly once per tick, so the server's record of a player's position rarely falls more than a fraction of a second behind reality. Fake Lag intercepts those outgoing packets, queues them, and holds the queue closed for a short window instead of letting them out immediately.
While the hold runs, nothing about the player's own experience changes. They still walk, jump, and swing normally on their own screen. What's frozen is everyone else's view: the server, and any player watching, is stuck on the last position that actually made it out before the hold started. When the hold ends, the queued packets release together, and the player appears to jump or stutter into their real spot instead of walking there.
Most implementations cap how long a hold can run. Let the gap between real and reported position grow too far and the server either rubber-bands the player back to a sane position or flags the movement outright, so the module is really trading how much desync it buys against how obvious the burst looks.
Why people use it in combat
The window of desync creates a targeting problem for opponents. During the hold, they're aiming at the last-known position, which is now several ticks behind your real location. Attacks land on empty space. The moment the burst sends the queued packets and you snap to your real position, the window closes, but you've bought a frame or two of invulnerability in a fight.
In a longer hold, the effect is more dramatic. A player could stutter backward or sideways by several blocks from the perspective of everyone else watching, making them much harder to hit with projectiles or blade weapons that require precision aiming.
Fake Lag vs Blink
Fake Lag gets lumped in with Blink because both are packet-manipulation modules that open a gap between a player's real position and what the server has been told. The mechanism underneath is different, and so is what it looks like on someone else's screen.
| Aspect | Fake Lag | Blink |
|---|---|---|
| Packet behavior | Delays movement packets, then releases them in a burst | Suspends the connection, then resumes it |
| Visual effect | Stutter or short teleport | Freeze, then a snap to a new position |
| What it exploits | Server holding a stale position while the client keeps moving | Server receiving no updates during the suspension |
| Detection marker | Sudden burst of movement packets after a hold | Connection gap followed by immediate update |
Same category of problem, different lever. Fake Lag never stops talking to the server, it just talks late and all at once. Blink stops talking altogether and picks the conversation back up when it decides to.
Detection and risk
Fake Lag exists to pull a player's real position away from what the server has recorded, and a burst of movement right after a hold is exactly the pattern server-side anticheats are built to catch. The consistency of packet bursts following holds, the pattern of stutter-movement across multiple fights, the impossible position transitions: all of these are tells a good anticheat looks for.
It's a detectable, gameplay-advantage cheat carrying the same ban risk as any other position-desync exploit. Don't treat it as something that fixes or hides a bad connection, treat it as a module that creates an obvious pattern when you use it.
FAQ
It changes when movement packets are sent, not how the player moves on their own screen. Packets get held back and released together in a burst, so the server's record of the position falls behind the real one.
No. High ping is a real network delay outside the player's control. Fake Lag is a deliberate, client-side hold-and-burst pattern that a normal connection would never produce on its own.
No. It opens a temporary gap between the real position and what the server has recorded, which can make the player harder to hit during the hold, but it doesn't block damage outright, and the burst itself is an easy detection signal.
Fake Lag keeps sending packets on a delay and bursts them later. Blink suspends the connection outright and resumes it after. Both desync position, just through different packet-level mechanisms.