Guide/Protect your server/Moderation commands & cases

Discord Moderation Bot Commands: Ban, Kick, Timeout

Every moderation command with its Discord permission, plus the per-moderator caps that stop a rogue or stolen staff account.

Quick answer

Day to day

!mute @user 10m spamming
!warn @user please read #rules
!clear 50 @user
!ban @user raid account 1
!case user @user

Ask the guide

Step by step

Command	What it does	Discord permission
`!ban @user [reason] [delete_days]`	Ban; delete_days removes their recent messages (0–7)	Ban Members
`!softban @user [reason]`	Ban and immediately unban to purge messages	Ban Members
`!unban <user id> [reason]`	Remove a ban (also pardons heat/strikes)	Ban Members
`!kick @user [reason]`	Kick	Kick Members
`!mute @user 10m [reason]`	Timeout (alias !timeout); up to 28 days	Moderate Members
`!unmute @user`	Remove a timeout	Moderate Members
`!warn @user <reason>`	Warning with a case number; warnings count toward strikes	Moderate Members
`!quarantine @user · !unquarantine @user`	See Quarantine	Moderate Members
`!clear 50 [@user] [contains:text] [bots:true]`	Bulk delete up to 1000 recent messages, optionally filtered. Discord only allows 100 per call and nothing older than 14 days, so the bot pages through and stops at the fortnight mark	Manage Messages
`!lock [#channel] [10m] [reason] · !unlock`	Deny sending/connecting for @everyone; staff roles keep access	Manage Channels
`!lockall [10m] [reason] · !unlockall`	Lock the configured lockdown set (or every channel)	Manage Server
`!nuke [#channel] [reason]`	Wipe a channel by re-creating it: identical name, topic, slowmode, category, position and permissions, all messages gone. Asks for confirmation; posts a notice in the new channel; logged as a case. Protected channels are refused	Administrator
`!case view 12 · !case user @x · !case reason 12 new text`	Cases are numbered per server	Moderate Members
`!incident list · !incident view 3 · !incident resolve 3 "false alarm"`	Correlated events (raids, nuke attempts, escalations) with timelines	View Audit Log

Every action, whether taken through the bot or natively in Discord, is recorded as a case with actor, target, reason, duration and evidence links, and appears on the dashboard under Security → Cases. Native actions are attributed from the audit log.

Moderator limits (rogue staff protection)

Every moderator, whitelisted or not, has a cap per rolling window (default 10 minutes): 3 bans, 5 kicks, 10 timeouts, 5 quarantines, 10 purges, 10 role removals. Bot commands and native Discord actions share the counters. When a cap is exceeded the next action is blocked and, depending on the setting, the moderator is quarantined, has their roles removed or is kicked, and staff are alerted. Configure under Security → Protection → Moderator limits (window, each limit, apply to whitelisted, action on exceed).

Copy and try

Day to day

!mute @user 10m spamming
!warn @user please read #rules
!clear 50 @user
!ban @user raid account 1
!case user @user

Wipe a channel

!nuke #general fresh start   # Administrator only; asks for confirmation

Lock a whole category

!lock #Community 30m raid   # a category locks every channel inside it
!unlock #Community

Good to know

Security → Moderate can lock or unlock single channels for N minutes (same as !lock / !unlock in them) next to the server-wide containment buttons; tickets can be claimed, closed and reopened from the Tickets page.
Every action, bot or native, becomes a numbered case.
Moderator limits apply to everyone including whitelisted staff when "apply to whitelisted" is on.

If it does not work

"Target role is above yours". Discord hierarchy: you cannot act on someone whose top role is at or above your own.

Still stuck? Ask in the support server.