Skip to main content
← Back to Blog

Telegram Anti-Flood Protection: Stop Message Flooding in Groups

4 min read
telegram antiflood spam rate limiting moderation

Telegram Anti-Flood Protection: Stop Message Flooding in Groups

Message flooding — when one person sends dozens of messages in seconds — is one of the most disruptive things that can happen in a Telegram group. It buries real conversations, annoys active members, and can crash mobile apps with notification spam.

Whether it's a troll trying to disrupt your community, a bot attack, or someone who just doesn't know how to use the "edit" button, anti-flood protection stops it automatically. It is one of the essential layers in any comprehensive group management setup.

What Is Message Flooding?

Flooding is when a user sends an unusually high number of messages in a short time period. This can be:

  • Intentional trolling — Someone copy-pasting the same message or random text to disrupt the group
  • Bot attacks — Automated accounts sending messages at machine speed
  • Accidental — A user pasting a long text that Telegram splits into multiple messages, or someone excited and typing fast
  • Raid flooding — Multiple accounts coordinated to flood simultaneously

Without protection, admins have to manually mute or ban each offender — which is too slow during an active flood.

How Anti-Flood Works in OmniGest

OmniGest's anti-flood system monitors message frequency per user and automatically takes action when someone exceeds the configured threshold.

The Three Settings

1. Max Messages — The maximum number of messages a user can send within the time window before triggering the flood filter. Default: 5 messages.

2. Time Window — The time period in seconds for counting messages. Default: 10 seconds.

So with defaults: if a user sends more than 5 messages in 10 seconds, they trigger the flood filter.

3. Action — What happens when someone floods: - Mute — User is silenced temporarily (default) - Kick — User is removed from the group - Ban — User is permanently banned

Cooldown Period

After being caught by the flood filter, the user enters a cooldown period. During this time, any messages they try to send are automatically deleted. This prevents them from resuming the flood immediately after their mute expires.

Setting Up Anti-Flood

Step 1: Add OmniGest to your group

Add @OmniGest_bot and make it admin with delete and ban permissions.

Step 2: Configure via /config

Send /config in a private chat with the bot. Select your group, then press AntiFlood [OFF].

Step 3: Adjust thresholds

The configuration menu lets you:

  • Toggle ON/OFF — Enable or disable anti-flood
  • Set max messages — Increase for active groups, decrease for strict moderation
  • Set time window — Shorter windows catch faster floods, longer windows are more lenient
  • Choose action — Mute (recommended), kick, or ban

Step 4: Test

Send several messages quickly in the group. If you exceed the threshold, the bot will take the configured action. Note: admins are exempt from anti-flood.

Casual community (< 200 members): - Max: 8 messages / 10 seconds - Action: Mute - Why: Generous threshold, people chat fast in small groups

Active group (200-1000 members): - Max: 5 messages / 10 seconds - Action: Mute - Why: Balanced — catches floods without bothering active chatters

Large group (1000+ members): - Max: 4 messages / 8 seconds - Action: Mute (or Kick for repeat offenders) - Why: Tighter limits prevent small floods from escalating in busy groups

Under attack: - Max: 3 messages / 5 seconds - Action: Ban - Why: Maximum protection during active raids. Revert to mute after the attack subsides.

Anti-Flood vs Anti-Spam

These are different protections that complement each other:

Feature Anti-Flood Anti-Spam
Detects Message frequency (too many messages) Message content (spam links, forwarded spam)
Triggers on Speed of posting What is posted
Best for Trolls, raids, bot floods Link spam, promotions, scam messages
Works together? Yes — enable both for comprehensive protection

For full protection, combine anti-flood with AntiSpam, Word Filter, and Captcha.

How OmniGest Handles Edge Cases

What about admins? Admins are never affected by anti-flood. They can send as many messages as they want.

What about media? Photos, videos, stickers, and GIFs count as messages. A user sending 10 GIFs in a row will trigger the flood filter.

What about forwards? Forwarded messages count. Someone forwarding 20 messages from another chat will be caught.

What about edited messages? Editing an existing message does NOT count as a new message. Only new messages increment the counter.

Combining Anti-Flood with Other Tools

For maximum group protection, enable this stack:

  1. Captcha — Block bots at join
  2. Anti-Flood — Stop message flooding
  3. AntiSpam — Block spam content
  4. Word Filter — Block specific words/phrases
  5. AI Moderation — Catch everything else with AI

OmniGest lets you enable all five from one /config menu. No need for separate bots.

Get Started

Protect your group from message flooding in 30 seconds. Add @OmniGest_bot to your group, open /config, and enable AntiFlood. It's free, instant, and fully configurable.

For complete documentation, see the AntiFlood guide. New to OmniGest? Start with the Getting Started guide.