Skip to main content

🚦 Traffic Control

Traffic Control helps protect your community from two major threats: message flooding (spam) and coordinated raid attacks. This feature includes Flood Control for managing excessive messaging and Raid Detection for identifying suspicious member influxes.

Overview​

Traffic Control provides automated protection against:

  • Flood Control: Users sending too many messages in a short period
  • Raid Detection: Sudden influxes of new members (potential spam or bot attacks)

These features work together to maintain a healthy, secure community environment by automatically detecting and responding to abnormal activity patterns.

Configuration​

To access Traffic Control settings:

  1. Use the /settings command in your chat
  2. Navigate to 🛡️ Moderation → 🚦 Traffic Control
  3. Configure Flood Control and/or Raid Detection settings

💬 Flood Control​

Flood Control helps manage users who send too many messages in a short period. This prevents spam, reduces chat clutter, and stops disruptive behavior.

Configuring Flood Control​

Enable/Disable Flood Control​

Use the Status Toggle to turn the Flood Control feature 🟢 Enabled or 🔴 Disabled.

Set Message Threshold​

Configure the number of messages a user must send in the selected time window to be restricted.

Example settings:

  • Strict: 5 messages (low tolerance)
  • Moderate: 10 messages (balanced)
  • Lenient: 15+ messages (high tolerance)
Choosing Threshold

Consider your community's conversation style. Active discussions may need higher thresholds.

Define Time Window​

Set the period of time (in seconds) to monitor for excessive messages.

Example

Setting "10 messages in 30 seconds" means if a user sends 10+ messages within any 30-second window, Flood Control activates.

Select Action​

Choose the action to apply when Flood Control is triggered:

  • Mute: Temporarily silence the user. Specify the duration (e.g., 240 seconds)
  • Kick: Remove the user from the group
  • Ban: Permanently ban the user from the group
Action Severity

Start with Mute for first offenses. Reserve Kick/Ban for repeat offenders.

🛡️ Raid Detection​

Raid Detection protects your group from sudden influxes of new members. This feature automatically detects and responds to potential spam, bot activity, or coordinated attacks.

Configuring Raid Detection​

Enable/Disable Raid Detection​

Use the Status Toggle to turn the Raid Detection feature 🟢 Enabled or 🔴 Disabled.

Set User Join Threshold​

Define the number of new members that must join the group within the specified time window to trigger a raid detection.

Calibrating Threshold

Monitor normal join patterns during your community's growth phases to set appropriate thresholds.

Define Time Window​

Specify the period of time (in seconds) to monitor for excessive messages.

Common configurations:

  • 60 seconds: Very sensitive, catches fast raids
  • 120 seconds: Balanced detection
  • 300 seconds: Less sensitive, fewer false positives
Example

Setting "15 joins in 120 seconds" means if 15+ users join within any 2-minute window, Raid Detection triggers.

Set Cooldown Period​

Configure the cooldown period, which determines how long the system will wait before monitoring for new raids after one is detected.

Purpose:

  • Prevents repeated alerts for the same raid event
  • Allows time for manual intervention
  • Reduces notification spam

Choose Actions​

When a raid is detected, you can customize the bot's response:

Warn Group​

Post an alert in the group to notify members of the suspicious activity.

DM Admins​

Notify administrators privately about the detected raid.

Kick New Members​

Automatically remove all users who joined during the detection window.

Kick New Members Carefully

This action removes ALL users who joined during the detection period, including potentially legitimate members. Use with caution and consider enabling captcha as an alternative.

Best Practices​

Effective Traffic Control
  • Monitor normal activity patterns before setting thresholds
  • Start with lenient settings and gradually tighten as needed
  • Use Mute for Flood Control before escalating to Kick/Ban
  • Enable multiple Raid Detection actions for comprehensive response
  • Review and adjust thresholds after community growth
  • Combine with Captcha for additional raid protection
Avoiding False Positives
  • Don't set Flood Control too strict during active discussions
  • Account for legitimate growth spurts in Raid Detection
  • Use appropriate cooldown periods to prevent alert spam
  • Review kicked users to identify false positives
  • Provide clear guidelines about acceptable message rates
  • Consider time zones and global community activity patterns
  • Use Warn Group instead of Kick New Members when unsure
Troubleshooting

Flood Control Issues​

Legitimate users being muted?

  • Increase message threshold
  • Extend time window
  • Review conversation patterns
  • Consider whitelisting active contributors

Spam still getting through?

  • Lower message threshold
  • Reduce time window
  • Change action to Kick/Ban for repeat offenders
  • Combine with Word Blacklist and Triggers

Flood Control not activating?

  • Verify feature is toggled 🟢 Enabled
  • Check threshold and time window settings
  • Ensure bot has mute/kick/ban permissions
  • Test with a known scenario

Raid Detection Issues​

False raid alerts?

  • Increase join threshold
  • Extend time window
  • Increase cooldown period
  • Disable during planned growth campaigns

Missing actual raids?

  • Lower join threshold
  • Reduce time window
  • Enable multiple detection actions
  • Review recent join patterns

Legitimate users being kicked?

  • Use Warn Group or DM Admins instead of Kick New Members
  • Combine with Captcha instead of auto-kick
  • Increase time window to reduce sensitivity

Too many notifications?

  • Increase cooldown period
  • Adjust thresholds to be less sensitive
  • Use DM Admins instead of Warn Group
  • Disable notifications for Flood Control if too frequent

On this page