Repository navigation
Known Issues
Documented, deliberate gaps and platform-specific limitations — not bugs, just things this mod genuinely can't or doesn't yet do on certain builds.
NeoForge builds don't offer Mod Whitelist's AUTO mode. NeoForge has no equivalent to Fabric's global network-channel registry, so there's no way to scan installed mods for "has a server channel" the way AUTO mode does on Fabric. Use BLOCK ALL or CUSTOM instead — every other protection feature works the same as on Fabric.
NeoForge builds are also newer and less battle-tested overall than the Fabric line (available since v1.6.0, for MC 1.21.1 / 1.21.11 / 26.2) — please report issues.
The Show HUD Indicator setting renders via a direct Mixin on 1.20.1–1.21.11, which is reliable. On 26.1+ it uses Fabric API's newer HUD rendering pipeline instead, since vanilla's own rendering internals there change shape between patches. Report back if it doesn't show up for you on 26.1+.
MC 26.3 changed a lot at once (authlib 9.x→10.x, GLFW→SDL windowing, a resource-pack composition rework). Two features are scaled back rather than shipped as an unverified guess:
-
Bypass Server Pack Requirement / Strip Mod Shader Overrides don't apply. 26.3 replaced how server packs are opened internally (
openPrimary/openFull→openMetadata/openResourcesreturning aStream<PackResources>) — a real architecture change, not a signature tweak, and not something to wrap correctly on a guess without a server actually pushing a pack to test against. Every other protection feature is unaffected. -
Account Import/Export uses a fixed file path instead of a native file picker — 26.3 dropped the
lwjgl-tinyfdmodule entirely (window backend moved to SDL). Import reads from, and Export writes to,opsec-accounts-import.json/opsec-accounts-export.jsonin your Minecraft config folder.
(And only on NeoForge 1.21.11/26.2, not the 1.21.1 port.) The underlying DebugEntryPosition F3 entry doesn't exist before that version. It also only covers vanilla's own F3 overlay, not a third-party debug-HUD replacement (e.g. BetterF3) that reads your position independently of vanilla's F3 system rather than through it — see Streamer Mode for why that's a harder problem than a signature change.
Only the above-head nametag and tab list are replaced so far — a name baked into chat message text (e.g. <Steve> hello) isn't masked.
ServerStatusPinger.pingServer's callback shape on 1.20.1/1.20.2/1.20.4 isn't special-cased by the relay, so on those versions Lazy Server List Ping just blocks the automatic ping as before — see Cloudflare Ping Relay.
Security-hardened public servers (e.g. Hypixel, 2b2t) commonly firewall off datacenter/cloud IP ranges, including Cloudflare's — pinging one of these through the relay fails with "proxy request failed, cannot connect to the specified address" even though the relay is working correctly. This is the target server's own anti-bot filtering, not a bug in the relay. Smaller/community servers that don't block cloud ranges work fine.