A chat command is a chat message starting with a configured trigger (such as !ping) to which the bot responds. streamion.bot supports two types of commands:

• Built-in commands — shipped with the bot, with logic implemented in code. You can rename their trigger, change cooldowns, change the required permission, add aliases, or disable them entirely. See the built-in command reference.
• Custom commands — commands you define yourself with a static response message. See custom commands.

Both kinds are managed on the Commands page (/commands).

If you want a command that counts up by one every time it is used (death counter, "lost the bit" counter, …), use a Counter instead. Counters live on their own page and behave the same way in chat, but they remember a value across uses and expose a {count} placeholder you can drop into the response.

Anatomy of a command

Permissions

Each command has a required permission level. The bot only responds if the chatter meets it:

Higher levels include all lower levels — e.g. a moderator can always run a "Subscriber"-restricted command. The Follower check uses Twitch's follower data with a short cache (about 10 minutes), so a viewer who just hit Follow may need a moment before the bot recognises them as one.

Cooldowns

Cooldowns suppress the bot's reply if the command was used too recently. There are two:

• Global cooldown — applies channel-wide. Set this to throttle noisy commands.
• Per-user cooldown — applies per chatter. Set this to prevent one viewer from spamming a command.

Set either to 0 to disable that cooldown. The broadcaster and moderators are typically still subject to cooldowns; check on the Commands page if you need exceptions.

Disabling a command

Toggle the Enabled switch on the Commands page. The trigger is still reserved (so you can re-enable it without losing settings), but the bot won't respond.