Counters: numbers that remember

at a glanceA command bumps the counter, the {counter:name} token shows it. The count survives every stream.

A counter is a named number the bot remembers between streams. Create one on the Counters page, then turn on Bump a counter in a custom command such as !death and pick the counter. Every use adds 1. Write {counter:deaths} in any response to show the current total.

!death adds 1 to the counter, and !deaths reads the total back with the token.

Counters need Loyalty Points Counters are stored by the Loyalty Points module. Switch it on first, or {counter:…} stays as literal text in chat.

02

Four ways to count

at a glanceWhole channel, per user, per command, or both. Pick one when you create the counter; it sticks.

Every counter has exactly one scope, chosen the moment it's created, and it stays that way for the counter's whole life. Scope answers one question: whose number is this?

Scope	What's counted
Whole channel	One shared total, everyone adds to the same number.
Per user	Each viewer gets their own number.
Per command or reward	One shared total for a single command or reward, every viewer pooled together.
Per user + command or reward	Each viewer gets a separate number for each command or reward.

Whole channel

Everyone bumps the same shared number. Perfect for a tally that belongs to the stream itself, not to any one viewer, like a running death count.

Whoever asks, the channel shows one shared total.

Per user

Each viewer gets a private number, untouched by anyone else's. Good for personal streaks: how many hugs someone has given, how many times they've won a game against you.

Same command, two viewers, two totally separate counts.

Per command or reward

The newest scope: one pooled total for a single command or channel-point reward, with every viewer adding to the same number. Ideal for "how many times has this specific reward been redeemed, total?"

Every redemption adds to the reward's own total, and any viewer can read it back.

Per user + command or reward

Combines both: every viewer gets a separate number for each command or reward that shares this counter. Bind one counter to two commands and each viewer ends up with one bucket per command, not one shared bucket for both.

MikanMeerkat's count for !hugs and their count for !highfives don't mix, even though both use the same counter.

Locked once created A counter's scope can't be changed afterward. Picked the wrong one? Delete it on the Counters page and create it again; the old values don't carry over.

03

Counting from chat

at a glanceA command with Bump a counter adds 1, and moderators can type a number to add or remove several.

Counters are made on the Counters page (next section). To count from chat, create a custom command such as !death, turn on its Bump a counter option and pick the counter. Moderators can then choose the step:

Command	What it does
`!death`	Adds 1 to the counter, whoever types it.
`!death 5` or `!death +5`	Adds 5. Only moderators, lead moderators and the broadcaster can pick the amount.
`!death -1`	Removes 1 (a negative number subtracts), for the same roles.
`!death 5` from a viewer	The number is ignored, the counter still adds 1.
`!death 0`, `!death abc`, or a number past 1,000,000	Falls back to adding 1.

The same command: a viewer adds 1, a moderator adds 5 in one go.

Set, reset and delete Changing the total itself happens on the Counters page: set it to any number, reset it to zero, rename it or delete it. In a response, {counter:deaths} only shows the value and never changes it.

Try it: bump the counter

#your_channel chat

Ayshacinder !death

ItsBagelBot The boss wins again.

SnackPackPanda !deaths

ItsBagelBot Oh no, 12 deaths so far.

04

The dashboard, and channel-point rewards

at a glanceThe Counters page for hands-on control, and how a reward binds to one.

The Counters page lists every counter on your channel. It is where you create, set, reset, rename and delete them.

dashboard.itsbagelbot.com/counters

Name: the same string you'd write inside {counter:…}.
Counts: the scope. Fixed once you create it.
A plain-language reminder of where counters get bumped from.

New counter panel: name it, pick a scope, done. Existing rows get +/- steppers for whole-channel counters, or a values table for the others.

Binding a counter to a channel-point reward

Every Channel Points reward can optionally keep a counter of its own, right from the reward's editor: type a counter name (new or existing), pick its scope, and every redemption bumps it. Use {counter} in the reward's chat reply to show the current total.

dashboard.itsbagelbot.com/channelpoints

Off by default, most rewards don't need one.
Per user + reward is usually the right call: each viewer builds their own redemption count for this reward.

The reward editor's counter block: a toggle, a name, and the same four scopes.

Try it in the builder The command builder can walk you through naming a counter and picking its scope, then hands you the finished {counter:…} token. Open the command builder