Lock and restore a channel
.lock [#channel] [reason] (aliases .lk, .l) and /lock block the current or selected text channel. .unlock [#channel] [reason] (aliases .ulk, .u) and /unlock restore access. When a prefix command runs inside a thread, the callback operates on its parent text channel.
The actor and Headless need Manage Roles; Fake Permissions may satisfy the compatible actor check, but the bot needs its native permission and must be able to edit the channel’s overwrites. The first .lock stores the original @everyone overwrite per server. It denies sending messages, adding reactions, and creating public or private threads. Repeated locks do not replace the saved snapshot. Each lock and unlock creates its own case and log event.
If a snapshot exists, .unlock restores the saved @everyone overwrite exactly. Without one, it removes explicit lock values so Discord can recalculate inherited access. It does not restore overwrites for other roles; an inherited category lock can still deny access after unlock.
.lock
.unlock
.lock
.unlock
Slowmode
.slowmode [#channel] <duration> [reason] (aliases .slow, .sm) changes the interval in the current or selected channel. Prefix accepts seconds or s, m, and h suffixes, plus off or 0 to disable it. The maximum is 21,600 seconds (six hours). /slowmode accepts the channel, seconds as an integer from 0 to 21,600, and a reason; slash does not accept unit suffixes.
The actor needs Manage Channels (native or a compatible Fake Permission), and Headless needs its own native Manage Channels permission. Each change records the old and new values in a case and log. Slowmode only limits message frequency; it does not delete messages or lock the channel.
.slowmode
.slowmode #general 10m flood · .slowmode #general off
.slowmode
10m in prefix equals seconds: 600 in slash. .lockdown and .endlockdown are prefix-only.
Lockdown across multiple channels
.lockdown [reason] (alias .ld) and .endlockdown (aliases .eld, .elock) are prefix-only; there is no slash equivalent. Lockdown iterates available categories, text channels, voice channels, Stage channels, and forums. The actor needs Administrator (native or a compatible Fake Permission); Headless needs native Manage Channels.
Dashboard → Lockdown can configure up to 80 allowed roles. Before changing a destination, Headless persists its previous @everyone overwrite and the overwrites for those allowed roles. It then denies @everyone sending messages, adding reactions, creating threads, connecting, speaking, and streaming; allowed roles receive explicit participation overwrites. A failure on one destination does not stop the rest, and the case/log record successful and failed targets. Configuration and snapshots are server-scoped. Starting another lockdown while one is active or still has snapshots pending is refused so the original permission baseline cannot be overwritten.
.endlockdown attempts to restore @everyone and allowed roles that still exist. Other role overwrites are neither saved nor restored. If Discord rejects a restoration, Headless keeps the original snapshots only for the failed destinations, leaves lockdown active, and reports that recovery is pending. Resolve the permission or role-hierarchy issue, then run .endlockdown again; snapshots are cleared only after all remaining destinations are restored. Deleted destinations are skipped because there is no channel left to update.
.lockdown
.endlockdown
Recreate the current channel (nuke)
.nuke [reason] (aliases .nk, .recreatechannel, .reiniciarcanal) or /nuke [reason] recreates only the text channel where it is invoked. It does not accept a target channel. The command presents a confirmation and requires Manage Channels and Anti-Nuke Admin access; the server owner and Headless owner also pass that check. Administrator alone does not grant Anti-Nuke Admin access. Headless needs Manage Channels, View Channel, and Send Messages; the prefix command also requires the bot’s Manage Messages. The account confirming must be the same one that started the action and must still pass the Anti-Nuke access check. The current callback does not set a confirmation expiry.
Headless clones the channel, attempts to preserve its position, and then deletes the original. The ID changes and message history is not copied. The case retains the old reference and the log points to the new channel. Automatic clone cleanup is attempted only if something fails before the original is deleted; after deletion, there is no automatic rollback.
If you omit the reason, the command records the default text Channel recreated.
.nuke
.nuke
Steps
1
Identify the scope
Test lock and slowmode in a staging channel. Before lockdown, review categories, channels, and configured allowed roles.
2
Apply the smallest change
Choose the channel, duration, and reason. Do not lock a category without checking channels that inherit its permissions.
3
Verify the result
Confirm effective access in Discord and review the case and log event, including partial failures.
4
Restore and check
After a temporary measure, run
.unlock or .endlockdown as appropriate and manually review channels Discord could not restore.