Nuke protection
Stop a rogue or compromised moderator who starts banning, kicking or stripping roles in bulk.
What it watches
The Moderation action spam (Nuke) trigger counts moderation actions per person. It can watch bans, unbans, kicks, timeouts, role additions and role removals, and watches bans, kicks and timeouts if you pick none. Nighthawk reads the server audit log, so actions taken straight from Fluxer count as well as actions taken with Nighthawk, and an action seen both ways is counted once.
Set the limit
Set how many watched actions one person may take within how many seconds. The defaults are 5 within 30 seconds. Past that, the rule fires and its actions run against the moderator, not the members they acted on. Useful choices are removing their staff role, muting, kicking, or alerting the rest of your team.
Who is covered
Nighthawk itself and the server owner are never actioned. Everyone else is counted, staff included, because a phished staff account is the case this exists for. Bulk commands count too: n!massban of 30 members is 30 bans. Use the Roles or Permission groups condition to exempt people you trust, such as the lead moderator who runs cleanups, or raise the limit.
Start with an alert
Treat a new nuke rule like any other automod rule. Run it with Send an alert and Log for a week, read what it catches, and only then add a punishment.