- Long Jump is a movement module that extends how far a single jump carries past vanilla Minecraft's normal distance.
- It works by altering the movement packets sent while a jump is already in progress, not by changing how the jump is triggered.
- The gain is small on any one jump but adds up over repeated use crossing terrain or breaking off a chase.
- It changes measurable movement, so a server that recomputes expected jump distance can flag it as easily as any other physics violation.
Long Jump is a movement module that stretches how far a single jump carries past what vanilla Minecraft's physics allow. Instead of changing how a jump gets triggered, it works on the data describing the jump while it's already happening: the packets reporting the player's position and motion mid-arc. The result is a jump that lands farther than gravity, starting velocity, and existing momentum should permit. It sits in the movement category alongside things like speed and momentum modules, and it's exactly the kind of measurable deviation a server-side anticheat is built to catch.
How Long Jump works
Vanilla Minecraft works out a jump's horizontal distance from a small set of physics inputs: how fast you were moving when you left the ground, gravity pulling you back down, and whatever momentum you already had going into it. There's no hidden "jump further" setting sitting in the client waiting to be flipped. The distance falls out of those numbers every time, the same way, for every player.
Long Jump doesn't touch how the jump starts. It intervenes after that, in the packets describing the player's position and motion while the jump is already in the air, stretching the horizontal distance covered before landing. Servers generally trust a client's reported position within some tolerance, nobody wants a false flag every time someone's connection hiccups, and that tolerance is what the module leans on. It can carry a player past where a legitimate jump would end without one obviously broken frame that stands out on its own.
Is Long Jump safe to use
The appeal is straightforward: clear a gap a normal jump can't, cut the time spent crossing open terrain, or put a few extra blocks between you and whoever's chasing you. On any single jump the gain looks minor. Used every crossing or every disengage, it adds up.
None of that makes it invisible. Long Jump is a gameplay-advantage feature, not a cosmetic one, and it moves something a server can measure directly: horizontal distance per jump. A server that recomputes what a jump should cover from a player's reported velocity and position can flag one that lands farther than physics allows, regardless of how clean the individual packets look. It's turned up in clients including Fan and Tenacity. Treat it as detectable, not as a safe shortcut.
Opal ships it, labeled honestly
Opal's own catalog carries a Long Jump module, described about as plainly as a description gets: lets you jump further. It's filed under use at your own risk, the same as it would be on any client, because a jump distance vanilla physics doesn't produce is precisely the kind of thing a server-side check is watching for.
Reference, not a how-to
This page explains what Long Jump means and how the effect generally works, not how to configure it. Extending jump distance past vanilla physics breaks the movement-cheat rules on effectively every server that enforces them, and getting caught costs the account.
FAQ
It extends the horizontal distance a jump covers by altering the movement packets sent while the jump is already in progress, not how high or how often the player jumps.
No. Bhop chains repeated jumps to build or hold speed over time, while Long Jump stretches the distance of one single jump. Both are movement modules and both exceed vanilla physics, but the mechanism is different.
Yes. It produces jump distances vanilla physics doesn't allow, a server checking movement against expected values can detect that, and using it typically breaks the movement-cheat rules most servers enforce.
Not inherently. Packet manipulation can avoid one obviously impossible frame, but the resulting distance is still measurable against what the reported velocity and position should produce, which is exactly what server-side checks compare against.
