Warning System
SYNTHET's warning system creates a structured progression of consequences. Warnings accumulate, trigger automatic escalation at configured thresholds, and optionally decay after periods of good behavior. This gives users clear opportunities to improve while protecting your community.
How the Warning System Works
The Warning Lifecycle
- 1. Warning Issued: Moderator uses /warn @user - warning recorded and user notified via DM
- 2. Counter Increments: User's warning count goes up (e.g., 1, 2, 3...)
- 3. Check Threshold: System checks if count matches any escalation threshold
- 4. Action Triggered: If threshold reached, automatic action executes (mute, kick, ban)
- 5. Decay (Optional): Warnings age out after configured period of good behavior
Unlike one-off punishments, warnings give users a "score" that reflects their overall behavior. A user with 2 warnings who improves their behavior is different from a first-time violator.
Escalation Thresholds
Configure what happens when a user reaches specific warning counts. These are fully customizable to your community's standards:
First Warning
No automatic action. User informed of issue.
Default: Mute for 1 hour
User receives second chance notice. At 3 warnings, they're silenced to cool off.
Default: Mute for 24 hours
Escalation shows severity. User is given a full day to reflect on behavior.
Default: Kick from server
Clear message: repeated violations result in removal. User can rejoin if behavior improves.
Default: Permanent ban
After 10 warnings, user is banned. Pattern shows they won't follow rules.
Customizable: You can adjust these thresholds and actions via Dashboard → Protection → Moderation → Settings → Warning Escalation. Different servers have different cultures - set thresholds that fit yours.
Warning Decay & Forgetting
Optionally configure warnings to expire after good behavior, allowing users to "earn" a fresh start:
How Decay Works
Each warning has an age. When the warning reaches the configured decay period WITHOUT new violations, it automatically expires:
Configuration Options
- Enable Decay:Toggle via Dashboard. If disabled, warnings never expire unless manually removed.
- Decay Period:Days until a warning expires (typically 14, 30, 60, or 90 days). No standard - choose based on your community.
- Reset on New Warning:When user gets new warning, does oldest warning restart its decay clock or continue counting? Configurable.
Best Practice
Enable decay with a 30-60 day period. This shows users they can improve. It also prevents the system from being "permanently scarred" by old infractions. A user who was warned 6 months ago and has been perfect since shouldn't be treated as a repeat violator.
Warning Commands
/warn <user> [reason]
Issue a warning to a user. Increments their warning count and triggers escalation if threshold reached.
User gets DM: "You've received a warning (Reason: Spamming in general). You now have 1 warning. At 3 warnings, you'll be muted."
/warnings <user>
View all warnings for a user including timestamps and reasons.
Shows: [1] Spamming (Jan 5) | [2] Harassment (Jan 10) | [3] Expired: Bad language (Dec 1) [auto-decay]
/warnings remove <user> <id>
Remove a specific warning by ID. Useful for wrongly issued warnings or appeals.
Removes the warning about "Harassment" and decrements counter.
/warnings clear <user>
Clear ALL warnings for a user. Use rarely - only for major appeals or when restarting a user's record.
All 3 warnings removed. User gets fresh start. Consider DM-ing them why as context.
/warnings export <user>
Export user's warning history as CSV/PDF. Useful for appeals review, documentation, or sharing with moderation team.
User Notifications
What Users See When Warned
When you issue a warning, the user receives a DM containing:
- ✓ Why they were warned (your reason)
- ✓ Their current warning count (e.g., "You now have 2 warnings")
- ✓ What happens at next threshold (e.g., "At 3 warnings, you'll be muted for 1 hour")
- ✓ Total warnings before automatic ban
- ✓ How to appeal (if appeals system configured)
When Thresholds Trigger
User also receives a separate notification when automatic action is taken:
"You have reached 3 warnings and have been automatically muted for 1 hour. This is an automatic consequence of our rules. You will be unmuted on [time]. Please review the server rules."
Integration with Appeals System
Warnings can be appealed. If your appeals system is enabled:
- • Appeal Code:Users receive an appeal code in DM. They use this to submit appeals.
- • Review Process:Appeals go to designated review channel. Leadership can remove warnings if user makes good case.
- • Documentation:Appeals and decisions are logged. Helps avoid repeated bad decisions and provides transparency.
Best Practices for Warning System
1. Be Consistent with Thresholds
Set thresholds once and stick to them. Don't randomly escalate or forgive. Users learn the system and expectations.
2. Always Provide Clear Reasons
Vague reasons ("Rule break") confuse users. Specific reasons ("Spam in #general with 10+ messages in 5 seconds") help them understand and improve.
3. Use Warnings Proportionally
Minor violations: Warn. Serious violations: Timeout/Mute directly. Warnings work best for pattern enforcement, not one-off severe issues.
4. Monitor Warning Activity
Review which users accumulate warnings. Look for patterns. Is one user always warned? Are you warning too much? Too little?
Important Notes
- • Warnings are per-user, per-server (not global across Discord)
- • Automatic actions execute immediately when threshold reached
- • You can't prevent a threshold action from triggering without modifying thresholds
- • Decay happens automatically in background - users don't see exact timing
- • Manual removal (via /warnings remove) doesn't trigger appeals system