12 min · Owner
Antinuke
Owner only. Master on, then modules. Whitelist last.
You will
The master switch is on, a log exists, and only the modules you chose can trip.
Examples use the default prefix, a comma.
Before you start
- Only the Discord owner should touch antinuke.
- Have a log channel. Whitelist last, not first.
Set it up
- Master on. Turn the master switch on. Modules stay off until you enable them.
,an on
- Point a log. Antinuke needs somewhere to write. Use your staff log, not jail-log.
,an log #mod-logs
- Modules. Enable the events you care about. Thresholds stay in the details. Do not copy someone else's numbers blindly. Defaults are 3 for ban and timeout, 1 for the rest.
,an ban on
- Whitelist last. Add trusted bots and roles after the modules work. Whitelist first and you will not notice a miss.
,an wl 123456789012345678
See it in Discord
This is the help card for this command. It uses the same syntax and example as `,help`.
member
,help an
nearAPP
Examples
,an
,an on
,an log #mod-logs
,an ban on
Do not
- Do not whitelist everyone first. You will think it is working when it is not.
Troubleshooting
- If antinuke does nothing, the master switch is off or the actor is whitelisted.
- Dashboard antinuke fields are editable by the Discord owner and antinuke admins.
Verify it works
- Confirm the log channel gets a test event after you enable logging.