What this is for
If a moderator account gets compromised or a bot goes rogue mid-raid, killswitch strips the permissions being abused from every role at once. It buys you time to work out who’s responsible without hunting through role settings while damage is still happening.
This is a last-resort tool. It touches every role in your server, and members lose access to things until you restore. Try ,killswitch preview first to see what it would hit.
Limited to the server owner and antinuke admins.
Put misery’s role above every other role in the server so it can reach all of them.
Pulling the switch
misery shows you how many roles will be affected and asks you to confirm. Once you do, it works through them at a paced rate — expect it to take up to a minute on a large server.
There’s a cooldown between uses. If you’ve just run it, misery tells you how long to wait.
Bots only
When the problem is clearly a bot rather than a member, this leaves your staff roles alone:
Seeing what it would do
Lists every role carrying a dangerous permission. Nothing is changed.
Worth running once while things are calm, so you know what the real thing would do before you ever need it.
Finding who caused it
Groups recent destructive audit log entries by who performed them — bans, kicks, channel and role deletions — sorted by volume. This is usually how you identify the compromised account.
Undoing it
Once the incident is handled:
misery puts every role back to the permissions it held before the killswitch ran, using the snapshot it saved at the time.
Server owner only — antinuke admins can trigger a killswitch but can’t restore from one.
Lockdown
For a full emergency stop, lockdown punishes every non-owner action — even from whitelisted users, whitelisted bots, and antinuke admins — and reverts what it can until you turn it off.
Choose what happens to anyone who acts during a lockdown:
,killswitch status shows whether a lockdown is active.
Turning lockdown on and off is server owner only.
