CommandWhitelist: Complete Control Over Server Commands

Ever ran a Minecraft server where players discovered commands you wish you could hide? CommandWhitelist solves that. It lets server admins control exactly which commands players can use and see, complete with custom "unknown command" messages. Simple idea. Powerful impact.

What This Plugin Does

CommandWhitelist is a Minecraft server plugin that acts as a command gatekeeper. Instead of every command being visible to every player, you define what they can and can't use. You can block command execution entirely, hide commands from tab completion, or target specific subcommands. The plugin works on Bukkit-based servers (Spigot, Paper, Purpur, and others), Waterfall proxies, and Velocity, making it flexible for virtually any server setup.

The core idea is simple but powerful: don't let players know commands exist if they're not supposed to use them. If your players can't tab-complete something like "op", they're less likely to try using it. If the "plugins" command doesn't appear in their suggestions, they won't snoop around your server's configuration or discover your installed mods. It's security through obscurity, but for server admins, that obscurity buys real peace of mind.

Why Server Admins Use This

Scenario one: you're running a vanilla survival server with some admin-only quality-of-life commands installed. You don't want regular players discovering `/give`, `/gamemode`, or `/tp`. CommandWhitelist keeps those dangerous tools invisible.

Scenario two: you've got a modded server with 50+ plugin commands and you only want players to see the ones they're actually allowed to use. Instead of overwhelming new players with `/admin`, `/debug`, `/dev`, and fifteen other commands they can't touch, you show them just the player-facing commands. Clean. Professional.

Then there's immersion-focused servers. Run a role-play community? Hide commands that break character. Building a hardcore challenge server? Hide commands that make survival easier. Creating a mini-games server? Only show the commands relevant to each game. If you're also checking out the Minecraft Server List to get discovered, you'll want your server presenting a polished experience, and CommandWhitelist helps with that.

Don't overlook the branding angle. Instead of the default "Unknown command. Type '/help' for help", CommandWhitelist lets you customize that response. Add your server name, point players to your Discord, make them feel like they're on a real, intentional server rather than a generic Spigot instance.

Installation and Configuration

Getting CommandWhitelist running takes two minutes. Download the latest JAR from GitHub, drop it into your plugins folder, and restart:

cd /path/to/server/plugins
wget https://github.com/YouHaveTrouble/CommandWhitelist/releases/download/v2.12.0/CommandWhitelist-2.12.0.jar
# Restart your server

On first startup, CommandWhitelist generates a config file automatically. The default behavior blocks nothing - you've to explicitly define what you want to hide. Configuration is YAML-based and straightforward once you open the file.

If you're also managing your server's player whitelist, the Minecraft Whitelist Creator tool works great alongside CommandWhitelist to handle traditional player username whitelisting separately.

Core Features That Solve Real Problems

Tab completion hiding is the standout feature. When players press tab after typing `/`, CommandWhitelist controls what suggestions appear. It's subtle but solves two problems: preventing players from discovering commands they shouldn't use, and eliminating confusion from seeing commands that don't work.

Subcommand targeting separates this plugin from one-dimensional command blockers. Most plugins work at the command level - you either allow `/say` entirely or block it. CommandWhitelist goes deeper. You can block `/say message` but allow `/say`. Most players can block `/give player_item_amount` while allowing other `/give` subcommands. This matters when you've got complex permission structures with dangerous subcommands.

Custom "no such command" messages replace vanilla error text with something that fits your server. Instead of the default error, you get something like: "That command isn't available on this server" or "Questions? Check your server documentation or ask a staff member." It's a small touch that makes your server feel intentional.

Permission integration is built in. If a player doesn't have permission to use a command, CommandWhitelist hides it from tab completion automatically. Combined with a permissions plugin like LuckPerms, this creates a cohesive experience where players only see commands they're allowed to use.

Gotchas and Common Pitfalls

The biggest gotcha: CommandWhitelist uses opt-in blocking. Nothing is hidden until you explicitly add it to the config. If you expect everything hidden by default and only certain commands allowed, you'll be disappointed. You've to actively configure what gets blocked.

Tab completion blocking doesn't prevent command execution through other means. If a player already knows about a `/give` command, they can still type it directly. CommandWhitelist can block the execution, but for complete secrecy, you need to prevent both tab completion AND execution. Plan accordingly based on your use case.

Compatibility runs solid back to Minecraft 1.13, which covers virtually every active server. The latest release (v2.12.0) is compiled against Java 21 with updated adventure dependencies. If your server runs 1.12 or earlier, CommandWhitelist won't help - though at that point you've got bigger problems.

One critical limitation: CommandWhitelist works on Waterfall proxies but explicitly doesn't support BungeeCord. If you're running BungeeCord, you'll need to configure CommandWhitelist on each backend server individually instead of centrally on the proxy. Waterfall users get the convenience of central configuration.

Customizing Your Server Presentation

CommandWhitelist pairs well with other server customization efforts. You're already thinking about player experience if you're managing commands. That same mindset applies to letting players browse Minecraft Skins in your community, set up custom spawns, and create a distinctive server identity. These small touches compound into a server that feels professional rather than thrown together.

Alternatives Worth Knowing About

PermissionsEx, if you're already running it for permissions, can handle some command blocking. It's less specialized than CommandWhitelist but might satisfy your needs. LiteBans has command hiding built in, but it's primarily a punishment system - better if you need full ban management than pure command control.