moderation.

every completed punishment creates a numbered case with the target, moderator, action, reason, and duration where one applies. staff with manage messages can inspect a member’s record, open one case, narrow history to an action, correct a reason, or review a moderator’s action counts.

,warn @member repeated insults
,history @member
,history @member warn
,reason 184 repeated insults after staff reminder
/moderation caselog member_or_case_id: 184

a warning records the event and attempts to dm the member; closed dms do not prevent the case. a kick removes the member without blocking a return. the ban family differs in how long the block lasts and whether it removes recent messages.

,ban @member 2h posting scam links
,softban @member 1d cleanup after spam
,tempban @member 7d repeated raids
/moderation unban id: 123456789012345678 reason: appeal accepted

only 0 or a duration at the start of a ban or softban is treated as the message-deletion window. that window is capped at seven days. omit it when the first words belong to the reason.

use the listing commands before broad changes. ban recent shows the latest 50 ban-related cases;hardban list shows persistent hardbans. the bulk commands work in small, cancelable chunks rather than issuing every request at once.

timeout and mute both use discord’s native timeout and accept a duration up to 28 days. their matching removal commands clear it. the shorter mute names change member-specific channel overwrites across every channel instead of stopping all participation.

::imute / iunmute

deny or restore attach files and embed links. ordinary text and reactions remain available unless another permission blocks them.

::rmute / runmute

deny or restore add reactions, external emoji, and external stickers. it does not remove existing reactions or stop ordinary messages.

::saved state

havoc stores the previous overwrite values before applying these restrictions, then restores only fields it set to false. new channels receive the active restriction too.

jail is role isolation, not a timeout. run setupmute first to create the havoc jailed role and havoc-jail channel. jailing saves the member’s non-managed roles, removes them, adds the jail role, and schedules restoration. the jail role can see and write only in the jail channel and cannot connect to voice.

timed bans, timeouts, mutes, and jails are stored with scheduled release data, so a bot restart does not erase their expiry. if a jailed member leaves, the state is retained and jail is applied when they return. roles that were deleted, became managed, or moved above havoc cannot be restored.

successful moderation replies include the action and case id. targets may receive a dm for supported actions, but closed dms are reported as a note and do not cancel the punishment. audit-log reasons include the acting moderator’s id. case history remains available to staff with manage messages, while expiration emits a moderation event for configured logging routes.

servers can replace punishment replies and dm wording through the invoke family. those 76 command paths are documented separately in custom responses; changing wording does not change permissions, case creation, or the underlying action.