everything's up and runningsee status
// STREAMION.BOT DOCS

All about streamion.bot.

Sign-in flow, chat commands, event responses, alerts, music integrations — the full reference for your bot configuration.

Counters

A counter is a chat command that goes up by one each time someone uses it. Counters are useful for tracking running totals on stream, such as deaths per session, retries, donation milestones, or any other recurring tally.

Counters are managed on the Counters page (/counters), separate from regular commands. In chat they behave like a normal command: a viewer types the trigger, the bot responds with the message you configured, and the stored count goes up by one.

How it differs from a regular command

Custom commandCounter
ResponseFixed template with the placeholders {user}, {displayname}, {channel}.Same, plus the additional {count} placeholder.
StateNone — the command forgets every use.Stores a count value that goes up by one for each use (race-safe even if multiple chatters trigger it at the same instant).
ResetNot applicable.Workspace members with the right permission can override or reset the count from the dashboard.

In all other respects a counter is configured like a custom command: trigger, aliases, cooldowns, permission, and an enabled toggle.

Creating a counter

Click New counter on /counters and fill in:

FieldNotes
TriggerStarts with !, lowercase, letters/digits/underscore/hyphen, max 32 chars. Example: !lost.
AliasesComma-separated. Up to 10. Each alias must be unique within your workspace.
MessageUp to 400 characters. Placeholders you can drop in: {count}, {user}, {displayname}, {channel}.
Counter valueThe starting number when creating; the current number when editing. Type a new number to override; click the reset icon next to it to set it back to 0.
Global cooldown (s)Time the bot must wait between any two uses of this counter, no matter who triggered it. 0 = no limit. Maximum 86 400 (24 h).
Per-user cooldown (s)0 = no limit. Same maximum.
Minimum roleSame six-tier scale as commands (Everyone / Follower / Subscriber / VIP / Moderator / Broadcaster).
EnabledIf off, the trigger is reserved but the bot stays silent.

Example

  • Trigger: !deaths
  • Aliases: !died, !rip
  • Message: Death count for this stream: {count}.
  • Cooldowns: 5 s global, 0 per-user

After seven invocations, chat displays: "Death count for this stream: 7."

Editing a counter

Click the edit icon on the row. The dialog shows the current count. If a chat use increases the counter while the dialog is open, your save will not undo that increase — streamion.bot only writes a new count value when the field is different from what it was when you opened the dialog. So you can safely edit the message text mid-stream without losing recent counts.

Two distinct permission concepts

Two different permission mechanisms apply to counters and should not be confused:

  • counters.manage controls which workspace members can view and edit the Counters page. By default this includes the Owner, every Admin, and every Moderator. See Team & permissions to adjust this.
  • Minimum role on each individual counter controls which Twitch chatters can trigger it (Everyone, Follower, Subscriber, VIP, Moderator, Broadcaster). This is independent of workspace membership.

A workspace Moderator can therefore edit a counter whose minimum role is Subscriber, even if they are not themselves subscribed to your Twitch channel.