For the complete documentation index, see llms.txt. This page is also available as Markdown.

What is a custom bot

A custom bot is Member Counter running under your own Discord bot token, on our hosting, with every feature turned on.

A custom bot is Member Counter logged in with your own Discord application. It uses your name, avatar and status. It is only in the servers you invite it to, and every feature is on.

We host it and keep it updated. You bring the token and pay the subscription.

The dashboard page of a custom bot
A custom bot in the dashboard: its Discord profile, the Control panel and the Subscription card

How it compares

Public bot
Legacy premium bot
Custom bot
Self-hosted bot

Every 10 minutes

Every 5 minutes

Every 5 minutes

Every 5 minutes

Member filters by role, account type, game and voice channel

No

No

Yes

Yes

Online, Idle and Do Not Disturb

Only an approximate Online, which includes Idle and Do Not Disturb

Same as the public bot

Exact, and told apart

Exact, and told apart

Twitch and YouTube counters

No

Yes

Yes

Yes, once you add the API credentials

Own name, avatar and status

No

No

Yes

Yes

Who runs it

We do

We do

We do, under your token

You do, on your own machine

Cost

Free

Only for servers with a legacy server upgrade

From €5.00 per quarter

Free, you pay for the machine

A self-hosted bot has these features when you keep the default settings and enable the privileged intents on your application. See Configuration.

A custom bot is per bot, not per server. One custom bot can sit in as many servers as you want, as long as the subscription covers the members it has to keep in memory.

Start here

How to get a custom botCreating a Discord bot accountSetting up your custom bot

Once it is running, see Changing the bot's status, Control panel and Managing your subscription. If you already hold server upgrades, see Legacy Premium vs. Custom Bot.

The free alternative

Member Counter is open source, so self-hosting gives you the same features for free on your own machine.

If you get stuck, ask at the support server.

Technical details
  • The Update channels job runs on cron 0 */5 * * * * when DISCORD_BOT_INSTANCE_IS_PREMIUM is true and on 0 */10 * * * * when it is false. Custom bots are launched with that flag and DISCORD_BOT_INSTANCE_IS_PRIVILEGED hard-coded to true, and .env.example ships both as true.

  • The bot always asks for the Guilds, GuildEmojisAndStickers and GuildModeration intents, adds the privileged GuildMembers and GuildPresences only when it is privileged and premium, and GuildVoiceStates when it is premium. The member, presence and voice caches follow the same rule.

  • Without those intents the Members counter can only return guild.approximateMemberCount, guild.approximatePresenceCount (served for both the Online filter and the one that groups Online, Idle and Do Not Disturb) and the two subtracted for Offline. The role, account type, game and voice filters and the Idle and Do Not Disturb statuses throw BOT_IS_NOT_PREMIUM, or BOT_HAS_NO_ENOUGH_PRIVILEGED_INTENTS when the bot is premium but the intents are off.

  • The Twitch and YouTube evaluators check for premium before anything else, so they fail as a whole on the public bot instead of option by option. Self-hosting them needs YOUTUBE_API_KEY for YouTube and TWITCH_CLIENT_ID with TWITCH_CLIENT_SECRET for Twitch.

  • A custom bot runs as a single-shard StatefulSet (shard 0 of 1) with DISCORD_BOT_INSTANCE_DISCORD_API_RPS=50 against the public bot's 45, DISCORD_BOT_INSTANCE_DEPLOY_COMMANDS=true so it registers its own slash commands, and the bot-list stats tokens blank. Custom bot launch settings live in packages/services/src/customBots/index.ts.

Last updated