What it does
- Tune the evidence
- Join and text rules have configurable counts and windows. Coordinated media and link checks require repeated bursts from each participating account and at least two accounts. One image, ordinary link or isolated AutoMod block is not enough for those coordinated rules.
- Limit resource floods
- Ticket and Join to Create checks default to six distinct accounts in three seconds in configured AntiRaid setups. Raid mode blocks new flanker tickets and rooms and can remove recent resources attributable to flagged raiders. Established voice rooms are retained.
- Verify and restore access
- Suspicious members can be held behind a captcha with a verification-channel fallback when DMs are closed. Successful verification clears stale raid evidence. Failed permission restores remain pending rather than being reported as successful admission.
- Give staff a readable record
- Raid alerts go to the dedicated antiraid log and the configured alert destination, without duplicate posts to the same channel. Reports separate actual mitigation time from how long raid mode remains on.
Get started
Type the slash command in Discord and fill in its fields, or mention flanker before it. Commands still require their usual permissions.
- Use an account with real Manage Server permission or the required security authority.
- Run guided setup and choose limits that fit your community.
/antiraid setup wizard - Choose a channel for raid alerts.
/antiraid log #antiraid-log - Check the resulting settings before enabling new checks or changing thresholds.
/antiraid config
Common questions
Does ending raid mode automatically admit everyone?
No. Ending raid mode restores the server's lockdown permissions, while members still held for captcha verification remain held until admitted. Fresh spam can trigger protection again after verification.
Can flanker detect every other ticket bot's button click?
No. Other applications' interaction clicks are private. External ticket detection uses configured panel, bot and category information together with attributable channel creation. Ambiguous openers are skipped, and external thread tickets are not covered.
Can staff still use the server during lockdown?
Configured staff, the owner and the backup owner keep their access. Flanker Admin retains channel visibility, but that role alone does not grant permission to change antiraid settings or end a raid.