Minecraft plugin CommandBlocker

🔌 About CommandBlocker

CommandBlocker — is a plugin for Minecraft servers that allows operators to block commands and optionally block TAB autocomplete so players cannot discover or run unwanted commands. CommandBlocker is focused on straightforward command blocking for Paper/Purpur/Spigot (and Folia in recent releases) server environments.

🎯 Purpose

CommandBlocker solves the problem of players discovering or abusing server/plugin commands. On public or semi‑public minecraft servers, untrusted players can discover commands via TAB or execute harmful commands; CommandBlocker prevents that by keeping a whitelist of allowed commands and blocking everything else by configuration.

• Prevents accidental or malicious use of sensitive commands
• Hides plugin commands from discovery via TAB
• Lets staff keep control of which plugin commands are available to ordinary players

⚙ Main features

• Block any command not on an allowed list
• Block command autocomplete (TAB) so commands aren't discoverable
• Permission-based bypass (permission node to allow staff access)
• /cb reload to reload configuration without restarting
• Hidden /cbtest command to verify plugin is active
• Configurable messages (customizable block / no‑permission messages)
• Compatible with Paper, Purpur, Spigot and Folia (as listed on official distribution)

🧩 Who it's for

• Server owners who need to restrict plugin or vanilla commands
• Networks, lobbies, survival and PvP servers that want to hide commands
• Admins who prefer a lightweight, configuration-driven approach to command control

🏗 Examples of use

• Block all plugin commands except a small allowed list (e.g., help, msg, spawn)
• Prevent players from discovering admin commands via TAB completion
• Provide a custom "command blocked" message when a blocked command is attempted

⌨️ Commands

Note: official distribution lists /cb reload and a hidden /cbtest. Other /cb subcommands exist in older or different forks; see URLs below for variant specifics.

🔐 Permissions

If you need exact default permission assignments for your build, check the plugin's GitHub or distribution page listed below.

⚙ Installation

📥 Install

• Download the plugin .jar from an official distribution (Modrinth / Spigot / GitHub releases as available).
• Place the .jar into your server plugins/ folder.
• Start the server (full restart recommended).
• Edit the generated config.yml to set allowed-commands and messages, then run /cb reload to apply.

📦 Dependencies

• No mandatory external dependencies are listed by the modern distribution. (Older forks/releases have used libraries such as CS‑CoreLib or optional ProtocolLib for advanced tab blocking; check the specific release notes.)

🧾 Configuration

• The plugin generates a config.yml with at least allowed-commands: and messages: entries. Example keys shown in official config: allowed-commands, messages.command-blocked, messages.reload-success, messages.no-permission, messages.test-success.
• No database (MySQL/SQLite) is required or mentioned.

🧠 Additional information

⚠ Known conflicts

• No specific conflicts are listed in the official modern distribution. The plugin notes compatibility with common permission and auth plugins (examples listed include LuckPerms, AuthMe, TAB on the distribution page).
• Older forks or older Spigot builds referenced different libraries (CS‑CoreLib, Metrics). If you run an older Minecraft server version, check the release notes for legacy modules.

🚧 Limitations

• CommandBlocker works by blocking commands and TAB autocomplete; it is not a permissions plugin — you should use a permissions manager (e.g., LuckPerms) alongside it for fine‑grained access control.
• Behavior and available commands may differ between forks and older releases. Use the distribution that matches your server core and Minecraft version.

❓ FAQ

Q: How do I allow a command for players?
A: Add the command (without leading slash) to the allowed-commands list in config.yml and reload with /cb reload.

Q: Will CommandBlocker hide commands from ops?
A: The modern distribution uses a permission bypass node; exact behavior for ops by default is not specified in the modern distribution—check your chosen release or assign the bypass permission to groups as needed.

Q: Does it block TAB autocompletion?
A: Yes — the modern release documents the ability to block TAB autocomplete to stop command discovery.

Q: Is a database required?
A: No — there is no indication of MySQL/SQLite usage in the official distribution.

📊 Telemetry and support

• The modern distribution does not explicitly document bStats/Metrics in its description. Older variants have used anonymous metrics; check the release notes or plugin.yml/config of the specific jar for metrics configuration.
• The project links to a GitHub repository and a Discord support invite on the official distribution page; use the GitHub issues for bug reports.

🌐 When to use CommandBlocker

Use CommandBlocker when you need a lightweight, low‑overhead spigot plugin to block plugin commands and prevent players from discovering commands via TAB. It is suitable for Paper plugin setups, spigot plugin environments, and modern Folia‑compatible servers where hiding plugin commands and controlling plugin permissions interplay are required.