Skip to main content
Raid mode temporarily tightens the server’s protection during an incident. Start it manually or enable automatic activation when joins exceed a chosen threshold. Manual activation is attributed to the logged-in moderator; join-burst activation is recorded as automatic. pup saves the previous join settings and Discord settings before changing join admission, verification, messaging, invites, roles and notifications. When raid mode ends, it restores only values that still match its changes. Newer manual changes are kept. The configured response can pause automatic role changes and member notices while staff alerts continue. Moderators can still edit member roles. Open Protection overview → Raid mode to configure, activate or end it. These actions require server configuration access and remain subject to Discord’s limits.

​
Configure and start a raid response

Review Saved raid response before activation. Activation settings controls manual-only or automatic join-burst activation, burst threshold/window and duration. Response settings controls Discord verification, channel slowmode, new invites, pup’s automatic anti-nuke roles and join-guard notifications. Activation uses the saved configuration; unsaved edits do not block it. Raid mode raises Discord verification to at least High, applies at least 10 seconds of slowmode when selected, and denies new invites for @everyone in server channels. Existing invites and role-specific overrides are not revoked. Both staff-alert choices suppress member-facing join-guard notices; neither creates a new audit channel. A legacy review-only messaging setting also applies slowmode; it does not hold messages for approval. Select Activate raid mode. Manual incidents use High severity. Activation in progress means Discord has not finished applying the response; Raid mode active confirms that Discord confirmed the changes. Refresh status loads the current state without discarding configuration drafts.

​
End and recover

End raid and restore settings starts recovery; the incident also restores settings when its duration ends. Restoration in progress remains visible until recovery completes, including after the scheduled end time. Settings cannot be edited in this dashboard while the incident is open. Recovery uses the join and Discord settings saved before the incident, even if the saved raid policy changed later. If no join policy existed before the incident, recovery removes the temporary policy. If activation only partly succeeds, those changes can still be restored. Each channel is compared independently; later manual changes are preserved, and a retry does not reapply a completed restoration. Only Restoration complete confirms the recovery operation finished.