Commands overview
A chat command is a message starting with a trigger (like !ping) that the bot recognizes and responds to. AveloBot supports two kinds 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).
Anatomy of a command
| Property | What it does |
|---|---|
| Trigger | The exact text that activates the command, e.g. !uptime. Must be unique within your workspace. |
| Aliases | Alternative triggers that run the same command, e.g. !fa for !followage. Also must be unique. |
| Permission | Who can run this command. See Permissions below. |
| Global cooldown | Minimum seconds between any two invocations in your channel. |
| Per-user cooldown | Minimum seconds between two invocations by the same chatter. |
| Enabled | If off, the command is silently ignored. |
Permissions
Each command has a required permission level. The bot only responds if the chatter meets it:
| Level | Who can use it |
|---|---|
| Everyone | Any chatter |
| Subscriber | Subscribers, VIPs, moderators, broadcaster |
| VIP | VIPs, moderators, broadcaster |
| Moderator | Moderators and broadcaster |
| Broadcaster | Only the streamer |
Higher levels include all lower levels — e.g. a moderator can always run a "Subscriber"-gated command.
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.