Strike System
The strike system lets you define automatic escalation thresholds for /warn. When a user accumulates enough warnings, Lunova automatically applies a mute or ban — no manual intervention needed.
Setup
/strikes setup mute_threshold: 3 mute_duration: 1h ban_threshold: 5| Parameter | Required | Description |
|---|---|---|
| mute_threshold | required | Number of warnings before an automatic mute is applied. |
| mute_duration | required | How long the auto-mute lasts. Accepts 30m, 1h, 6h, 12h, 1d, 3d, 7d. |
| ban_threshold | required | Number of warnings before an automatic ban is applied. Must be higher than mute_threshold. |
Checking Status
/strikes statusShows the current strike configuration: whether it's enabled, both thresholds, and the mute duration.
Disabling
/strikes disableTurns off automatic escalation. Existing warnings remain on user records, but no further auto-mutes or auto-bans will trigger.
How it works
When /warn is used:
- Lunova counts all
warntype cases for that user in the server. - If the new count equals mute_threshold, a timeout is applied immediately for the configured duration.
- If the new count equals ban_threshold, a ban is applied immediately.
- Both escalations create their own auto-case (type
muteorban) with an automatic reason.
ℹ Only
/warn triggers strike checks — other actions (ban, kick, mute) do not count toward the strike total. The count is cumulative across all time; there is no decay or expiry.Example
With mute_threshold: 3, mute_duration: 1h, ban_threshold: 5:
| Warning # | Result |
|---|---|
| 1, 2 | Warning logged, no escalation |
| 3 | Warning logged + auto-mute for 1h |
| 4 | Warning logged, no escalation |
| 5 | Warning logged + auto-ban |