Never leak your base coordinates again!
A lot of things in Minecraft screenshots or videos for some reason can leak coordinates. Whether that's the bedrock, the clouds, block rotations, your F3 menu, etc.
The worst part about this is that there are servers such as DonutSMP where it is critical to keep your location a secret, otherwise you risk losing much of your progress.
Hide Me removes those pesky little accidents by sending everyone trying to reverse engineer to find your coordinates down a rabbit hole of randomizers.
The Nitty-Gritty
Thirty-four vanilla blockstates ship a random variant list: stone, deepslate, dirt,
grass_block, sand, sculk, every concrete powder, and netherrack with sixteen variants rather
than four. Each visible face is worth about two bits, so roughly thirty blocks pins a position in a
world thirty million blocks across. A wall of stone in frame is more than enough. So is a roof of
grass.
Every one of those choices is a rotation or a mirror of one texture, never a different texture. That is exactly why nobody notices, and why nobody thought to hide it.
Hide Me re-keys all of it.
| Leak | Derived from | What Hide Me does |
|---|---|---|
| Block rotations | the coordinate alone | re-keys the rendering seed |
| Plant jitter | the coordinate alone | re-keys the model offset |
| Cloud phase | the coordinate alone | slides the cloud origin |
| Bedrock | the world seed | re-rolls the gradient layers |
| F3 coordinates | nothing, it just says them | scrambles every reading |
It re-keys rather than flattens
The other way to close a rotation leak is to make every block face the same way, or retexture stone to something rotationally symmetric. That works, and it announces itself in every screenshot, and it makes the game look like a bug report.
Hide Me draws from the same distribution instead. Measured over 26.2M positions, vanilla's split across a four-variant block is 24.996 / 25.001 / 24.984 / 25.019 percent and Hide Me's is 24.988 / 24.994 / 25.005 / 25.013. Change a single bit of your key and the two patterns agree on 25.008 percent of blocks, which is exactly what unrelated patterns do. Your world looks exactly like a world. It just is not this one.
The same care goes everywhere. The cloud offset is a whole number of cloud cells, because every cloud edge in an untouched client lands on a multiple of twelve blocks and one that did not would be a worse giveaway than the phase it was hiding.
It is not an X-ray mod, and nothing desyncs
- Nothing is hidden. Ores, chests, fluids, spawners and anything a player placed are untouched.
- Air stays air. Holes you dug in the Nether roof are still there, still where you left them.
- Physics is unaffected. Collision, ray tracing and block breaking all use the real world, so you cannot walk into a wall that is not there. Bamboo is deliberately left out of the plant jitter, because vanilla derives its hitbox from the same number.
- No packet changes. Everything your client sends is built from the real world, so not one byte differs from an unmodified client. There is no desync to detect, because there is no desync.
Seeing the real thing
The disguise is convincing enough to fool you, which is a problem when you actually need to know where you are. Hold the reveal key and the truth comes back for as long as you hold it, all of it: rotations, plant jitter, clouds, bedrock and the coordinates.
That matters for more than navigation. It is the only way to check the disguise is doing anything at all, and a mod whose whole design rests on "you cannot see the difference" has to leave you exactly one way to see the difference. Stand at a deepslate wall and tap it.
| B | Hold to see the real world, or switch it to a toggle |
| New key | Throw the secret away and redraw everything from a fresh one |
| Settings | In the kUI hub, or on a keybind of its own if you do not use kUI |
While you have the real world toggled on screen, there will be an outline on the edge of your screen to remind you that you are not hidden.
About F3
Coordinates are also scrambled so that there's no more accidental leaks when your live or on screenshare. However, when you need to actually view your real coordinates, the reveal keybind works here as well.
Keep your config to yourself
Your key lives in config/hideme.json. Do not share that file, and never ship one in a modpack.
Anyone holding those two numbers can reproduce every pattern you see. A pack shipping a hideme.json
would hand all of its users the same key, and breaking one would break every one of them.
What it does not protect
Distinctive terrain, a ravine, a structure or a biome edge in frame is still searchable against a cracked seed. A minimap or coordinate HUD from another mod still says exactly where you are. Sound is still honest, so audio in a recording can tell bedrock and deepslate apart. Screenshots cannot.
On 1.21.9 and later, the crack particles thrown off while mining are not disguised. Minecraft restructured that path away and there is no equivalent left to hook. It is a small leak, visible only while you are actively breaking a disguised block, and everything else is intact. The mod says so in its own log at startup rather than letting you assume otherwise; on 1.21.8 and earlier those particles are disguised like the rest.
Requirements
Fabric 1.21.4 through 1.21.11, client-side only. Needs Fabric API. Sodium is supported. kUI is optional on the versions it publishes for, adding the settings to the shared hub.
This is a technical statement, not a promise about any particular server's rules. Nothing here is detectable, but a server that forbids client mods as a matter of policy is a rules question rather than a detection one.
All rights reserved. Free to download and use, but not to redistribute, modify or republish, and not to bundle into a modpack without asking first (this is especially important since everything relies on players have different keys).
Copyright © 2026 KALPE.
