InfoBridge

InfoBridge

Know exactly what your players are running. InfoBridge sends each client's mods, resource packs and shader packs to the server, where staff can inspect them and set what's allowed.

Install it on both the server and the client. Requires Fabric API.

What staff can see

• Mods: name, version, jar file, SHA-256 hash, and where each one loaded from, including mods loaded from outside the mods folder
• Mods folder: every file, even ones Fabric didn't load
• Resource packs: enabled packs in priority order, plus a look inside each pack. It warns automatically about common X-ray tricks: see-through stone and deepslate, block models with no geometry, replaced core shaders, and glowing ore textures
• Shaders: Iris or OptiFine, whether shaders are on, and the active pack and its contents
• Launch details: the launcher profile the game was started as (a cheat client installed as its own profile shows up here), Java version, launcher, JVM arguments, Java agents, fabric.addMods
• Change history: alerts when a player's setup changes between sessions or mid-game

Everything is clickable in chat. Hover for details, click to open the next view.

Enforcement (off by default)

• Checked at login: blocked players are refused before they spawn
• Blacklist: mod ids, name patterns, file hashes, pack and shader patterns
• Whitelist and review queue: unknown mods wait for staff to approve them for everyone, approve them for one player, or deny them
• Approve a whole setup at once: /ib approve all <player> [mods|packs|shaders|everything] approves everything a trusted player uses, for everyone. Blacklisted or denied items are always skipped, never approved
• Require the client mod: /ib requiremod on turns away clients without InfoBridge, operators included
• Bypass: exempt trusted players with /ib bypass add <player>
• In-game config: /ib config changes settings without editing files

Commands

/infobridge (alias /ib): list, check, mods, files, packs, shaders, env, changes, refresh, search, export, review, approve (including approve all), deny, revoke, bypass, config, requiremod, reload

Permissions

Supports LuckPerms and any other fabric-permissions-api provider. Every sub-command has its own node (infobridge.command.<name>), plus infobridge.notify for alerts and infobridge.bypass for exemptions. Without a permissions mod, it falls back to operator levels.

Privacy

Clients only send reports to servers running InfoBridge that ask for one. Home-folder paths are shortened to ~, and anything that looks like a password or token is removed before sending.

Limitations

InfoBridge relies on the client reporting honestly about itself. It catches ordinary cheat mods, X-ray packs and careless setups, but a heavily modified client can lie. Use it alongside a server-side anti-cheat, not instead of one.

If your server is behind Velocity or BungeeCord, set loginPhaseCheck to false in the config. Checks then run right after the player joins.