When setting up a multiplayer world or dedicated server with mods that rely on LibX, keeping the library consistent across machines prevents connection rejections and command errors.
Client vs. Server Placement
Because LibX supplies shared code used by other mods as well as the /libx [name] in-game commands, treat it as a both-sides requirement whenever dependent mods are active:
- Dedicated server: Place the LibX
.jarinside the server'smodsdirectory alongside the mods that depend on its shared code. Without it, the server fails startup with a missing-library error or cannot register/libx. - Player clients: Every player joining a modded server that runs LibX-dependent mods must also keep the matching LibX build in their local
modsfolder so Forge or NeoForge passes the mod-list handshake on login.
Running /libx Commands on a Server
Once connected to the server, you can invoke LibX utilities either in chat or from the host console:
1. In game, open chat and enter /libx [name], replacing [name] with one of the auto-completed subcommands shown above the input bar.
2. From the dedicated server console, enter libx [name] without the leading slash to trigger commands allowed from the console.
3. If a trusted moderator cannot see /libx in tab-completion, grant their account operator status so the server exposes restricted subcommands to them.