How to set up a Discord member count bot

Before you start

• Have an online Build Discord Bots bot in the server you manage. The Statistics module is included on Free, but the staff member creating or editing stat channels needs the Discord permissions required by the module: Manage Channels for channel operations and Manage Server for the update interval.
• Choose a category where read-only counter channels make sense. The bot must be able to create and manage channels there. Use a test category if your server has an established public layout you do not want to disturb.

1. Enable the free Statistics module

   Open your bot’s Modules tab, confirm Statistics is enabled, and open its Settings. Unlike the Pro-only modules in some other guides, Statistics is included on the Free plan. Select the server you intend to configure before choosing a category or interval. The dashboard controls are shared with the Discord commands, so a later command change appears in the same saved configuration. Wait until the bot is online: a channel counter cannot create or rename Discord channels while the bot is unavailable.

   Counters should be treated as a display of a Discord server property, not an analytics report. A member count can include accounts that do not participate, and an online count depends on Discord presence data and the bot’s available view of the server. Decide what the label means before putting it in a prominent category. “Members: {count}” is clearer than a vague label that looks like a live activity promise. Do not publish a target or benchmark simply because the channel makes a number visible.

2. Choose a Statistics Category

   In Settings, select Statistics Category if you want newly created counters grouped under a parent category. None means no parent category, which may be fine for a test but is rarely tidy in a busy server. The setting tells the module where future stat channels should be created; it does not move unrelated channels or reorganize your existing server. Save the category choice and verify that the bot role has the permission to create and manage channels there before running a creation command.

   Keep the category permissions simple. Members usually only need to view a counter channel, while staff may need to adjust its position or delete a test. The module uses Discord voice channels as the visible counter channels, renaming them as statistics update. Do not assume a voice channel invites conversation merely because Discord uses that channel type; your permission choices determine whether members can connect. A read-only display category can make the counter visible without creating another place for chat.

3. Create the member count channel

   Run `statchannel` with the members type from an account with Manage Channels. The command creates a statistics channel; its optional format can include the {count} placeholder. Start with a simple format such as “Members: {count}” so the resulting channel name tells visitors exactly what they are seeing. The module supports several types, but create one at a time and inspect it before adding more. A member counter is the best first test because it is easy to recognize in the server channel list.

   After the command completes, look in the selected category or server list for the newly created channel. Check its name, position, and permissions as a normal member as well as a staff member. If the channel is missing, verify the bot’s Manage Channels permission and the selected category’s overwrites. Do not rerun the command repeatedly without checking: your goal is one clear counter, not a pile of similarly named channels. Remove a mistaken test with statremove once you know which type it created.

4. Format the counter without hiding its meaning

   Run `statformat` to change a statistic channel’s format. It takes a type and a format containing {count}, so retain that token when you want the live value shown. A format that omits the token may be descriptive but will not display the number you intended. Keep names short enough to scan in Discord’s sidebar and avoid emojis that make distinct counters hard to identify. If you add a second counter later, give it a precise label, such as humans or boosts, rather than several channels all named “Stats.”

   The supported stat types include members, humans, bots, online, channels, roles, boosts, boosters, text, and voice. These are separate choices, not different interpretations of the same member total. Do not equate humans with members or online with active participation in an announcement. A counter is most useful when its label describes the module’s data source honestly. Ask a moderator to read the sidebar as a new member would; if they cannot tell what a count represents, simplify the wording.

5. Set a sensible refresh interval

   Set Auto-update Interval (minutes) in the dashboard, or use `statinterval` in Discord. This controls how often the bot refreshes all statistics channel names. The command requires Manage Server because it changes a server-wide behavior. Choose an interval that keeps labels current enough for your purpose without treating every ordinary join or leave as an emergency. The setting is not an activity dashboard and does not promise real-time, event-by-event updates. Save the change and give the bot time to perform its next refresh.

   You can use `statupdate` to request an update when staff need to check a configuration change. Test it after creating the channel, then compare the displayed number with the server’s visible member count knowing Discord’s own state can change. If a counter does not update, first confirm the Statistics module is enabled and the bot can manage that channel. Moving or deleting the channel manually can change what the bot can reach, so use the module tools where possible and record any server layout changes for staff.

6. Maintain a small, useful counter set

   Run `statlist` to see active statistic channels. It is a quick way to audit what the module is managing before you change formats or categories. If a counter is no longer useful, use `statremove` for its type instead of leaving stale labels in the server. A compact list is easier for members to scan and easier for moderators to troubleshoot. If you later add an online or boosts counter, repeat the same permission and label review rather than assuming every stat type has the same audience or meaning.

   Statistics remains a Free module, so it is a practical place to begin when you sign up for Build Discord Bots and want a hosted bot feature without a Pro-only commitment. The member-count setup does not depend on Pro. Review the counter category after server redesigns, and avoid building moderation, access, or rewards rules around a displayed number that can legitimately change. A clear counter supports orientation; it should not become pressure on members.