How to prepare a Discord server for a nuke, and recover from one

01

Before you start

Only the server owner can switch Anti-nuke on or off, and only the owner can confirm a restore. People with Administrator can change the limits, the response and who is exempt. Kirzen never asks for Administrator itself, so the permissions it needs are listed on one page.

Read what Kirzen asks for

02

Part 1: get ready

• 1. Turn Anti-nuke on Only the owner can do this, and it starts off. Until then, nothing is being watched.
  /antinuke toggle enabled: true
• 2. Let Kirzen read the audit log Give the Kirzen role View Audit Log. Without it Kirzen cannot tell who did what, and the protection has almost nothing to go on.
• 3. Choose where alerts go Without an alert channel Kirzen acts quietly.
  /antinuke alerts
• 4. Choose what happens to someone who passes a limit The choices are to only alert, strip their roles, kick or ban. Stripping is the default: it removes their power and keeps them in the server.
  /antinuke punishment
• 5. Set the limits and the window Each limit runs from 1 to 100 actions, and the window from 5 to 300 seconds. The default window is 15 seconds. Raise a limit if a legitimate rebuild would trip it.
  /antinuke limit /antinuke window
• 6. Exempt people you trust The server owner is exempt by default and bots are not. Add the people or roles you trust, and remove them when that changes.
  /antinuke trust /antinuke untrust
• 7. Record the server A restore works from this record. While Anti-nuke is on, Kirzen refreshes it by itself every few hours.
  /denuke snapshot
• 8. Optional: save a template before a big change A template keeps the roles and channels as they are now, so you can put back what goes missing.
  /template save

Then look at what is configured and what has been caught, what the record holds and what is missing, and how well defended the server is.

03

Part 2: if an attack gets through

• 1. Close the server If someone is still acting, close the server first. One command closes it and another opens it again.
  /panic on
• 2. See what is missing It compares the server with the last record.
  /denuke status
• 3. Preview the restore Without confirm, nothing changes. You see how many roles and channels would be recreated.
  /denuke restore
• 4. Confirm the restore Only the server owner can confirm it.
  /denuke restore confirm: true
• 5. Lift a ban wave It looks back 30 minutes by default, from 1 minute to 24 hours, and can be limited to bans placed by one person. It shows a preview first, and only the owner can confirm.
  /denuke unban
• 6. Open the server again When everything is back, open the server.
  /panic off

04

What a restore does not do

• It does not bring messages back. Recreated channels are new and empty. Discord gives no way to bring messages back.
• It does not give the roles back to people. Recreated roles are new too, so nobody holds them and they carry no permissions until you grant them.
• It is not from today. A restore works from the last record, so anything created after it is not in it. Check when it was recorded with the status option.

05

Common mistakes

• Forgetting View Audit Log. The command warns you, but until you grant it the protection has almost nothing to go on.
• Limits too low for a legitimate rebuild. A big reorganisation can pass a limit. Raise it for the day, or exempt the person who is doing it.
• Trusting an old record. Look at when the server was recorded before you restore from it.