ClientPermissions: Control Client Mods with Permissions
Running a Minecraft server means welcoming players who bring their own bag of tricks. Some use minimaps, others rely on macros, and a few might have tools that give them an unfair edge. For a long time, the only way to police this was clunky, outdated block codes hidden in your server MOTD. It was messy, hard to maintain, and nearly impossible to scale across different ranks. ClientPermissions: Control Client Mods with Permissions changes that completely by bringing client mod management into the modern age of server permissions.
This lightweight Bukkit plugin acts as a bridge between the mods your players have installed and the standard SuperPerms system you already use. Instead of relying on fragile text parsing, it communicates through dedicated plugin messaging channels. The result is a clean, granular, and predictable way to decide exactly what each player can and cannot do with their client-side modifications. If you are looking to download ClientPermissions: Control Client Mods with Permissions, you are taking a significant step toward a more balanced and orderly server.
Why Rethink Your Mod Management Strategy?
The old school approach of using block codes in the server description was never elegant. It required players to manually interpret codes, and it was nearly impossible to enforce. ClientPermissions: Control Client Mods with Permissions for Minecraft offers a smarter solution. It integrates directly with your existing permission manager, whether that is LuckPerms, PermissionsEx, or bPermissions. This means you can grant or revoke access to specific mod features with the same commands you use for any other plugin permission.
Imagine a scenario where guests are not allowed to use an auto-fishing mod, VIPs can use it but only during certain hours, and moderators have full access. With this plugin, that level of control is not just possible, it is straightforward. The mod remains installed on the client, but its behavior is dictated by the permissions assigned to the player. This gives you total freedom to curate the gameplay experience without forcing players to uninstall their favorite tools.
Preparing Your Server for Integration
Before you dive in, you need a server that is already running a permissions plugin. ClientPermissions does not replace your permission manager; it works alongside it. The plugin is compatible with any Bukkit version that supports SuperPerms, making it a versatile addition to your setup. You should be comfortable with the basics of your chosen permissions plugin, as all the configuration for mod access will happen through that system.
Getting Started: Installation and Configuration
The installation process is simple. Copy the plugin's JAR file into your server's plugins folder and restart. Once loaded, the plugin automatically registers the necessary communication channels. The next step is figuring out which mods you want to control. The plugin makes this discovery process painless.
Join your server with the client mod you want to manage and run the command /clientperms query. The plugin will list all compatible mods it detects on your client. For instance, you might see "Player: Steve Mods: Examplemod 1.5". The short name, "examplemod", is the identifier you will use to add it to the control list. Simply run /clientperms add examplemod to bring it under the plugin's jurisdiction. By default, all permissions for that mod are now denied, so you must explicitly grant access to your player groups.
To grant permissions, you use your standard permissions plugin. For example, with PermissionsEx, you might run /pex user Steve add mod.examplemod.somepermission to give a single player a specific permission. To give a group full access, you would use /pex group moderators add mod.examplemod.*. The syntax always follows the pattern mod.<mod_name>.<specific_permission>. To see a full list of what a mod offers, use /clientperms perms examplemod.
Supported Client Mods and Their Capabilities
ClientPermissions currently supports a curated list of popular client-side mods, each bringing unique features to the table. This selection covers some of the most common tools players use to enhance their experience.
- The Macro / Keybind Mod (0.9.4+): A powerful utility for creating complex macros and custom keybindings. You can control which ranks can automate repetitive tasks.
- VoxelPlayer (0.9.7+): A versatile mod for recording and replaying in-game actions, useful for creating tutorials or demonstrating builds. Server admins can restrict this to trusted members.
- VoxelMap (1.6.2+): An advanced minimap with a wealth of configuration options. You can decide who gets to use waypoints and radar features.
- AutoFish: Automates the fishing minigame, a boon for players on farming or economy servers. You can gate this behind a specific rank or donation tier.
- VoxelVision: Expands the visual capabilities of the game, offering enhanced rendering options. Control who can use these enhancements to ensure fair play.
Discovering Available Permissions for a Mod
While mod developers often list permissions in their documentation, there is a universal method to find them. Connect to your server with the mod active and run /clientperms perms <mod_name>. The plugin will output every permission node it knows for that specific mod. This is invaluable when you are setting up complex scenarios, such as allowing macro usage for builders but not for players in PvP arenas, or disabling video recording for new players to prevent griefing evidence from being missed.
Navigating the Plugin's Command Set
The command interface is minimalist but complete, giving you all the tools you need without overwhelming you with options.
- /clientperms query: Displays the list of mods you have installed that are compatible with the plugin.
- /clientperms add <mod>: Adds a mod to the plugin's control list.
- /clientperms remove <mod>: Removes a mod from the plugin's control, reverting it to unmanaged status.
- /clientperms list: Shows all mods currently being tracked on the server.
- /clientperms perms <mod>: Displays the specific permissions available for a given mod.
All operations are logged, and commands can be executed from the console or in-game by admins with the appropriate permissions. This ensures full accountability and ease of management.
A Note for Mod Developers
If you are a developer looking to add ClientPermissions support to your own client mod, the process is accessible. The plugin's author, Mumfrey, has made the source code available on GitHub. Integration relies on the exchange of plugin messages, allowing for granular control over features without complex overhead. Your mod would receive its own identifier, and permissions would follow the intuitive mod.yourmod.featurename pattern, which any admin can understand immediately.
Final Thoughts on Server Control
ClientPermissions: Control Client Mods with Permissions transforms the chaotic task of managing client-side modifications into a structured, predictable system. It eliminates the need for hacky MOTD edits and relies on the familiar mechanics of Bukkit permissions. By integrating seamlessly with your existing permission manager and supporting a solid lineup of popular mods, it becomes an indispensable tool for any server owner aiming to maintain balance and order. Whether you are running a small community server or a large network, this plugin offers the transparency and control you need. If you are ready to streamline your server management, exploring how to install this plugin is your next step toward a more controlled and enjoyable Minecraft environment. The plugin ensures that your rules are enforced automatically and transparently, letting you focus on building a great community rather than policing individual players.