Moderator Accountability
Detect a staff member performing too many destructive actions in a short window, then freeze or alert before the damage spreads.
Anti-nuke catches admins acting through the audit log, but a moderator abusing normal bot commands (mass-banning, mass-kicking, mass-stripping roles) slips past it. This guard counts each staffer's destructive actions over a short window and, if one spikes, freezes them and alerts the owners. It is off by default.
Commands
,modguard (aliases ,modaccountability, ,modwatch) needs Administrator:
,modguard enable turn the guard on
,modguard disable turn it off
,modguard threshold 5 actions that trip the guard
,modguard window 60 window in seconds they're counted in (min 5)
,modguard action freeze response: alert, freeze, or strip_roles
,modguard freezetime 600 how long a frozen mod is timed out (min 60)
,modguard channel #mod-log where alerts go (or none for the mod log)
,modguard exempt add @role let a role bypass the guard
,modguard triggers show recent triggers
,modguard status show the current config
Example
Freeze any mod who takes more than 5 destructive actions in a minute, and exempt senior staff:
,modguard enable
,modguard threshold 5
,modguard window 60
,modguard action freeze
,modguard exempt add @Head Mod
Tip: Set your threshold above normal activity so the guard only fires on a genuine spike. The owner and your anti-nuke admins are never frozen. The dashboard's Moderator Accountability page shows recent triggers.
Related
- Anti-Nuke covers destructive actions taken through the audit log (admins); this covers destructive bot-command use (mods).
- The case system records the very actions this guard counts.