Anti-Raid

Lunova's anti-raid system monitors member joins in real time. When too many users join in a short window, it fires automatically — either locking the server down or alerting staff.

Setup

/raidmode setup threshold: 10 window: 30 action: lockdown channel: #raid-alerts

Parameter	Default	Description
threshold	10	Number of joins within the window that triggers the response.
window	30s	Rolling time window in seconds.
action	lockdown	`lockdown` — raises server verification to max and logs it. `alert` — posts to the alert channel only, no server change.
channel	—	Channel where raid alerts and status messages are posted.

Administrator

Checking Status

/raidmode status

Shows the current configuration and whether a raid is currently active.

Ending a Lockdown

/raidmode end

Manually ends an active raid lockdown, restoring the server's previous verification level. Use this after the raid has passed.

Disabling

/raidmode disable

Turns off raid detection entirely. Any active lockdown is ended first.

How lockdown works

When triggered, Lunova records the current verification level, then raises it to Highest (must have a verified phone number).
An alert embed is posted to the configured channel with join timestamps and how many users triggered the threshold.
When /raidmode end is run, Lunova restores the previous verification level exactly.

⚠ If the bot is restarted while a lockdown is active, the lockdown state is saved in the database. /raidmode end can still be used after a restart to restore the original level.

Alert action

If action is set to alert instead of lockdown, Lunova only posts a warning embed to the alert channel. No server settings are changed. Useful for servers that want visibility without automatic intervention.