What it looks like
You create a channel that nobody can enter, and the bot writes the number into its name, for example 👥 ┃ Members: 1,234. Several counters below one another form a small block at the very top of the channel list.
Setup
The seven counter types
| Type | Counts |
|---|---|
| Members | all members including bots |
| Humans only | members without bots |
| Bots only | bots only |
| Boosts | active server boosts |
| Boost level | the level reached (0 to 3) |
| Channels | number of all channels |
| Roles | number of all roles |
We deliberately do not offer an “Online” counter. It would need a special access permission that this bot does not have, offering a field that permanently shows zero would be worse than none at all.
Why only every ten minutes
This is the most important quirk of this building block, and it explains why some counters in other bots show permanently wrong numbers.
Discord allows only two renames per channel in ten minutes. Every further one is discarded without comment, there is no error message, the name simply stays as it is. Anyone who renames on every join uses up the quota within seconds and then shows outdated numbers for hours.
That is why our counter works on a fixed ten-minute cycle. And it only renames when the number has really changed, a quiet server therefore uses up no quota at all, so the next real change takes effect immediately.
Name templates
The template is free, {count} is replaced, everything else stays as it is. A few examples:
👥 ┃ {count}, compact and fits on narrow screens too.Members: {count}, clear, but wider.💎 Boosts: {count}, for the boost counter.
Discord limits channel names to 100 characters; the bot shortens them where necessary. The number is grouped according to your server's language, 1.234 in German and 1,234 in English.
Without a subscription
Without an active subscription the first counter is updated. Further counters remain stored in full and start running again as soon as a subscription exists, nothing is lost just because a subscription ends.
Common pitfalls
- The number does not change. Wait for one full ten-minute cycle. If it stays that way, the bot lacks the “Manage Channels” permission for this channel.
- The number is too low. Shortly after a restart the member cache is not yet complete. That is why the first run is deliberately delayed.
- The channel can be joined. That is a permission setting of your server, not of the bot, take the Connect permission away from
@everyone.