purging & cleanup.

every purge command requires manage messages. havoc reads a bounded slice of channel history, applies the chosen filter, and deletes matches. the default search is 100 messages for filtered variants and the maximum is 2,000. a search limit is how many messages havoc examines, not a promise that it will delete that many.

,purge 25
,purge @member 200
,purge links 500
,purge contains "spoiler text"
/purge bots search: 100

the plain command treats a number as a count of recent messages. a member followed by an optional search limit removes only that member’s matching messages. clear is the registered alias for purge; the named filters keep their purge paths.

emoji and emotes are separate because unicode symbols and custom discord markup are different data. images is narrower than files, while embeds can also match rich previews that are not uploaded files.

use member cleanup when one account caused the problem; it avoids removing the surrounding conversation. content filters are case-sensitive exact substring checks, so copy the relevant text exactly. startswith is useful for repeated command output, while endswith can target a repeated footer. all three text variants use the standard 100-message search window.

,purge @spammer 300
,purge startswith "limited offer"
,purge endswith "click here"
,purge mentions @moderator 500

range commands are safer than a broad count when staff can identify a boundary. before, after, and upto accept a discord message link and can operate in the channel named by that link. havoc verifies that the moderator and bot have view channel, read message history, and manage messages there.

,purge before https://discord.com/channels/123/456/789
,purge after https://discord.com/channels/123/456/789
,purge between 111111111111111111 222222222222222222
,purge upto https://discord.com/channels/123/456/789

discord’s bulk-delete endpoint does not accept messages older than fourteen days. havoc accounts for this: recent matches are deleted in batches of up to 100, while older matches are flushed and deleted one at a time. old cleanup is therefore slower and can produce individual failures, but it is not silently skipped.

a purge creates a havoc case and discord emits a bulk message-delete event. if message_delete is routed, the log records the bulk deletion count and channel. it does not duplicate every deleted message’s body into the log. member-targeted and mention purges also create a victim-targeted case with the channel and deleted count.

configure the destination before cleanup begins; logging is not retroactive. the logging guide explains routes, ignores, and a private message-log layout.

havoc caches recent non-bot deleted messages, edits, and removed reactions per channel for one hour. the commands show the newest entry by default; pass an index to inspect an older cached entry. the viewer needs access to view the channel and read its message history.

,snipe
,snipe 2
,editsnipe
,reactionsnipe 3