Lockdown
Lock down channels or your entire server instantly when a raid or attack starts.
Lockdown lets you restrict channels and roles in seconds. When a raid hits, you don't have time to manually edit permissions channel-by-channel — lockdown does it all at once with a single command, then reverts everything cleanly once the threat is over.
Commands
How lockdown works
When you trigger a lockdown, AntiRaid saves the current permissions for the affected channels or roles, then overwrites them to deny sending messages (and other configurable permissions) for your member roles. When you remove the lockdown, AntiRaid restores the saved permissions — so nothing is permanently changed.
Member roles
On first setup, AntiRaid will ask you to define your member roles — the roles that represent regular server members. These are the roles that get locked down. Admin and moderator roles are not affected, so your staff can still communicate during an incident.
Lockdown types
| Type | Command | Best used when |
|---|---|---|
| Quick server lockdown | /lockdowns quick | Raid is actively happening — lock everything immediately |
| Channel lockdown | /lockdowns channel | Trouble is isolated to one channel |
| Role lockdown | /lockdowns role | A specific role is being abused |
Permissions required
lockdown.*— grants access to all lockdown commands
Migrating from Wick
If you're coming from Wick or a similar bot, here's how AntiRaid's lockdown types map across:
| AntiRaid | Wick equivalent |
|---|---|
Quick server lockdown (qsl) | Channels lockdown (sc) |
Channel lockdown (scl) | Channel lockdown (c) |
Traditional server lockdown (tsl) | No direct equivalent |
Features like Join Auto Kick and Join Auto Ban are not part of the lockdown system — they are handled separately through AntiRaid's inspector and auto-response modules.