Strike Automation

Automatic punishments that fire as a member's record builds up, set from Moderation & Security → Strike Automation on the dashboard. It has its own page now, having previously been the bottom half of the AutoMod page.

The page's Simple and Advanced switch is the choice of ladder. Simple is the plain thresholds, Advanced is the tiered ladder, and there's no longer a separate control for picking between them. Switching back to Simple lists what it will turn off first and stages it on the save bar, so Reset puts the tier ladder back.

What counts as a strike

Switches at the top of the page decide which actions go on the record and move the ladder. A server setting strikes up for the first time counts warnings, mutes and timeouts. A server that has already saved this page keeps whatever it chose, so nothing changes underneath anyone.

Switch	What it does
Warnings count as strikes	Turn it off and a warning is still recorded and still shows in strike history, it just stops moving the ladder. That leaves auto-punishment driven purely by mutes and timeouts
Mutes count as strikes	A mute a moderator issues goes on the record and escalates exactly like a warning
Timeouts count as strikes	The same for timeouts
Your own Discord AutoMod rules count	Advanced only, and off unless you switch it on. A hit on an AutoMod rule you wrote yourself, rather than one Aegis manages, records a strike and moves the same ladder

💡

AutoMod strikes move this ladder too. A filter handing out the strike that reaches your auto-kick or auto-ban number fires it there and then, rather than waiting for a moderator to act. Only the strike that actually crosses a threshold triggers anything, so nobody is punished for a total they were already sitting past. Anti-Scam, Raid Defense and the Honeypot still carry their own punishments and never feed this ladder.

Simple (thresholds)

One running total with a threshold for each action, which is how this has always worked. Each threshold defaults to 0, meaning off, until you set it.

Threshold	Action	Default duration
Auto-Kick at strikes	Kick	None
Auto-Mute at strikes	Mute (role)	1 hour, adjustable
Auto-Timeout at strikes	Native timeout	1 hour, adjustable
Auto-Ban at strikes	Ban	None

If a strike crosses several thresholds at once only one action fires, in a fixed priority of Ban → Kick → Mute → Timeout, no matter which numeric threshold is lower.

⚠️

Simple counts a member's whole history rather than recent strikes, and nothing ages out of it. The count only comes down through /unwarn, which removes the most recent entry, or on the dashboard's Strikes page, where an entry can be deleted on its own and Clear All wipes a member's record in one go. Advanced below is the mode with a reset window.

Advanced (severity tiers)

The same idea split by how bad the offence was. Offences sit in named bands, each band carries its own ladder of punishments and its own reset window, and repeating inside a band promotes the next offence to the band beneath it.

Switching the page to Advanced for the first time seeds three bands rather than handing you an empty screen. Every part of them is editable and a ladder holds up to ten bands.

Band	Clears after	Escalates after	Ladder
Low	30 clean days	3 strikes	DM, then a 10 minute mute, then an hour
Mid	Never	3 strikes	24 hour mute, then 7 days, then a kick
High	Never	Never	Ban

Each band takes three things.

Setting	What it means
Clears after	Days without a new strike in this band before its count resets. `0` never clears. The window is measured from now, so "30 days clean" means thirty days without a new one rather than thirty days from the first
Escalate after	Strikes in this band before the next offence is punished by the band beneath it instead. `0` never escalates
Strike 1, 2, 3…	The ladder. Strike 1 is what a first offence costs, strike 2 the second, and so on. Past the end of the ladder its last rung repeats, so a band still bites after you run out of steps

A promoted offence keeps climbing the band it was promoted into rather than repeating that band's first rung. On the seeded defaults, seven low-severity strikes in a row cost a DM, a 10 minute mute, a 24 hour mute, a 7 day mute, a kick, and a kick from then on. It never promotes twice off a single offence, so a run of low-severity strikes cannot reach a ban on its own.

Each rung can be Nothing (record only), DM them, Mute, Timeout, Kick or Ban. Only a mute or a timeout carries a duration, up to Discord's own 28 day ceiling. Indefinite is not honored here: a rung left on it runs for an hour instead. A rung can also carry its own DM, which wins over the wording set anywhere else, and {tier} and {step} in it name where on the ladder the member has landed.

The offence list

Maps an offence name to a band, so a moderator picking "spam" lands in whichever band you filed spam under. /warn autocompletes its offence field from this list, showing each entry's band number beside it. The list holds up to 100 entries.

⚠️

With no offence picked, Aegis falls back to reading the typed reason as one, and that has to match an offence name exactly, ignoring only upper and lower case. A reason of "spam" matches an offence named "spam", but "spamming in general" does not and falls to band 1 along with everything else unlisted.

💡

Simple and Advanced are a choice, not a replacement. A server happy with the plain thresholds stays on Simple and never has to open the tier builder.