loadinggriefloadinggriefloadingWhitelist first, then protect the server against nukes and join raids.
Antinuke watches privileged actions — mass bans, channel deletes, role changes, webhook creation — and reverses them when one account crosses a threshold. Whitelist your admins and bot roles first, then turn it on: the server owner is always exempt.
;antinuke whitelist add @Admin
;antinuke enable
;antinuke enable channels ban 3
;antinuke settings
;antinuke modlog #mod-logs
;antinuke rollback on # restore what was damaged
Before trusting it, run ;antinuke test: it stages a small fake nuke in a hidden sandbox and shows the rollback. Then check ;antinuke settings, point ;antinuke modlog at your log channel, and keep ;antinuke rollback on so damage is restored instead of just reported. If someone is caught by mistake, ;antinuke release gives their roles back.
Antiraid handles the other half: the wave of accounts that arrives before anyone can react. ;antiraid toggle turns it on, ;antiraid list shows the modules, and ;antiraid punishment plus ;antiraid threshold tune them. During a live raid, ;antiraid unlock ends the lockdown early once it is under control.