Counters running in a Discord server
Counters running in a Discord server
The dashboard offers to add the bot to the selected server
Discord asks where to add the bot
The eight permissions the invite link requests
The permissions the bot needs on this specific channel
Discord offers the three subcommands as you type
The reply mid-run, and after Creation completed.
The result in the channel list
Any voice, category, text or announcement channel will do
The channel page: the enable toggle, the template editor and the save button
Search the counter list from inside the editor
Each counter brings its own options
A display label only renames the chip in the editor
Preview resolves every counter to its current value
The server rail on the far left, the channel list next to it, and the server page on the right
An orange dot means the counters are running; a red pinging dot means the last update failed
What you see when the bot is not in the server yet
Formatting marks and the emoji picker on the left, Preview and Add counter on the right
Custom server emojis sit above the Unicode groups
The counter list, searchable by name and by keyword
A display label renames the chip in the editor, never the output
Preview replaces every chip with its real value and lists any errors below
The Enable template switch, the template editor with its Last updated caption, and the Save button
The permissions the bot needs on this specific channel
What the last failed update reported
The three controls inside Format settings.
One input per digit.
A display label renames the chip in the editor only.
The whole page: three settings and the buttons at the bottom.
The ten digit inputs, under the screen reader warning.
The Reset settings confirmation
A counter used as the value of an option, with its Edit counter and Remove counter buttons
The breadcrumb shows where you are; earlier entries are clickable
The Math counter with its two Members rows, and the second one filtered by role
The Replace counter with the HTTP counter as its input, and one replacement
Number turns the HTTP counter's text into a number, so Format settings apply
The channel page tells you when the bot last processed this template.
Avatar, username, badges and Logout at the top; the Settings card and the Danger zone below.
The Credit card with the custom bots of the account. The amount comes from a test account.
The Available server upgrades card, with the tooltip of the Upgrade server button
A red dot in the dashboard channel list marks a channel that needs attention.
When a template cannot be processed, the bot writes a placeholder in the server's language in place of the value.
The dashboard lists the permissions the bot needs in that channel; check each one yourself.
The red box carries the exact message; look it up in the table below.
The Add counter picker, scrolled to the top
Every option of the Members counter
Counting the members of one role
Counting who is playing a game right now
With "Count only banned members" checked the other filters are hidden
The Roles counter panel
The only option is "Filter by category"
No category selected, so the whole server is counted: the test server has 11 channels
One category selected under "Filter by category"
The Nitro Boosters counter panel
A Math counter dividing Members by Nitro Boosters
The two options of the Clock counter, with the Live preview underneath
A 24-hour clock in a voice channel name
Two Clock counters, one per timezone, in one template
A Date counter and a Clock counter in one template, with the rendered preview underneath
The two options of the Date counter, with the Live preview underneath
The weekday and the date in a voice channel name
A Date counter and a Clock counter side by side
The two options of the Countdown counter, with the Live preview underneath
The default format in a text channel topic
A days-only countdown in a voice channel name
The date comes from a nested counter, so the date field is replaced
The Twitch counter options in the template editor
The same counter live and off air
The YouTube counter options in the template editor
A voice channel driven by a YouTube counter
The Reddit counter options in the template editor
A voice channel driven by a Reddit counter
The Game counter panel
The counter in the template after Online: , and the Game panel it opens
The query port is not the port players connect to
The Display and Username options
The rendered result in a voice channel
The HTTP counter panel with every option filled in. The API key here is a placeholder, so Test response still holds the built-in sample and Preview reports that the path is not in it
The response and the value the Data path pulls out of it
The counter sits between New York and Β°C in the template
The counter after the text LA AQI - , with the IQAir endpoint, a one hour lifetime and the data path filled in
Template: BTC: $81502.27, the live price when this was captured
The Math counter panel: Operation type and Number list
A Multiplication of a nested Division and 100, with compact notation on. On the small test server 1 of 2 members is online, so the channel reads Online: 50%
The Number counter panel, with a nested HTTP counter in the Number field
HTTP fetches the price as text; the Number counter around it makes compact notation apply
The Concat counter panel: a single Text list
The Replace counter panel: Input text and one replacement card
The stack in the dashboard: an HTTP counter in Input text, one replacement card, and the whole Replace counter inside a Number counter
The Display dropdown
The rendered result in a voice channel
Type / and pick Member Counter to see the list.
` string; anything else falls back to the generic "Something went wrong" message.
* The error ID is the OpenTelemetry trace id of the interaction span and only the hosted bots produce one. A self-hosted bot shows the literal `Error ID: {{ERROR_ID}}`; read the bot's own log instead.
The three subcommands, and the option each one asks for.
The result, seen by a member without administrator permissions.
The Twitch set on the left, the YouTube set on the right.
The same message mid-run and after "Creation completed."
The reply, with the clickable /setup server mention and the dashboard button.
All the links in one reply, ending with the running version.
Run inside a server by someone with Manage Server, so all three buttons show.
The right-click route, on a member in the member list.
Your own profile, with the Delete data button underneath.
Nothing is deleted until you press Yes.
A custom bot in the dashboard: its Discord profile, the Control panel and the Subscription card
The minus and plus buttons set the size of the subscription
The Create custom bot button sits above the server list
Name the application and click Create
Presence Intent and Server Members Intent on, Message Content Intent off
The Reset Token button on the Bot tab. The new token is shown only once, right after you confirm
The OAuth2 tab of the same application
Paste the token into Discord Bot Token and click Save
The Setup subscription dialog with the terms checkbox and both payment methods
The power button in the Control panel, with the tooltip showing the current state
The Bot configuration card, with the live Status preview on the right
The Control panel card with the bot stopped: only the title and the power button
The Subscription card: quota picker, price, and the control buttons
The Setup subscription dialog, with the agreement checkbox ticked and both payment methods shown
The Available server upgrades card on the account page
The Upgrade server page with the UPGRADE NOW button and its footnote
| Self-hosted bot | Custom bot |
|---|---|
| Free. You only pay for the hardware. | Paid, per quota unit per quarter. |
| You install, update and back it up. | We install, update and back it up. |
Full control over your data and over every setting in .env. | Control panel with the settings that matter, on our hosting. |
| Runs as long as your machine is on. | Runs 24/7 on our infrastructure. |
| No official support beyond this guide. | Support from the team. |
| Software | Notes |
|---|---|
| Docker, with Docker Compose v2.23.1 or newer | Install Docker. Check your version with docker compose version. Older versions cannot read the compose file. |
| git | Install git. |
| A CPU with AVX support | The database runs mongo:7, and MongoDB 5.0 and newer need AVX. Older processors lack it, and some VMs and NAS boxes hide it from their guests. On Linux, check with grep -o avx /proc/cpuinfo | head -1. |
| Variable | What to put in it |
|---|---|
COOKIE_SECRET | A random string of at least 32 characters. On macOS or Linux, openssl rand -base64 32 generates one. Shorter values are rejected on start-up. |
DISCORD_CLIENT_ID | Your application's client ID. |
DISCORD_CLIENT_SECRET | Your application's client secret. |
DISCORD_BOT_INSTANCE_TOKEN | Your bot token. |
WEBSITE_URL | Where you will open the dashboard. Leave http://localhost:3000 unless you put the bot behind a reverse proxy or a domain. Never add a trailing slash. |
DISCORD_OAUTH2_REDIRECT_URI | Must match the redirect URL you saved in the Developer Portal character for character. Leave http://localhost:3000/api/auth/callback if you kept the default. |
| Variable | Why it matters |
|---|---|
PUBLIC_BOTS_IDS | Ships as '["main", "premium", "beta"]'. Your install runs a single bot with the id main, so the other two ids make your dashboard show two bots that are permanently offline. Set it to PUBLIC_BOTS_IDS='["main"]'. |
MAIN_DISCORD_CLIENT_ID | Ships as 478567255198662656, the official Member Counter application. /invite builds its link from this value, so until you change it, /invite on your own bot invites ours. Set it to the same value as your DISCORD_CLIENT_ID. |
Your servers appear in the picker on the left
| Command | What it does |
|---|---|
docker compose ps | Shows which services are running. |
docker compose logs -f bot | Follows the bot's log. Swap bot for backend, frontend or website. |
docker compose restart bot | Restarts one service. It does not pick up .env changes; use docker compose up -d for that. |
docker compose up -d | Starts everything in the background, and applies .env changes. |
docker compose down | Stops and removes the containers. |
One published port, two destinations behind it.
One limiter for one token, instead of one limiter per process.
Your badges on the account page, with one description shown
The reply of /profile, with the Badges field