Pantheon Mode — Emergency Lockdown

An extra layer that runs on top of regular anti-nuke — activates automatically once an attack is confirmed, temporarily freezing dangerous permissions across every role to prevent a repeat attempt during recovery.

When does it activate?#

• Automatically, the moment the bot begins restoring channels/roles after punishing a confirmed attacker — no manual setup or toggle needed.
• Doesn't activate on suspicious activity or warnings — only once an actual confirmed attack crosses the protection threshold.

What exactly does it do?#

• Strips only dangerous permissions (Administrator, Manage Roles/Channels, Ban, Kick, and similar) from every role the bot can manage — the rest of a role's permissions keep working normally.
• Runs alongside the restore process, not instead of it — the restore proceeds on its usual timing whether Pantheon activates or not.

Two levels based on severity#

Pantheon doesn't treat every attack the same way — the response scales with whether it's an isolated event or a repeating pattern:

• Isolated attack: permissions return automatically a few minutes after the restore completes — no action needed from you.
• Repeated or coordinated attack (more than one attempt or account within a relatively short window): permissions stay frozen until you confirm manually — stronger protection because a repeat signals a higher chance the attack is still ongoing.

How to confirm manually (when needed)#

• The bot DMs you the moment strict mode activates — any reply to that message restores permissions immediately.
• If your DMs are closed, use !pantheon confirm inside the server (owner-only) — an alternative that always works.
• You'll also find a full alert in the Security Logs channel in every case, including if the DM fails to arrive.

It doesn't stop at punishing the attacker#

If the attacker held a dangerous role, Pantheon also checks who granted it to them — and if that person isn't the server owner or a trusted account, they're punished too. The details of that check are intentionally not documented here.

More accurate restores#

• The post-attack restore now cross-references the last full automatic backup to place channels back in their correct order, not just recreate them in any order.
• Anything that failed to restore on the first attempt is retried automatically — no manual intervention needed in the vast majority of cases.