Anti-Raid & Anti-Nuke

Anti-Raid watches join velocity and account signals for a wave of joins. Anti-Nuke, configured on the same dashboard page, instead watches for one actor already inside the server performing rapid, destructive actions — mass channel or role deletion, permission changes, mass bans, or webhook abuse. Both apply the same configured response when a threshold is crossed.

• Confirm the server has active premium access.
• Review normal join volume and admin activity before setting thresholds.
• Ensure Airwavy has the permissions required by the selected response and sits above affected member roles.

1. Open Anti-Raid in the dashboard.
2. Set join thresholds, the observation window, account checks, and the response action for Anti-Raid.
3. Scroll to the mass-destructive-action section to enable and threshold the Anti-Nuke categories you want covered.
4. Choose notification or log destinations, save, and monitor the first alerts closely.

• Set a join threshold from 2 through 100 members within a 1- through 300-second observation window.
• Optional signals include young accounts, default avatars, bot accounts, and clusters of similar usernames.
• Choose quarantine, kick, ban, or alert-only handling, and exclude trusted roles or members where the dashboard allows it.
• Optional Discord lockdown can temporarily restrict joins for 5 minutes through 24 hours.
• Anti-Nuke reuses this same response setting for a triggered destructive-action category — there is no separate response choice per category.

• Mass channel deletion, mass role deletion, mass role permission changes, mass bans, and webhook abuse are each independently toggleable with their own threshold.
• Only exempted roles or accounts bypass detection — every other actor, including admins and bot integrations, is covered.

Adding exemption roles or disabling Anti-Nuke protection is restricted to the server owner, since either change can widen the surface a compromised account could exploit.

• Send alerts to a private destination and choose the staff roles permitted to act on them.
• Guarded alert actions let authorized staff resolve the incident, prune the detected members, or keep protection active.
• Rollback support restores the relevant protection state after staff resolve an incident.
• Review every automated action against Discord's Audit Log and your own incident policy.

• Normal joins and normal admin or integration activity continue without intervention.
• A matching join wave, or a matching burst of destructive actions, triggers the configured protection and a staff-visible alert where configured.