Skip to main content
Anti-Raid does two independent jobs: it reacts to a flood of joins, and it screens individual accounts as they arrive.
Requires Basic premium. Below that the entire page is replaced by pricing — the settings are not shown at all.
Anti-Raid also needs its switch on the Setup page. If it is off, this page shows an amber banner and every control is disabled until you enable it.

​
Raid detection

When enough members join within your window, Vetox declares a raid.
Account Age is a filter, not a requirement. Only accounts younger than the threshold are counted toward the raid trigger. Older accounts joining at the same time are ignored entirely.Raising it makes Anti-Raid more sensitive, not less.
Only the member who trips the threshold is punished. The earlier joiners in the window are named in your alert but are not kicked, banned or muted.If you need everyone in the wave handled, use Join Guard below.
The number inputs let you go below the minimum of 2, but saving that value fails with a generic error. Keep it at 2 or above.

​
Raid reports

Choose a channel and write a start and end message. Both support variables.
Two limitations here:
  • [ServerName] is offered in the picker but never replaced. It posts as literal text.
  • The end message substitutes nothing at all. Any variable you put in it posts literally. Write it as plain text.
[UsersCount] excludes the member who triggered the raid, so it reads one lower than your threshold.
Clearing the report channel does not take effect. The selector appears to clear, but the old channel is retained and alerts keep going there. The channel visibly reappears after saving.To stop alerts, point them at a channel you can archive rather than trying to clear the field.

​
Join Guard

Join Guard screens every join individually and runs independently of the raid threshold — it acts whether or not a raid is happening. Up to 10 conditions.

​
Rules

Each condition holds up to five rules: Generated-name detection covers names ending in three or more numbers, starting with numbers, an underscore followed by numbers, numbers followed by an underscore, only numbers, and short random letter-number mixes.

​
Matching

Each condition chooses All rules must match or Any rule must match.
“Any” with a broad rule such as default avatar will act on a large share of ordinary new members. Combine rules and prefer “All” unless you are certain.

​
Actions

Up to five per condition: assign a role, kick, ban, timeout for a number of minutes, send a DM, post to a channel, or open a moderation case.
Actions run in order, and a kick or ban stops everything — remaining actions on that condition and all later conditions are skipped.Put your logging and DM actions before any kick or ban, or they will never run.
Join Guard messages support a much richer variable set than raid reports, including the member, their account age, the matched rules and the condition name.

​
Building a sensible configuration

1

Start with raid detection alone

The defaults handle the obvious case. Leave Join Guard empty at first.
2

Add one narrow Join Guard condition

Combine two or three rules with “All” — a very new account and a default avatar and a generated name is almost never a real member.
3

Use a non-destructive action while you watch it

Assign a quarantine role and open a case rather than banning. Review for a week.
4

Tighten only once you trust it

Move to kicks or bans after seeing the condition behave on real traffic.

​
Troubleshooting

Check that accounts joining are actually younger than your Account Age threshold — older accounts are never counted.
Expected. Raid detection acts on the triggering member only. Use Join Guard to act on every matching join.
[ServerName] is never substituted, and the end message substitutes nothing at all.
Clearing the report channel does not persist. Pick a different channel instead.
Usually the user threshold is below 2, or the interval is above 300 seconds. Both are accepted by the form and rejected on save.
A kick or ban earlier in the action list aborts everything after it. Reorder so logging runs first.

Protection

Defends against damage from inside.

Auto-Roles

Delayed roles are a quieter anti-raid measure.