Skip to main content

Search GiselleBot's commands and docs.

Try /ban, or start with / for commands only.

Press Ctrl K anywhere in the dashboard to open this.

GiselleBot and Moderation

Note

Originally written by NaviKing, updated to reflect the current slash commands and dashboard pages.

GiselleBot has a points-based moderation system for tracking misbehavior and notes on your server's users. This guide covers how to set up and use the moderation module. It does not replace the documentation for each command, and not every command appears here; for details, see the [full Moderation Module documentation](/docs/moderation-and-administration/moderation) page or use GiselleBot's `/help` command.

Enabling the moderation module

The moderation module works properly only with both the moderation and warning logs enabled somewhere on your server. Use GiselleBot's /log toggle command to enable them by running each command below

/log toggle type:Warning
/log toggle type:Moderation

After this, you will need to define the roles that should be allowed to use the moderation module. This is done from your server's Command Permissions page on the dashboard - authorize any number of roles there for the Moderation module to designate your mod team.

Rules and Points

You may also want to add the rules of your server to GiselleBot and configure how many points they are worth. Rules are assigned point values to denote how severe a violation is by default, and a moderator can adjust them on a per-violation basis (more on that later). For example, a user that is breaking a nickname rule is likely committing a less severe violation than a user posting NSFW content on the server. Points let you weigh both how often and how severely a user breaks the rules.

You can see the default set of rules that GiselleBot has by using the /rules command. Disabling rules you don't want to use, and adding your own rules (including the rule name, description, alias, and point value), is done from your server's Moderation Settings page on the dashboard. Global rules will always be represented by a number, while custom rules will be represented with s_ before the rule number (e.g., s_1).

The system was designed such that rules are expected to be an even number between 2 and 10 points, with 6 points representing an "average" warning. You can use any number you want, including 0.

Also by default, GiselleBot will half the points associated with the first infraction of each rule that a user commits. This results in users being able to commit two different violations of three different rules before being banned. Other halving rules can be configured with the Half Logic setting on your server's Moderation Settings page on the dashboard. For example, setting Half Logic to "none" will prevent GiselleBot from halving the points for any warnings a user received. This can be useful if you want your server to be more strict.

Once enough points accumulate, GiselleBot's moderation system will automatically suggest that a user be muted when they have acquired 18 points and banned when they hit 27 points. Warnings expire to 1 point after 90 days, and these two thresholds apply only to unexpired points. Users that acquire 54 points total, regardless of expiration, will also cause GiselleBot to suggest banning the user, which is referred to as an absolute ban. GiselleBot does not enforce any of these thresholds automatically, so you can ignore them if you want.

Types of Punishments

GiselleBot offers several moderation actions you can take against a user. By default, each action logs a case associated with that user and sends them a direct message about the violation. That message includes the name of the moderator who sent the warning by default, and can be anonymized from your server's Moderation Settings page on the dashboard.

The available punishments are warning, muting, banning, kicking, channel banning (preventing a user from accessing a channel), channel muting (preventing a user from speaking in a channel), image banning (preventing a user from uploading images or embedding links), and channel image banning (preventing a user from uploading images or links in a specific channel).

The moderation actions below are now slash commands (/warn, /kick, /mute, /ban, and the /restrict command tree for the channel/image restrictions), and their exact options differ slightly by command - see the full Moderation Module documentation for the full list. In general, they take

  • A user option
  • reason: a text explanation of how the rule was broken
  • rule: the name, ID, or alias of the rule broken
  • attachment1 through attachment4: up to 4 files you upload as proof of the infraction
  • points: overrides the case's point value instead of using the rule's default (available on /warn, /ban, /kick, and /mute)
  • justification: explains a points override - required whenever points is set, and rejected otherwise
  • silent: logs the case without DMing the user
  • no_case: executes the action without creating a case at all (also skips the DM, matching the legacy --no-case flag). Available on /warn, /ban, /kick, /mute, and the case-generating /restrict subcommands

Note

Each of these slash commands only takes one target user per invocation. A case's reason, rule, attachments, and point value can still be adjusted afterwards with /case edit (see Reviewing, Modifying, and Deleting Cases below) - useful for filling in details you skipped at the time, or fixing a mistake - but you can also set them in the same command that creates the case with points/justification. /warn, /kick, /mute, and /ban each have their own silent option if you don't want the target DMed at all.

After running a moderation command, GiselleBot will inform whoever runs the command if they are missing any necessary parameters, and will show them how to fix the case with /case edit. You can turn these alerts off from your server's Moderation Settings page on the dashboard. A few example moderation commands are provided below; read the full documentation on the moderation commands for the rest.

/warn user:@user rule:1 reason:being a jerk
/mute user:356831787445387285 duration:1d reason:Posting NSFW content in the #general channel
/ban user:356831787445387285 rule:Spam reason:Posting a phishing link in chat

Reviewing, Modifying, and Deleting Cases

After logging an action against a user, it may be necessary to review their warning history, edit, or remove warnings against them.

The /history command can be used to look up a user's warning history with their ID, name, or mention (one user per call). If you wish to review any cases in detail, /case show with the case ID will show you that case. Similarly, cases can also be deleted using /case delete and the case ID. Moderators are allowed to delete automoderator cases created by the bot (e.g. in case of auto-moderation actions), but cannot delete cases created by other mods, including themselves. Only users with Manage Server permissions are allowed to delete cases issued by hand.

/case edit overwrites parts of an existing case: reason, rule, points, justification, the attachments, or how long a punishment still has to run (duration, counted from the moment you run the edit). Uploading attachment1-attachment4 replaces the case's evidence, and clear_attachments removes it. Deleting or restoring a case needs Manage Server, but editing your own case does not; editing someone else's does. If a server enables Prevent Moderators From Editing Their Own Cases on its Moderation Settings page, editing a case you issued needs Manage Server too. You do not have to change every field at once. For example, if you only need to fix the reason of a case, you can use

/case edit id:1 reason:New reason

You can include as many or as few of the options as you want. If the edit changes anything, the target is DMed a summary of what changed - add silent:true if you'd rather it stay quiet.

Bonus: Using Zero Point Rules

One more feature of GiselleBot's warning system is "0 point rules". Rules worth zero points do not move someone any closer to a ban. That gives you a couple of options.

One option is to make a dummy rule worth 0 points to be used to make silent notes on someone's account. For example, on your server's Moderation Settings page on the dashboard, you could add a rule named "None", with a description like "This is an informational message and does not count towards being banned from the server", and a point value of 0.

That rule can be used in a "warning" like this

/warn user:@user rule:None reason:This user was acting weird in someone's DMs. Give them an official warning if you hear about it happening again

Note

Want this to stay completely quiet? Add silent:true to the /warn command above and the target won't be DMed about it either.

If you use your own moderation system based on warning counts instead of points, you may want to make all of your warnings worth zero points so the points system does not confuse your moderators. You can still use GiselleBot as a normal moderation bot.

Summary

The moderation module has a lot of moving parts. Set it up properly, check that the rules your moderators have access to suit your server, and then you can start applying punishments. You can also leave notes on someone's account or skip the points system entirely.

More information is in the module's documentation (see the full Moderation Module documentation). If you still have trouble, join GiselleBot's Support Server and ask there.