How do I read the anti-raid history and give my verdict (Threat / Legitimate)?
The History tab keeps the trace of everything anti-raid and anti-nuke decided. It is used to check and to correct.
Anti-nuke incidents
The Anti-nuke incidents table has five columns:
| Column | What it is |
|---|---|
| Author | The person or bot stopped (the “bot” mention specifies it). |
| Trigger | The action that exceeded the limit (for example deleting channels). |
| Measure | What the bot did (alert, quarantine, kick, ban). |
| Verdict | Your judgement: Threat or Legitimate. |
| When | The date and time. |
No incident? The message “anti-nuke has not stopped anything yet on this server” is good news.
Give your verdict
- Find the incident to judge
- Click “Threat” or “Legitimate” Two buttons in the row.
| Verdict | What it does |
|---|---|
| Threat | The attack is confirmed. The bot remembers it and will stop this type of behaviour earlier. |
| Legitimate | It was a false alarm. The author gets their roles and permissions back, and their ban is lifted. A person who was kicked is brought back by the member backup or receives a personal invitation. An author judged legitimate twice becomes more tolerated on this server. |
Be honest in your verdicts
The bot learns from you. A fair verdict reduces future false alarms without ever lowering the guard on real attackers.
The anti-raid log
At the very bottom, the Anti-raid log card lists events: Lockdown declared, Lockdown lifted, Influx observed, Attack stopped, Sensitive bot flagged, Webhook neutralised. Empty: “Nothing to report for now”.
The last 30 days statistics
- Lockdowns: number of lockdowns, joins refused and admitted.
- Attacks stopped: including how many by a bot.
- False positives judged: the share of incidents you judged legitimate.
- Watch: bots flagged and webhooks neutralised.
Still stuck?
Contact support with the title of this article, the step where you are stuck and what you see on screen.
Contact support More articles: ProtectionLast checked: 13 November 2026.