Anti-Raid
Use premium anti-raid controls to detect join waves and protect the server.
How it works
Premium Anti-Raid watches join velocity and account signals, then applies the configured response when a raid threshold is crossed.
Before you start
- Confirm the server has active premium access.
- Review normal join volume before setting thresholds.
- Ensure Airwavy has the permissions required by the selected response and sits above affected member roles.
Configure it
- Open Anti-Raid in the dashboard.
- Set join thresholds, the observation window, account checks, and the response action.
- Choose notification or log destinations, save, and monitor the first alerts closely.
Signals and response
- 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.
Staff incident workflow
- 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.
Expected result
- Normal joins continue without intervention.
- A matching join wave triggers the configured protection and a staff-visible alert where configured.
Common errors
Normal members are being caught
Raise the join threshold, shorten or adjust the observation window, and review account-age rules. Start conservatively for servers with bursty invite campaigns.
Saved changes do not take effect
Reload the feature page and confirm the saved values. Then verify that the selected Discord channel or role still exists and that Airwavy can access it.
Discord reports missing permissions
Check the permission on both the server role and the target channel. Channel overwrites and role hierarchy can deny an action even when the server-level permission is present.