Skip to main content

⚠️ Warns

The Warns feature allows moderators to issue warnings to users who break community rules. It serves as an escalating disciplinary system, with configurable actions triggered when a user exceeds a set warning limit.

Overview​

This feature ensures that rule enforcement is fair and transparent. By tracking warnings over time, moderators can implement a graduated response system that gives users opportunities to correct their behavior before more severe actions are taken.

Configuration​

To access Warn Settings:

  1. Use the /settings command in your chat
  2. Navigate to 🛡️ Moderation → ⚠️ Warns
  3. Use the Toggle Warns option to turn the feature 🟢 ON or 🔴 OFF

Configuring Warn Settings​

Notifications​

Define the message sent by the bot when the !warn command is issued by an admin or a user with permission to issue warnings via Fren One.

Customization options:

  • Create a custom warning message that fits your community's tone
  • Include information about the warning and consequences
  • Reference community rules or guidelines
Custom Warning Message

Make your warning message informative but not harsh. Include what rule was broken and how users can avoid future warnings.

Warn Limit​

Define how many warnings a user can receive before an automatic action is taken.

Prompt: "Set the maximum number of warns a user can receive before being penalized."

Options are fully customizable, allowing you to set an appropriate threshold for your community.

Example Configurations
  • Strict moderation: 2-3 warnings
  • Moderate moderation: 3-5 warnings
  • Lenient moderation: 5+ warnings

Warn Actions​

Choose what happens when a user reaches the warn limit.

Prompt: "Select the type of action to be taken when a user reaches the warn limit (e.g., mute, ban, kick)."

Available actions:

  • Mute: Restricts the user from sending messages in the group
  • Kick: Temporarily removes the user, allowing them to rejoin later
  • Ban: Permanently removes the user from the group
Choose Wisely

The warn action should match your community's tolerance level. Consider starting with Kick for first-time limit violations and escalating to Ban for repeat offenders.

Expiry​

Define the time period after which a user's warns will expire automatically. 📝 Note: If set to 0, warns will not expire.

Issuing Warnings​

Moderators can issue warnings in two ways:

By Replying to a Message​

Respond to the offending user's message with the !warn command.

[User posts inappropriate content]
Moderator: !warn

Result: User receives a warning with context of the offending message.

By Mentioning the User​

Use the !warn @username command to warn a specific user.

Example:

!warn @JohnDoe

Result: User receives a warning without reference to a specific message.

What Happens When a Warning is Issued​

When a warning is issued:

  1. The bot increments the user's warning count
  2. If in-chat warn messages are enabled, the bot sends a visible warning in the group
  3. The user is notified of their current warning count
  4. If the warn limit is reached, the configured action is automatically executed
Warning Tracking

All warnings are tracked per user. You can review a user's warning history to make informed moderation decisions.

Who Can Issue Warnings​

Warnings can be issued by:

  • Group Admins: Always have permission to warn users
  • Users with Warn Permission: Assigned through the Fren One Roles system
Role-Based Permissions

Learn more about assigning warn permissions in the Roles documentation.

Common Use Cases​

Progressive Discipline System​

Scenario: Gradually escalate consequences for rule violations.

Configuration:

  • Warn Limit: 3 warnings
  • Warn Action: Kick
  • Notifications: Custom message explaining the violation

Workflow:

  1. Warning 1: User informed of rule violation
  2. Warning 2: User reminded they're approaching the limit
  3. Warning 3: User automatically kicked from group

Strict Zero-Tolerance Policy​

Scenario: Quick response to serious violations.

Configuration:

  • Warn Limit: 1 warning
  • Warn Action: Ban
  • Notifications: Clear message about zero-tolerance policy

Use: For serious violations like spam, scams, or harassment.

Community Moderation Team​

Scenario: Empower trusted members to help moderate.

Configuration:

  • Warn Limit: 5 warnings
  • Warn Action: Mute
  • Permissions: Grant warn permission to trusted community members via Roles

Result: Distributed moderation with clear escalation path.

Educational Approach​

Scenario: Focus on educating users about rules.

Configuration:

  • Warn Limit: 5 warnings
  • Warn Action: Kick (not ban)
  • Notifications: Detailed explanation of violation and how to avoid it

Philosophy: Give users multiple chances to learn and improve.

Best Practices​

Effective Warning System
  • Set clear rules so warnings are predictable and fair
  • Use custom notification messages to explain violations
  • Set warn limits appropriate to your community size and culture
  • Document what behaviors warrant warnings
  • Be consistent in applying warnings across all users
  • Review warning history before taking additional action
  • Consider temporary mutes before issuing warnings for minor offenses
  • Use warnings for fixable behaviors, not for immediate ban-worthy offenses
Fair Enforcement
  • Apply warnings consistently to all members (except whitelisted users if applicable)
  • Don't stack multiple warnings for a single incident
  • Keep records of what each warning was for
  • Allow users to appeal warnings if they believe it was unfair
  • Consider warning decay (manually reset after good behavior period)
  • Communicate warning counts to users so they know their standing

Managing Warnings​

Checking Warning Count​

Moderators can check a user's warning count to make informed decisions about further action.

Resetting Warnings​

While automatic warning reset may not be available, admins can:

  • Manually track warning resets for reformed users
  • Implement a grace period after which warnings are forgiven
  • Use discretion when applying the final warning before action
Warning Forgiveness

Consider implementing a policy where warnings expire after a period of good behavior (e.g., 30 days without violations).

Troubleshooting​

!warn command not working?

  • Verify the Warns feature is toggled 🟢 ON
  • Ensure the bot has admin privileges
  • Check if the user issuing the warning has permission
  • Verify you're using the correct command syntax

Warnings not triggering actions?

  • Confirm the warn limit is set correctly
  • Check if the warn action is properly configured
  • Ensure bot has permissions for the action (mute/kick/ban)
  • Verify the warned user isn't whitelisted or an admin

Can't see warning count?

  • Warning counts may not be publicly visible
  • Admins should have access to user warning history
  • Consider keeping a manual log of warnings for reference

Users not receiving warning notifications?

  • Verify notification messages are configured
  • Check if in-chat notifications are enabled
  • Ensure the bot has permission to send messages
  • Test with a known user to verify functionality

Advanced Warning Strategies​

Tiered Warning System​

Implement different warn limits for different violation types:

Minor Violations (spam, off-topic):

  • Limit: 5 warnings
  • Action: Mute for 24 hours

Moderate Violations (rudeness, flooding):

  • Limit: 3 warnings
  • Action: Kick

Major Violations (harassment, scams):

  • Limit: 1 warning
  • Action: Ban

(Note: This requires manual tracking and may not be fully automated)

Warning Categories​

Document different warning types:

  • W1: Spam/Off-topic
  • W2: Inappropriate content
  • W3: Harassment/Toxicity
  • W4: Scam attempts

Track categories manually to understand violation patterns.

Integration with Other Features​

Combine Warns with:

  • Report System: Use warnings as aftermath action for approved reports
  • Triggers: Auto-warn for specific keywords or patterns
  • Filters: Apply warnings when filters are violated
  • Roles: Reward users with zero warnings with special roles

Probation Period​

After reaching warn limit but not banned:

  1. Kick user from group
  2. Allow rejoin with clear probation notice
  3. Set lower warn limit for probation period
  4. Ban if violations continue
tip

Remember to give the Fren One bot admin privileges in your chat for all warning features to work properly. Users with warn permissions must also be designated through the Roles system.