Automatic punishments
Applying a consistent penalty once a member reaches a set number of cases.
Escalation rules apply a penalty automatically once a member reaches a set number of cases, for example three warnings resulting in a timeout.
This keeps repeat offences handled consistently without a moderator needing to check a member's history.
Building a rule
A rule has three parts:
- What is counted. Warnings, timeouts or kicks.
- How many. The number that triggers the rule.
- What happens. A timeout with a length, a kick, or a ban.
What cannot be used
Reversals cannot be counted. Counting an unban would penalise a member for having a sanction lifted.
A warning cannot be the result. A rule that issues a warning in response to warnings either does nothing or repeats indefinitely.
How far back cases count
One setting applies to the whole server: cases older than a set number of days stop counting.
The default is 0, which counts every case. Adding a first rule therefore does not silently change how far back existing cases reach.
The window is rolling rather than a monthly reset. A monthly reset would allow offences late in a month to expire days later.
How rules apply
Each rule applies once. With a rule set at three warnings, a fourth warning does not repeat the penalty.
Rules chain. A timeout applied by a rule is itself a case, so it counts toward a timeout rule. This is what allows a sequence such as warnings leading to timeouts leading to a ban.
Setting it up
Open Moderation > Escalation on the Dashboard to add rules and set how far back cases count.