Moderation
Warns, timeouts, kicks and bans that each leave a numbered case: nothing happens without a record.
Nothing happens without a record
Every sanction leaves a numbered case in your server's history, whether a moderator typed it or a Discord AutoMod rule handed it out. A ban is a ban and a strike.
The full sanction set
Note, warn, mute, kick, ban, tempban, softban and unban, with tempbans and timeouts lifting themselves when the duration you gave runs out.
Auto-escalation and warn decay
Decide how many warns trigger a heavier sanction on their own, and let old warns expire so nobody is judged forever on one bad week.
A record one command away
/modhistory prints a member's history newest first, narrowed to notes or warns or widened to the revoked ones. /case views, edits or revokes any entry, and a revoke cancels the sanction's effect while keeping the paper trail.
Full documentation
Every setting explained, step by step.
Slash commands
The slash commands you'll use with this feature on Discord.
Questions about Moderation
Which permission does a moderator need?
The Discord permission that matches the command: Timeout Members for /warn, /mute, /case and /modhistory, Kick Members for /kick, Ban Members for the ban commands, and Manage Messages for /note. The Moderator roles field on the dashboard does not replace it.
Why was my sanction refused?
FlaviBot refuses to act on you, on itself, on the server owner, or on anyone whose highest role is equal to or above yours. It also refuses when it lacks the Discord permission the action needs, or while its view of the server is still loading right after a restart.
Can a sanction be undone?
Yes. /case can revoke any entry, which cancels the sanction's effect while keeping the record. /unmute and /unban are recorded too, as reversals rather than strikes.
Ready to try it out?
Add FlaviBot to your server and start using this feature for free.