Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.fight.rocks/llms.txt

Use this file to discover all available pages before exploring further.

​
why use an anti-nuke system?

anti-nuke is a system that automatically performs an action on a user that is trying to perform malicious actions on your server. this is customizable to your liking and will keep your server safe from any harmful actions.

​
allowing users to modify anti-nuke

by default, only the server owner can modify the anti-nuke configuration. using this command, you can allow other users to be able to change the anti-nuke settings.
this is a very risky command, as this will allow the user to change any of the anti-nuke configuration
,antinuke trust (user)
to remove an anti-nuke admin, simply just run the command again and they will be removed.

​
whitelisting users from the anti-nuke

by default, everyone will be affected by anti-nuke. to exempt a user, simply whitelist them using the ,antinuke whitelist command.
this will allow a user to completely bypass all the anti-nuke restrictions
,antinuke whitelist (user)
to remove someone from the whitelist, simply run the command again and they will be removed.

​
enabling an anti-nuke module

​
available flags

the following flags can be used to define the anti-nuke module
the threshold is the number of actions a moderator can perform before being punished.
it’s recommended to keep the threshold between 1and 6
--threshold (number)
the punishment which will be applied to the moderator
Available punishments can be found in the punishments section
Last modified on May 3, 2026