Bloom Command Filter

✿ Bloom Command Filter

Your commands. Your rules.

Keep your server’s command suggestions clean and easy to navigate. Choose which commands players see, create additional lists for LuckPerms groups, and manage everything directly in-game.

Features

• Command visibility filtering — Hide commands outside each player’s configured list.
• Shared default list — Define everyday commands for all players.
• LuckPerms integration — Add group-specific commands with inheritance support.
• Optional execution blocking — Separately control whether hidden commands can be typed manually.
• Subcommand restrictions — Configure blocked paths for unwanted subcommands.
• In-game management — Add, remove, and list entries without editing files.
• Live updates — Apply list changes to online players.
• Automatic OP bypass — Operators remain unaffected by Bloom’s restrictions.
• Customizable messages — Includes English and Turkish, HEX colors, and configurable sounds.

Quick start

1. Place the plugin JAR in your server’s plugins folder.
2. Start the server.
3. Add commands to the default list:

/commandfilter add default spawn
/commandfilter add default home
/commandfilter add default sell

The default list applies to all normal players. With LuckPerms installed, you can also assign additional commands to a group:

/commandfilter add mvip fly

Players receive the combined commands from the default list and their matching LuckPerms groups.

LuckPerms is optional. Without it, the default list continues to work.

Commands

Command · Description
/commandfilter · Show help.
/commandfilter help · Show available commands.
/commandfilter add · Add a command to a group’s list.
/commandfilter remove · Remove a command from a group’s list.
/commandfilter list · Display a group’s configured commands.
/commandfilter reload · Reload configuration and language files.

Enter command names without the leading /, such as sell. Management commands can also be used from the console.

Permissions

Permission · Description · Default
bloomcommandfilter.admin · Manage command lists and reload settings. · OP
bloomcommandfilter.bypass · Bypass Bloom’s visibility and execution restrictions. · OP

Operators bypass filtering automatically. Non-OP staff can receive the bypass permission separately.

Configuration

Edit plugins/BloomCommandFilter/config.yml to manage command lists, filtering options, colors, and sounds.

Messages are available in:

plugins/BloomCommandFilter/lang/en.yml
plugins/BloomCommandFilter/lang/tr.yml

Visibility filtering and execution blocking are independent: you can hide a command from suggestions while still allowing players to type it manually.

Aliases and namespaced labels, such as plugin:command, must be added explicitly if you want to allow them.

How filtering works

Bloom Command Filter works alongside your existing permission system.

• Adding a command to a list does not grant permission to use it.
• Bypassing Bloom’s filter does not grant permissions from other plugins.
• Allowed commands retain their owning plugin’s normal argument suggestions.
• Subcommand visibility depends on the owning plugin and the server’s command system; some client-side suggestions may not be filterable.
• Execution blocking applies to direct player commands, not every command indirectly dispatched by another plugin.

Requirements

• A server version and platform supported by the selected release.
• The Java version required by your server.
• Optional: LuckPerms for group-specific lists.

No database or resource pack is required. Refer to the release details for compatibility information.

✿ A little less clutter. A better command list.