TidyCommandBlock: Flexible Command Control for Minecraft Servers

Taking Control of Your Minecraft Server Commands Running a Minecraft server is a balancing act. You want players to have freedom, but you also need to protect sensitive commands from misuse. Maybe you have a donor-only warp, or you want to prevent new players from spamming /help. The vanilla perm...

Download TidyCommandBlock for Minecraft 1.8.1

Original name: TidyCommandBlock

Minecraft: 1.8.1

FileVersionLoaderSize
TidyCommandBlock.jar1.8.1—31 КБDownload

Taking Control of Your Minecraft Server Commands

Running a Minecraft server is a balancing act. You want players to have freedom, but you also need to protect sensitive commands from misuse. Maybe you have a donor-only warp, or you want to prevent new players from spamming /help. The vanilla permission system can feel rigid, and many plugins force you to accept their default error messages. TidyCommandBlock changes that. It gives you the power to block any command, from any plugin, with custom permissions and messages, all through simple YAML files.

What Is TidyCommandBlock?

TidyCommandBlock is a lightweight Minecraft plugin that lets you restrict in-game commands in a neat and tidy way. Instead of relying on each plugin’s built-in permission nodes, you can centrally manage which commands are allowed, who can use them, and what message appears when someone is denied. It works with commands from any plugin, vanilla Bukkit commands, and even subcommands like /warp donorsmarket or /f rules. The plugin is free, open-source, and designed to be as flexible as possible without cluttering your server’s configuration.

Key Features at a Glance

  • Block any command – from plugins, Bukkit, or custom subcommands.
  • Custom permission nodes – assign a unique permission to each blocked command.
  • Fully customizable messages – show players exactly what you want when they lack permission.
  • UUID whitelist and blacklist – override permissions for specific players.
  • Simple YAML configuration – one file per blocked command, easy to edit and share.
  • In-game management commands – add or remove players from whitelists/blacklists without editing files manually.
  • Lightweight and efficient – minimal impact on server performance.

How to Set Up Command Restrictions

Configuring TidyCommandBlock is refreshingly straightforward. Each command you want to block gets its own YAML file inside the plugins/TidyCommandBlock/commands folder. You can create these files with any text editor, even Notepad. The syntax is clean and easy to read:

command: /warp
permission: mycustom.warp.use
message: <red>Sorry, you need a donor rank to use warps!
whitelist:
  - player1-uuid
  - player2-uuid
blacklist:
  - banned-player-uuid

In this example, the /warp command is blocked for everyone unless they have the mycustom.warp.use permission. The message uses Minecraft color codes to display a red error with a gold highlight. Whitelisted players can always use the command regardless of permissions, while blacklisted players are always denied, even if they have the permission. This layered approach gives you surgical control over who can do what.

Once your YAML files are in place, simply reload the plugin with /tcb reload and the restrictions take effect immediately. No server restarts needed. For server owners who prefer a modern, all-in-one management experience, the foxygame.net launcher offers a convenient way to handle mods and plugins directly from its interface, making it easy to keep TidyCommandBlock updated alongside your other server tools.

Commands and Permissions

TidyCommandBlock adds a single administrative command to your server: /tcb. This command is the gateway to managing whitelists and blacklists in-game, without touching the file system. Here are the available subcommands and their corresponding permissions:

  • /tcb help – displays the plugin’s help page. Requires tidycommandblock.help.
  • /tcb reload – reloads all command block configurations from disk. Requires tidycommandblock.reload.
  • /tcb whitelist add <file> <player> – adds a player’s UUID to the whitelist of a specific command file. Requires tidycommandblock.manage.
  • /tcb whitelist remove <file> <player> – removes a player from the whitelist. Requires tidycommandblock.manage.
  • /tcb blacklist add <file> <player> – adds a player to the blacklist. Requires tidycommandblock.manage.
  • /tcb blacklist remove <file> <player> – removes a player from the blacklist. Requires tidycommandblock.manage.

These permissions can be given to moderators or admins using any permission plugin, such as LuckPerms. The tidycommandblock.manage node is particularly useful for letting staff handle exceptions without granting full access to server files.

Why Server Admins Love TidyCommandBlock

Many plugins come with their own permission systems, but they often lack the ability to customize the “no permission” message. Players might see a generic “You do not have permission” line that doesn’t explain why or how to gain access. TidyCommandBlock solves this by letting you craft messages that fit your server’s tone. You can inform players that a feature is donor-only, link to your store, or simply add a touch of humor. The plugin also supports full color codes, so your messages can match your server’s branding.

Another standout feature is the UUID-based whitelist and blacklist. Permissions are great for groups, but sometimes you need to make an exception for a specific player. Maybe a long-time member deserves access to a command even without the rank, or a troublesome player needs to be blocked from /msg despite having the right permissions. TidyCommandBlock handles both cases elegantly.

Server performance is always a concern. TidyCommandBlock is built to be lightweight, hooking into the command preprocess event with minimal overhead. It doesn’t run complex checks or store massive databases. Each command restriction is a simple YAML file, so the plugin reads them quickly and caches the data. This means even servers with dozens of blocked commands won’t feel a lag spike.

Real-World Use Cases

Imagine you run a survival server with a donor-exclusive /fly command. Without TidyCommandBlock, you’d rely on the flight plugin’s own permission node, and its default error message might be bland. With TidyCommandBlock, you can block /fly entirely, set a custom permission like server.donor.fly, and display a message: “&6Flight is a &c&lDonor &6perk! Visit our store to unlock.” You can also whitelist your staff members so they can fly for moderation purposes without giving them the donor rank.

Another scenario: you have a custom plugin that adds /kit starter for new players. You want to prevent players from spamming it. TidyCommandBlock lets you block /kit starter specifically, without affecting other /kit subcommands. You can set a cooldown permission or simply blacklist known abusers.

Installation and First Steps

Getting TidyCommandBlock onto your server is simple. Download the plugin JAR from the official Spigot page and place it in your server’s plugins folder. Restart the server, and the plugin will generate its default configuration. The main config.yml lets you toggle anonymous usage statistics sent to MCStats.org; you can disable this if you prefer. Then, head to the plugins/TidyCommandBlock/commands directory and start creating your restriction files. Each file is a single command block, so you can organize them by plugin or purpose. For example, you might have warp_donor.yml, msg_staff.yml, and help_global.yml.

Best Practices for Command Management

  • Use descriptive file names – this makes it easier to manage dozens of restrictions.
  • Test permissions thoroughly – log in as a player with different ranks to ensure messages appear correctly.
  • Combine with a permissions plugin – TidyCommandBlock works alongside LuckPerms or any other system to create a robust hierarchy.
  • Keep backups of your YAML files – they are small and easy to version control.
  • Use the whitelist sparingly – it’s powerful, but overusing it can make permission logic confusing.

Conclusion

TidyCommandBlock fills a gap that many server admins didn’t even realize existed. It puts command blocking back in your hands, with full control over permissions, messages, and player exceptions. The YAML-based configuration is a breeze to set up, and the in-game management commands make it easy to adjust on the fly. Whether you’re running a small community server or a large network, this plugin helps you maintain order without sacrificing flexibility. Give it a try, and you’ll wonder how you ever managed commands without it.