Every ModHider 26.2 Fabric feature, explained
Grouped by the thing each one closes rather than by menu order, because that is how you decide what you need. Everything below ships in ModHider 26.2 for Fabric and in the classic 1.21.11 build, and everything is on a switch.
Every module carries the builds it ships in. Most behave identically on ModHider 26.2 for Fabric and on the classic 1.21.11 jar; four are marked New in 26.2 because the classic build only approximates them. The line under each card is the config key it maps to.
Handshake
4 modulesWhat your loader tells the server the moment you connect. This is the layer the original ModHider projects were built to close, and it is where ModHider 26.2 for Fabric does most of its work.
Mod List Blocking 26.2 · 1.21.11
Strips your installed mods out of the loader handshake before it leaves your client, so the server logs an empty list instead of a roster of everything you run. This is the core of ModHider 26.2 for Fabric and it is on the moment you install the jar.
handshake.block_mod_listPer-Mod Visibility 26.2 · 1.21.11
Decide mod by mod what the server is allowed to see. Work from mod IDs the way the classic 1.12.2 ModHider config did, only without editing a file: every mod on your list gets a hidden or reported switch.
handshake.visibility[mod_id]Client Brand Spoofing 26.2 · 1.21.11
Modern Minecraft announces its loader over the minecraft:brand plugin channel, so a server sees the word fabric before it sees a single mod. ModHider reports vanilla on that channel instead.
brand.report_as = vanillaLoader Passthrough 26.2 · 1.21.11
ModHider deliberately does not hide the loader itself. A client that claims to have no loader while still speaking the loader's protocol is a louder signal than the mod list ever was, which is exactly why the loader itself is left untouched.
handshake.hide_loader = falseProbe Defence
3 modulesServers do not have to ask your loader anything. They can hand your client a piece of text and watch how it renders. ModHider 26.2 Fabric closes the three probes that actually get used in the wild.
Translation-Key Shield 26.2 · 1.21.11
A server sends a sign, a chat line or a boss bar containing a mod's translation key, such as sodium.option_impact.low. A client with that mod renders the translated string; a vanilla client leaves the raw key. ModHider leaves unknown keys untranslated so both clients look identical.
probes.translation_shieldKeybind Placeholder Shield 26.2 · 1.21.11
The same trick works with keybind placeholders, which resolve to a bound key on a modded client and stay raw on a vanilla one. ModHider applies the same rule there, so a probe sign gets the same answer either way.
probes.keybind_shieldProbe Detection Log New in 26.2
When a server pushes text that looks like a fingerprinting probe, ModHider notes it in a local log and can raise an in-game toast. Nothing is sent anywhere; it just tells you which servers are looking.
probes.notify = toastTraces
3 modulesEven with a clean handshake, mods leave fingerprints in channels, log files and the debug overlay. ModHider 26.2 for Fabric sweeps those too.
Channel Filter 26.2 · 1.21.11
Any mod that talks to the server has to register a custom payload channel, and registering it announces the mod by name. Choose which channels your client registers, with a warning when a mod genuinely needs one to work.
channels.allow / channels.denyLog & F3 Scrubbing 26.2 · 1.21.11
Keeps mod names out of latest.log and out of the F3 debug overlay. Useful when a screenshot or a pasted log is the thing that gives you away rather than a packet.
traces.scrub_logs / scrub_f3Self-Hiding 26.2 · 1.21.11
ModHider never reports itself. A mod called ModHider showing up in a server log would defeat the entire point, so hiding itself is the default and always has been, exactly as the original Forge build shipped it.
always onControl
6 modulesThe settings layer. Everything is configurable from inside the game, and the sensible answer is already selected before you touch anything.
Per-Server Profiles 26.2 · 1.21.11
Different rules per server address. Report a full list to the private SMP that asks you to, hide everything on a public network, and let ModHider pick the right profile automatically from the address you connect to.
profiles[address]Handshake Preview New in 26.2
Before you join, see exactly what the server would receive: the brand string, the channel list and the mod entries, with the hidden ones blacked out. No guessing whether a setting took effect.
preview.openIn-Game Config Screen 26.2 · 1.21.11
Toggle everything from a GUI reached through the mod list, the way the original ModHider was configured. No editing a .cfg by hand unless you want to.
GUI → Mods → ModHiderZero-Config Default 26.2 · 1.21.11
Install the jar and the useful defaults are already applied: mod list blocked, brand reported as vanilla, probes shielded, ModHider hidden. Configuration is for exceptions, not for getting started.
defaults.jsonHot Reload New in 26.2
Change a profile or flip a mod's visibility without restarting Minecraft. The next handshake uses the new rules, which matters when you are testing what a specific server accepts.
config.hot_reloadProfile Import & Export New in 26.2
Share a ruleset as a small text file, or move your setup between installs and between the ModHider 26.2 Fabric build and the classic 1.21.11 build. Profiles carry over untouched.
profiles.exportWhat ModHider 26.2 for Fabric added
Four modules are new or materially rebuilt in the 26.2 line. The classic 1.21.11 jar keeps its approximations of them, but it will not gain the rebuilt versions.
Handshake Preview
The single most useful thing in the 26.2 build. It renders the exact handshake a server would receive before you connect, so a wrong setting is something you see rather than something you find out about afterwards. The live demo on the home page is a copy of it.
Probe Detection Log
ModHider 26.2 recognises translation-key and keybind probes as they arrive and can raise a toast. The classic build records them to a file and says nothing at the time.
Hot Reload
Change a profile mid-session and the next handshake uses it. Before 26.2 that meant restarting Minecraft, which made testing what a given server accepts slow enough that most people never bothered.
Profile Import and Export
Profiles became a portable text file in 26.2, so a ruleset moves between installs, between machines and between the two builds without hand editing.
None of it is gated and none of it is sold separately. When you download ModHider 26.2 for Fabric, all 16 modules on this page are already in the jar and the sensible ones are already on.
Which ModHider 26.2 module closes which vector
Every module above exists because of one of these. The fifth row is the honest one.
The handshake mod list
The loader hands the server a manifest of what you have loaded, and the server writes it down. On Forge and FML that is a literal mod list attached to the connection handshake, which is the packet the original ModHider was written to rewrite. On Fabric the same information leaks through registry sync and the channels your mods register.
Covered — Mod List Blocking, Per-Mod Visibility
The client brand string
Modern Minecraft reports its loader brand over the minecraft:brand plugin channel: vanilla, fabric or forge. It is one short string, it arrives before anything else, and on its own it already tells a server you are modded even if your mod list came back empty.
Covered — Client Brand Spoofing
The translation-key probe
The clever one. A server puts a mod's translation key, say sodium.option_impact.low, into a sign, a chat message or a boss bar. Your client either renders the translated text, because the mod supplying that key is installed, or leaves the raw key on screen. The server sees which happened and knows. Keybind placeholders work the same way.
Covered — Translation-Key Shield, Keybind Placeholder Shield
Plugin and custom payload channels
Any mod that needs to talk to the server has to register a custom payload channel, and registering it hands over a namespaced name. A server that never asks for your mod list can still read the channel registry and recognise half of what you run.
Covered — Channel Filter, Log & F3 Scrubbing
Behaviour, watched by anti-cheat
The last one is not a packet at all. Anti-cheat infers a mod from what you do: reach, aim snap, timing, movement that a human hand does not produce. Nothing in a handshake matters here, and nothing ModHider does will change it.
Not covered — and no mod can honestly claim otherwise
The line ModHider 26.2 for Fabric will not cross
No behavioural cover
Not one module on this page changes what your mods do. ModHider edits the packets that describe your client, and that is the whole surface it touches. Anti-cheat that watches reach, aim, timing or movement is looking at something ModHider never sees.
No loader hiding
There is deliberately no module for hiding Fabric Loader itself. The reasoning is the same: a client with no loader that still speaks the loader's protocol stands out far more than a long mod list ever did.