A nuke spread over several minutes is now stopped, even when it comes from a bot on your whitelist. And a big loss no longer wipes your backup.
A server got destroyed by a bot it had put on its whitelist. The bot deleted channels slowly, two or three every thirty seconds, and Protector let it happen. We closed the three holes that made it possible.
01Slow nukes
The anti-nuke now also looks at the last 10 minutes. Deleting channels one by one, taking your time, no longer stays under the threshold.
The threshold follows your server level: at the balanced level, about a dozen channels deleted in 10 minutes is enough to stop the author.
02Whitelist
The whitelist still covers the everyday work of your bots and trusted members. It no longer covers destroying the server: a large part of the channels or roles deleted, or Administrator given to everyone, and the author is stopped anyway.
In that case there is no global blacklist: you trusted them, you decide what happens next.
03Backup
When a big part of the server disappears at once, the anti-nuke backup keeps the previous state instead of following the loss after 30 minutes. The previous state is also stored in /restore.
Did you reorganize the server yourself? The owner gets a message with a button to confirm the new state.