Rhino

Security

Protect the server from the people who hold permissions as well as the people who don't.

Anti-nuke

Anti-nuke watches for destructive actions done in bulk. Each kind of action is a module: you switch it on, set how many it takes to trip it and pick the punishment. Only the server owner and the anti-nuke admins the owner names can change these settings.

Start with ,antinuke recommended, then read the result with ,antinuke config.

Modules take flags after on. --do picks the punishment and --threshold sets how many actions trip the module. Each command's page shows an example.

People and bots you trust

Whitelist the members and bots whose normal work would otherwise trip a module, and name the admins who may edit anti-nuke with you.

Dangerous permissions

Rhino can also act the moment a permission such as Administrator is handed to a role, or taken away.

Anti-raid

Anti-raid deals with accounts arriving, where anti-nuke deals with staff. Each check has its own switch and punishment.

If a raid is already under way, the owner can close every channel at once and open them again afterwards.

Fake permissions

A fake permission lets a role use the Rhino commands that need a permission without holding that permission in Discord itself. Your moderators can ban through Rhino while the real Ban Members permission stays off their role.

Filters

The filter removes messages that break the rules you switch on. Most filters keep a list of roles they skip, and ,filter bypass sets roles and channels that every filter skips.

Escalation

Points turn repeat offences into a ladder. Each filter is worth a number of points, and each step of the ladder is a punishment at a points total.

Jail and hard bans

Jail takes a member's roles away and leaves them one channel. A hard ban is put back whenever someone lifts it.

Verification

Hold new members behind a check before they can see the server.

Also in this area