Taking Control of Your Server Commands with Command Blocker
Running a Minecraft server is a rewarding experience, but it comes with its own set of challenges. One of the most persistent headaches for server admins is keeping the command list clean and secure. Even after carefully assigning permissions, players can often peek at available commands by simply pressing the Tab key. This seemingly harmless action can reveal plugins you would rather keep hidden, or worse, allow users to execute commands they were never meant to touch. The Command Blocker plugin, with its integrated TabComplete removal, solves this problem in a straightforward and highly customizable way.
What Exactly Is Command Blocker?
Command Blocker is a lightweight Bukkit/Spigot plugin designed to give server owners granular control over which commands players can see and use. Unlike basic permission systems that only block execution, this plugin also strips commands from the TabComplete suggestions. That means when a player hits the slash key, only the commands you explicitly allow will appear. No more accidental discovery of admin tools or plugin names through autocomplete. The plugin was originally built for a private server, but its simple yet powerful approach makes it a valuable addition to any public or semi-public Minecraft world.
Why TabComplete Removal Matters
Many server administrators focus solely on blocking command execution with permission nodes. However, the TabComplete feature in Minecraft can still list commands that a player does not have permission to run. This creates two major issues. First, it gives curious players a roadmap of your server’s installed plugins. By typing common command prefixes and seeing what pops up, they can deduce which plugins you use and potentially search for known exploits. Second, some plugins display their own “no permission” messages instead of a generic error, confirming the plugin’s presence. Command Blocker eliminates both problems by ensuring that unauthorized commands simply do not exist in the player’s view.
How the Plugin Works
At its core, Command Blocker uses a single configuration file where you define a list of allowed commands. Every command a player types or tabs through is checked against this list. If the command is not on the allowed list, it is blocked entirely—both from execution and from appearing in TabComplete. Operators (OPs) are automatically exempt from these checks, so you can still manage the server without restrictions. The plugin also supports custom permission nodes, letting you create different command sets for different player ranks. For example, you might allow regular players to use /home and /msg, while VIPs get access to /fly and /nick, all without exposing admin commands.
Configuration Made Simple
The config file is intuitive and easy to edit. You start by listing the commands you want to allow under a specific permission group. Then you assign that permission to the appropriate players or ranks via your usual permissions plugin (like LuckPerms). The plugin also includes a reload command, so you can tweak the list on the fly without restarting the server. This flexibility is a lifesaver when you are testing new plugins or adjusting to player feedback. For those who run a Minecraft server and want to streamline plugin management, the foxygame.net launcher offers a convenient, flexible, and modern way to install server-side plugins like Command Blocker right from its menu, making the setup process even smoother.
Key Features at a Glance
- Complete TabComplete suppression: Unauthorized commands vanish from autocomplete, keeping your plugin list private.
- Permission-based command whitelist: Create multiple tiers of command access using custom permission nodes.
- OP bypass: Operators retain full command visibility and execution, so administration is never hindered.
- Reload command: Apply config changes instantly with
/CommandBlocker Reload. - Update notifications: Players with the appropriate permission (and OPs by default) are alerted when a new version is available.
- Lightweight and focused: The plugin does one job and does it well, without unnecessary bloat.
Permissions and Commands
Command Blocker introduces three simple permission nodes to manage its own functionality:
CommandBlocker.Bypass– Grants a player immunity from all command checks. This does not give them extra commands; it simply disables the plugin’s filtering for that user.CommandBlocker.Reload– Allows a player to reload the configuration in-game.CommandBlocker.UpdateNotify– Enables update notifications for non-OP players.
The only in-game command provided by the plugin is /CommandBlocker Reload, which refreshes the allowed command list from the config file. This makes maintenance quick and painless.
Requirements and Compatibility
To function properly, Command Blocker requires ProtocolLib as a dependency. ProtocolLib is a widely used library that allows plugins to interact with the Minecraft protocol without dealing with low-level networking code. Make sure you have it installed before adding Command Blocker to your server. The plugin has been tested on version 1.16.5, but it may work on other versions as well. If you encounter any issues, the developer encourages reaching out through the support channel on their site rather than leaving a negative review, as many bugs can be quickly resolved with a bit of feedback.
Limitations and Future Plans
One important note: if you are using a BungeeCord network, Command Blocker will not filter commands that originate from the proxy layer. BungeeCord commands are processed between the player and the proxy, not on the individual Spigot server, so the plugin cannot intercept them. A dedicated BungeeCord version is in the works to address this gap. For now, the plugin is perfect for standalone servers or as a backend filter on each Spigot node.
Why Every Server Admin Should Consider It
Command Blocker fills a niche that many permission plugins overlook. It is not just about blocking commands; it is about shaping the player’s entire command experience. By removing TabComplete entries, you create a cleaner, more professional interface that only shows what is relevant to each player. This reduces confusion, prevents information leaks, and adds an extra layer of security. Whether you run a small survival world with friends or a large minigame network, controlling the command list is a subtle but powerful way to improve server quality.
Getting Started
Installation follows the standard Bukkit plugin procedure. Download the latest jar from the developer’s official site, place it in your server’s plugins folder along with ProtocolLib, and restart the server. Once loaded, a default config file will be generated. Edit it to define your allowed commands and assign the custom permission nodes to your player groups. A quick reload, and the plugin is active. From that moment on, your command list is exactly what you want it to be—nothing more, nothing less.
Conclusion
Command Blocker (With TabComplete Removal) is a must-have tool for any Minecraft server administrator who values privacy, control, and a polished player experience. Its ability to hide commands from autocomplete sets it apart from standard permission systems, while the configurable whitelist approach gives you total flexibility. With ongoing development and a responsive creator, this plugin is a smart investment for your server’s long-term health. Take command of your commands today, and give your players an interface that is as clean and secure as your world itself.