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 🟢 ON or 🔴 OFF.

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, while announcement channels should be stricter.

Define Time Window​

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

Common configurations:

  • 10 seconds: Very strict, catches rapid spam
  • 30 seconds: Standard protection
  • 60 seconds: Lenient, allows for active conversations
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 or obvious spam bots.

Flood Control Use Cases​

Preventing Spam Bots​

Scenario: Protect against automated spam accounts.

Configuration:

  • Threshold: 5 messages
  • Time Window: 10 seconds
  • Action: Ban

Result: Instant removal of spam bots posting rapid messages.

Managing Overenthusiastic Users​

Scenario: Prevent accidental flooding by legitimate users.

Configuration:

  • Threshold: 10 messages
  • Time Window: 30 seconds
  • Action: Mute for 300 seconds

Result: Temporary timeout gives users a chance to slow down.

Protecting Announcement Channels​

Scenario: Maintain clean, organized announcements.

Configuration:

  • Threshold: 3 messages
  • Time Window: 60 seconds
  • Action: Mute for 600 seconds

Result: Strict control ensures only important messages are posted.

🛡️ 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 🟢 ON or 🔴 OFF.

Set User Join Threshold​

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

Recommended settings by community size:

  • Small groups (< 100 members): 5-10 joins
  • Medium groups (100-500 members): 10-20 joins
  • Large groups (500+ members): 20-50 joins
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

Typical settings:

  • 300 seconds (5 minutes): Quick reset for active monitoring
  • 600 seconds (10 minutes): Standard cooldown
  • 1800 seconds (30 minutes): Extended cooldown for manual review

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.

Benefits:

  • Increases community awareness
  • Alerts active members to be vigilant
  • Creates transparency

Use when: You want community involvement in monitoring.

DM Admins​

Notify administrators privately about the detected raid.

Benefits:

  • Discrete notification
  • Allows admin coordination
  • Doesn't alarm regular members

Use when: You want to handle situations quietly.

Kick New Members​

Automatically remove all users who joined during the detection window.

Benefits:

  • Immediate threat removal
  • Prevents spam from spreading
  • Strong deterrent

Use when: You face frequent raid attacks.

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.

Raid Detection Use Cases​

High-Security Community​

Scenario: Crypto project targeted by coordinated attacks.

Configuration:

  • Join Threshold: 10 users
  • Time Window: 60 seconds
  • Actions: Kick New Members + DM Admins
  • Cooldown: 600 seconds

Result: Immediate removal of raid participants with admin notification.

Growing Community​

Scenario: Legitimate growth with occasional spam attempts.

Configuration:

  • Join Threshold: 20 users
  • Time Window: 120 seconds
  • Actions: Warn Group + DM Admins
  • Cooldown: 300 seconds

Result: Alerts without disrupting legitimate growth.

Transparent Moderation​

Scenario: Community-driven monitoring.

Configuration:

  • Join Threshold: 15 users
  • Time Window: 90 seconds
  • Actions: Warn Group only
  • Cooldown: 1800 seconds

Result: Community awareness with minimal admin intervention.

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
  • Test settings during low-activity periods
  • Document your thresholds for team reference
  • 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

Integration with Other Features​

Flood Control + Warns​

Integrate flooding with warning system:

  1. First flood → Auto-warn
  2. Second flood → Mute
  3. Third flood → Kick/Ban

Raid Detection + Captcha​

Layered defense against raids:

  • Raid Detection identifies suspicious join patterns
  • Captcha verifies each new member
  • Combined approach stops both bots and coordinated human raids

Traffic Control + Notifications​

Stay informed about threats:

  • Enable "Flood Control" notifications
  • Enable "Raid Detection" notifications
  • Receive real-time alerts in your moderation channel

Traffic Control + Lockdown​

Emergency response protocol:

  1. Raid Detection triggers alert
  2. Admins manually activate Lockdown
  3. No new joins until situation resolved
  4. Review and remove raid participants

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 🟢 ON
  • 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 instead of Kick New Members
  • Combine with Captcha instead of auto-kick
  • Increase time window to reduce sensitivity
  • Review kicked users and manually re-invite

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

Advanced Strategies​

Dynamic Threshold Adjustment​

Adjust Traffic Control based on:

  • Time of day: Stricter at night when raids are common
  • Community events: Lenient during AMAs or announcements
  • Growth phases: Adjust Raid Detection for legitimate growth
  • Threat level: Tighten during active attack periods

Multi-Layer Defense​

Layer 1: Prevention

  • User Blacklist (suspicious usernames)
  • Captcha (verify humanity)

Layer 2: Detection

  • Raid Detection (unusual join patterns)
  • Flood Control (excessive messaging)

Layer 3: Response

  • Automated actions (kick, ban, mute)
  • Admin notifications
  • Manual review

Analytics and Monitoring​

Track Traffic Control effectiveness:

  • Number of flood incidents per day
  • Raid attempts per week
  • False positive rate
  • Average new member join rate
  • Patterns in attack timing

Use data to:

  • Optimize thresholds
  • Identify attack patterns
  • Schedule admin coverage
  • Improve overall security
tip

Remember to give the Fren One bot admin privileges with mute, kick, and ban permissions in your chat for all Traffic Control features to work properly. Test your settings during low-activity periods to ensure they're calibrated correctly.