​
Getting started

Antinuke is triggered by a threshold set per user. For example, the threshold could be 3 bans before triggering. Your threshold should never be too high, and should be set between 1-6 if you want antinuke to work properly.

​
Configuration

​
Antinuke Admins

Initially, only the server owner can run commands relating to antinuke. However, the owner can designate ‘Antinuke Admins’ that have full access to enabling, disabling, and whitelisting in relation to Antinuke. Antinuke Admins can be added with the command an admin [user]. Make sure you trust these people.

​
The 3 main parameters

  • --threshold (How many actions are allowed before trigger)
  • --do (What punishment to enact)
  • --command (If bleed commands, eg. ban, also count towards the threshold)

​
The 8 main modules

  • role deletion
  • channel deletion
  • emoji deletion
  • webhook creation
  • mass member ban
  • mass member kick
  • vanity protection
  • anti bot join filter
    The --command paramter only applies to modules with command equivalents - for example you cannot apply the --command parameter on the channel deletion module as there is no channel delete command within bleed

​
Example

antinuke role on
antinuke role on --do ban
antinuke role on --threshold 3
antinuke role on --do ban --command on
antinuke role on --do ban --command on --threshold 3
The vanity protection module only takes the --do parameter. The anti bot join filter module doesn’t take any.
antinuke vanity on 
antinuke botadd on
antinuke vanity on --do kick