SkullBot
Moderation
Warning escalation: automatic punishments after N warnings
Short answer
In the Moderation tab turn on Warning escalation and add rules, for example 3 warnings mean a one-hour mute and 5 mean a ban. Each rule fires once, exactly at its threshold.
Step by step
- Open the moduleIn the dashboard go to Moderation and pick Warning escalation.
- Turn it onThe switch inserts default rules: 3 warnings mean a 60 minute mute, 5 mean a ban.
- Adjust the rulesChange thresholds, actions and times or add more rules (up to 10).
- SaveClick Save changes. From now on every /warn create checks the thresholds.
How rules work
- A rule has a threshold (1 to 50), an action (mute, kick, ban) and, for mute and ban, a time in minutes.
- A rule fires only at exactly that warning. With threshold 3 the punishment happens at the third warning, not the fourth or fifth.
- A mute lasts from 1 minute to 28 days. A ban with a time lifts itself (up to a year), a ban with time 0 is permanent.
- An invalid threshold (0 or above 50) is rejected, not corrected, so a typo cannot ban at the first warning.
What the moderator sees
The result shows in the /warn create reply as an "Escalation" field. When the punishment cannot be applied (the user left, the bot role is too low) the embed says why. Every applied punishment goes to the /cases history with the moderator "SkullBot".
Related commands
- Warning systemIssue warns with codes, lists and escalation.
- Moderation casesA user's history of warnings, mutes, kicks and bans.
Frequently asked questions
Does the punishment fire at every later warning?
No. Each rule fires once, at its threshold. For punishments at the 3rd and 6th warning add two rules.
What happens when I remove a warning?
The warning count drops and earlier punishments stay in the history. The threshold fires again when the count reaches the rule value again.
How do I see who the bot punished by itself?
With /cases user. Escalation punishments have the moderator "SkullBot" and a reason with the warning count.