/antinuke
configurationProtect the server from being taken apart.
What it does
Use it to set up Anti-nuke: what Kirzen does to whoever passes a limit, where the alerts go, how many of each action are allowed, and who is exempt.
Anti-nuke counts what each person does to your channels, roles, members and webhooks inside a short window, and acts when one person reaches the limit.
Example
/antinuke statusProtection: on
Response: strip
Alerts: nowhere
Window: 15s
Server owner immune: yes
Bots immune: no
Limits: Deleting channels: 3 · Creating channels: 5 · Editing channels: 6 · Deleting roles: 3 · Creating roles: 5 · Editing roles: 6 · Banning members: 3 · Kicking members: 4 · Handing out roles: 2 · Pruning members: 1 · Changing webhooks: 2 · Creating webhooks: 2 · Deleting webhooks: 3 · Deleting emoji: 5
Exempt: nobody
Example reply in English, with the default settings after the owner turns the protection on.
Good to know
- Only the server owner can turn the protection on or off. Everything else needs the Administrator permission.
- It starts off. Until the owner turns it on, nothing is being watched.
- Kirzen needs the View Audit Log permission. Without it, the protection has almost nothing to go on, and the command warns you.
- Without an alert channel Kirzen acts quietly. The alerts option sets one.
- Limits go from 1 to 100, and the window from 5 to 300 seconds.
- Replies are only visible to you.
Parameters
statusOptionalWhat is configured, and what has been caught.
toggleOptionalTurn the protection on or off.
punishmentOptionalWhat Kirzen does to whoever trips it.
alertsOptionalWhere Kirzen reports what it caught.
limitOptionalHow many of one action, by one person, before it trips.
windowOptionalHow many seconds the counting window covers.
trustOptionalExempt a person or a role from the protection.
untrustOptionalRemove an exemption.