Slow Mode & Cooldowns

Why Pacing Matters in Large Groups

In small Telegram groups, messages arrive at a comfortable pace that everyone can follow. But as a group grows past a few hundred members, the message volume can become overwhelming. Conversations overlap, important messages get buried, and members who cannot keep up with the rapid fire pace either stop participating or leave the group entirely. This is not a moderation problem in the traditional sense, because no one is breaking the rules. It is a structural problem caused by too many people talking at once, and it requires a structural solution.

Slow mode is that structural solution. By requiring a minimum interval between messages from each user, slow mode naturally paces the conversation and makes it possible for more members to participate meaningfully. Instead of a few fast typists dominating the chat, everyone gets a chance to be heard. The conversation becomes more thoughtful and less reactive, because members have time to compose their messages rather than rushing to get a word in before the chat moves on.

Group Wide Slow Mode

The /slowmode command sets a group wide slow mode that applies to all non admin members. When slow mode is set to 30 seconds, each member must wait 30 seconds between sending messages. During that cooldown, they can read the chat and compose their next message, but they cannot send it until the cooldown expires. This creates a natural rhythm in the conversation that makes it easier to follow.

The right slow mode interval depends on your group's size and culture. A group with 50 members might not need slow mode at all, because the conversation pace is naturally manageable. A group with 500 members might benefit from a 30 second slow mode. A group with 5000 members might need a 60 second or even 120 second slow mode to keep the conversation readable. The /slowmode 0 command disables slow mode entirely, returning the group to unrestricted messaging.

Command Cooldowns

Beyond message pacing, BotWave supports per command cooldowns that prevent individual members from spamming bot commands. Without cooldowns, a single member could repeatedly trigger commands like /ask or /imagine, filling the chat with bot responses and drowning out human conversation. Command cooldowns solve this by requiring a minimum interval between uses of each command from the same user.

The /cmdcooldown command sets a cooldown for a specific command. For example, /cmdcooldown ask 60 means each user must wait 60 seconds between uses of the ask command. This prevents any single member from monopolizing the AI assistant while still allowing everyone to use it regularly. Cooldowns can be set independently for each command, so you can have a short cooldown for quick commands and a longer one for resource intensive commands like image generation.

Per User Restrictions

Slow mode and cooldowns apply to all members equally, but sometimes you need to restrict specific users who are particularly active or disruptive. The /restrict command applies custom restrictions to a specific user, such as preventing them from sending media, links, or stickers while still allowing text messages. This is a graduated response that falls between a warning and a full mute, letting you limit the type of content a user can post without completely silencing them.

Per user restrictions are particularly useful for members who are not technically breaking any rule but whose posting patterns are disrupting the group. A member who posts too many stickers, too many links, or too many images can be restricted from posting those specific content types while still being able to participate in text conversation. This targeted approach addresses the specific behavior without removing the member from the community, which is more constructive than an all or nothing ban.

Admin Exemptions

Admins are automatically exempt from slow mode and command cooldowns, since they need to be able to respond quickly during moderation situations and do not need to be rate limited in their own group. The /slowmodeexempt command can also exempt specific non admin members, such as bots that post regular updates or trusted members who manage automated feeds.

This exemption system ensures that slow mode targets the members who actually need pacing, which is typically the general membership, without interfering with the people who need to operate at full speed. The result is a group where the conversation is paced for readability but the admin team and essential contributors can still function without artificial delays.

Available Commands