Skip to main content
Bloom stays silent on names it does not recognize, so a command that does nothing usually means it was never recognized in the first place.

​
Bloom says nothing at all

1

Confirm the prefix

Send b.help, which works no matter what the server’s prefix is, or mention Bloom directly. Both bypass the prefix entirely and tell you what is set.
2

Check Bloom can see the channel

Bloom needs View Channel, Send Messages, and usually Embed Links where you are typing. A channel override can deny these in one channel only.
3

Check the spelling

Unknown names produce no reply on purpose, so a typo looks the same as a broken bot. Run !help <command> to confirm the name.
4

Check whether the command is restricted

A server can disable or restrict commands by channel or role. If it works elsewhere but not here, that is the likely reason.

​
Other symptoms

You have run commands faster than Bloom accepts them. The limits are per user and clear on their own, so wait a moment and try again. Bloom mentions this occasionally rather than on every blocked message.
That is a permission or hierarchy difference, not a broken command. See Permission errors.
Real command names are matched before your aliases, so an alias that collides with a built-in name never fires. Run !aliases to see what is taken.
Bloom’s prefix commands are server commands. In direct messages it responds only to verification flows, such as a join gate captcha. Run commands inside a server.
A required argument is missing or in the wrong position. The usage line shows <required> and [optional] parts in the order Bloom expects them.

Using prefix commands

How Bloom reads what you type.

Permission errors

When a command is refused rather than ignored.

Command aliases

Creating and inspecting your own shortcuts.

Support server

Ask if a command still will not run.