channels & voice.
creating, locking, slowing, and moving people around.
creating and editing text channels
the channel family handles structural changes and requires manage channels. commands that accept a channel can be run elsewhere, which is useful when the target is locked or quiet. cloning copies the source channel’s settings and optionally gives the copy a new name; deleting removes the selected channel.
| command | what it does | needs |
|---|---|---|
| /channel create <name> | create a text channel with the supplied name | manage channels |
| /channel clone <channel> [name] | clone a text channel, keeping its name unless a replacement is supplied | manage channels |
| /channel delete <channel> | permanently delete the selected channel | manage channels |
| /channel rename <channel> <name> | change a channel name | manage channels |
| /channel topic <channel> [text] | set its topic, or clear it when text is omitted | manage channels |
| /channel position <channel> <position> | move it to a numeric position in the server channel list | manage channels |
| /channel slowmode <channel> <duration|0> | set slowmode up to six hours, or use 0 to disable it | manage channels |
,channel create incident-room
,channel clone #announcements announcements-archive
,channel topic #rules read before posting
,channel slowmode #general 15s
/channel rename channel: #general name: lobbychannel delete removes the channel and its messages from discord. clone first when the goal is to preserve permissions and settings in a fresh channel, and confirm the mention before deleting.
how permission overwrites are changed
visibility, lockdown, and file restrictions edit channel-specific permission overwrites. discord resolves those overwrites together with server roles, member overrides, and administrator access; changing one deny does not rewrite every role. havoc saves the prior values for the exact target so its matching restore command can put them back.
- ::hide <channel> <role or member>
- sets view channel to deny for that target and saves the old value.
- ::unhide <channel> <role or member>
- restores the value saved by havoc for the same channel and target.
- ::revokefiles on <channel>
- denies attach files and embed links for @everyone, saving their previous values.
- ::revokefiles off <channel>
- restores those saved @everyone file and embed values.
unhide and revokefiles off are not generic allow switches. they restore a state previously saved by havoc. direct permission edits made while a restriction is active can be replaced by the stored values when it is restored.
what a lockdown actually changes
a lockdown denies four permissions for the configured role: send messages, send messages in threads, create public threads, and create private threads. it does not hide the channel, delete messages, disconnect voice users, or rewrite unrelated permissions. by default the target is @everyone.
,lockdown #general raid cleanup
,unlock #general cleanup complete
,lockdown role @Members
,lockdown all verification pause
,unlock all verification complete| command | what it does | needs |
|---|---|---|
| /lockdown [channel] [reason] | lock one channel, defaulting to the current channel | manage channels |
| /unlock [channel] [reason] | restore the saved permission values for one channel | manage channels |
| /lockdown all [reason] | lock every text channel except configured ignores | manage channels |
| /unlock all [reason] | restore saved lockdown state across text channels | manage channels |
| /lockdown role <role> | choose the role future lockdowns restrict | manage guild |
| /lockdown ignore [channel] | show the ignore list | manage guild |
| /lockdown ignore add [channel] | exclude a channel from future lockdown all runs | manage guild |
| /lockdown ignore remove [channel] | remove a channel from that exclusion list | manage guild |
| /lockdown ignore list [channel] | show the configured exclusions | manage guild |
lock is the alias for lockdown. changing lockdown role affects future locks only; existing locks remember the role and values they must restore.
planning a server-wide lock
- 01
choose the restricted role
leave the default at
@everyone, or set a member role withlockdown role. - 02
exclude operational channels
add staff coordination, verification, or status channels with
lockdown ignore add. - 03
inspect the list
run
lockdown ignore listbefore the incident, not during it. - 04
lock and later restore
run
lockdown allwith a reason, thenunlock allwhen normal posting should return.
the moderator needs manage channels in each affected channel, and havoc needs enough access to edit its overwrites. a server-wide run reports completed and failed channel counts; investigate failures rather than assuming every channel locked.
slowmode, topics, and files
standalone commands cover frequent current-channel work and still require manage channels. plain slowmode reports the current channel’s delay, while plain revokefiles reports the current @everyone file overwrite. topic always targets the current channel.
| command | what it does | needs |
|---|---|---|
| /slowmode | show the current channel’s slowmode delay | manage channels |
| /slowmode on <channel> <delay> | enable a delay up to six hours | manage channels |
| /slowmode off <channel> | set the channel delay to zero | manage channels |
| /topic <text> | replace the current channel topic | manage channels |
| /revokefiles | show the current channel’s @everyone file permission state | manage channels |
| /revokefiles on <channel> | deny attachments and embedded links for @everyone | manage channels |
| /revokefiles off <channel> | restore the saved attachment and embed values | manage channels |
,slowmode
,slowmode on #support 30s
,slowmode off #support
,topic weekly planning and decisions
,revokefiles on #generalmoving and moderating voice members
voice actions require the matching discord permission in the member’s current voice channel. movement also needs havoc to connect to the destination, and every selected member must already be connected. target role hierarchy still applies to member actions.
| command | what it does | needs |
|---|---|---|
| /voice move <member> <channel> | move one connected member to a voice or stage channel | move members |
| /drag <members...> <channel> | move several named members to one destination | move members |
| /moveall <channel> | move members from every other voice and stage channel to the destination | administrator |
| /voice mute <member> | server-mute a connected member | mute members |
| /voice unmute <member> | remove that server mute | mute members |
| /voice deafen <member> | server-deafen a connected member | deafen members |
| /voice undeafen <member> | remove that server deafen | deafen members |
| /voice disconnect <member> | disconnect a member from voice | move members |
,voice move @member "Support Room"
,drag @one @two "Town Hall"
,voice mute @member
,voice undeafen @member
,voice disconnect @member
/voice deafen member: @memberhavoc accepts a voice channel name or id. if two channels share a name, the command stops rather than guessing; pass the destination channel id. mass actions validate all selected targets before movement starts, then report succeeded and failed counts.
common operating patterns
a fast incident pause
prepare ignores, lock all channels, keep a private staff room open, and restore with unlock all after the incident.
a noisy support room
apply slowmode instead of lockdown when members should still answer, just less frequently.
attachment abuse
use revokefiles to deny attachments and embeds without blocking ordinary text, then restore the saved overwrite.
voice event staging
use drag for an explicit group. reserve administrator-only moveall for moving everyone across the server.