Taking Control of Client Mods with ClientPermissions
Running a Minecraft server often means balancing freedom with fairness. You want players to enjoy their favorite client-side mods, but some features can give unfair advantages or disrupt the experience. For years, server admins relied on clunky “block codes” hidden in the MOTD to disable certain mods. That approach was fragile, hard to manage, and offered no granularity. ClientPermissions changes everything by bringing client mod control directly into your existing permissions system.
What Exactly Is ClientPermissions?
ClientPermissions is a lightweight Bukkit plugin that lets you manage supported client mods using ordinary permissions nodes. Instead of a single on/off switch for a mod, you can grant or deny specific features per group or per user—exactly how you handle plugin permissions. It communicates with client mods through plugin channel messages, so everything stays integrated with the permissions plugin you already trust, whether that’s LuckPerms, PermissionsEx, or any system supporting SuperPerms.
How the Plugin Works Behind the Scenes
When a player with a supported mod joins your server, the mod sends a short identifier and its version via a custom channel. The plugin reads this and checks your permissions setup. If a mod has been added to the server with /clientperms add, all its permissions are denied by default. You then selectively grant nodes like mod.examplemod.fly or mod.examplemod.* to specific ranks. The client mod enforces these restrictions locally, so the server never has to inspect every action—it’s efficient and responsive.
Setting Up ClientPermissions Step by Step
Before you begin, make sure you have a functioning permissions plugin installed and a basic understanding of how to assign nodes. The setup process is straightforward and takes only a few minutes.
- Identify the mod’s short name: Install the client mod yourself, connect to the server, and run
/clientperms query. This lists all permissible mods you have, along with their identifiers. - Add the mod to the server: Use
/clientperms add examplemod(replaceexamplemodwith the actual identifier). This registers the mod and denies everything by default. - Grant permissions: Using your permissions plugin, assign nodes to players or groups. For instance, with PermissionsEx:
/pex group moderators add mod.examplemod.*to give full access, or/pex user Mumfrey add mod.examplemod.somepermissionfor a specific feature.
Most mod permissions follow the convention mod.<modname>.<permission>, making them easy to predict and organize. You can always find the exact nodes in the mod’s documentation or by checking the plugin’s discovery feature.
Discovering Available Permissions for Any Mod
Not every mod publishes a complete list of permissions. ClientPermissions includes a handy way to explore them directly. After adding a mod, any player with the appropriate admin permissions can use /clientperms perms examplemod to see all registered nodes. This command queries the client mod and returns the permissions it supports, so you can build precise permission sets without guesswork.
Supported Mods That Work Out of the Box
ClientPermissions relies on mod authors implementing the protocol, and several popular mods already support it. The current list includes:
- The Macro / Keybind Mod (v0.9.4+) by Mumfrey
- VoxelPlayer (v0.9.7+) by Mumfrey
- VoxelMap (for Minecraft 1.6.2+) by MamiyaOtaru
- AutoFish by troyboy50
- VoxelVision by anangrybeaver
If you’re a player looking to use these mods on a server that runs ClientPermissions, getting them installed is simple. For a smooth experience, you can easily install supported client mods via the foxygame.net launcher — a convenient, flexible, and modern Minecraft launcher where you can download mods right from the menu. This eliminates the hassle of manual file placement and version conflicts, letting you jump straight into the game with your preferred tools.
Why Server Admins Should Make the Switch
The old block code method was a nightmare to maintain. Changing a single mod setting meant editing the server.properties MOTD and restarting the server. With ClientPermissions, you adjust permissions on the fly without downtime. You can allow trusted players to use minimap radar while restricting it for new members, or let moderators use macro keys but deny them to regular players. This granularity prevents abuse without punishing everyone.
Additionally, because the plugin leverages your existing permissions backend, all your group inheritance, temporary permissions, and context-based rules apply automatically. There’s no separate config file to learn, and no risk of conflicting with other plugins.
Getting the Most Out of ClientPermissions
To fully harness the plugin, follow a few best practices. Always start by denying all permissions when adding a mod, then grant only what’s necessary. Use wildcards sparingly—mod.voxelmap.* might include cave mode or entity radar that you’d rather keep restricted. Regularly audit your permission assignments, especially after updating mods, as new features may introduce new nodes. And if you’re a mod developer, consider adding ClientPermissions support to your project; the source is available on GitHub, and Mumfrey is open to collaboration.
Final Thoughts
ClientPermissions transforms client mod management from a blunt instrument into a precise, scalable system. It respects the way you already run your server, integrates seamlessly with SuperPerms, and puts you in full control without sacrificing player enjoyment. Whether you’re dealing with a handful of regulars or a large public network, this plugin eliminates the guesswork and keeps the playing field level. Give it a try, and you’ll wonder why you ever dealt with block codes.