Punishments are actions like ban, kick or mute that can be given to a user when he violates the rules. You can either call punish users directly by using commands, or you can define punishments that happen after a user reaches a certain amount of strikes.
How can I punish a user after reaching a certain amount of strikes?
With the punishmentconfig command you can set after how many strikes a certain punishment action will be given.
Strikes are points that users get for violating server rules. Every time the user receives a strike, he gets a personal message telling him how many strikes he has and why he got them. When a user reaches a certain amount of strikes, he will receive a punishment.
What are violations?
Violations are auto-moderation rules that you can enable or disable on your server. Currently, the following violations exist:
For each of those violations, you have to define how many strikes will be given if someone violates it. You can do that by using the strikeconfig command:
For example, if you want users to get 2 strikes for violating the invites rule, then you would use the following command:
You can check the current config by doing:
This violation is triggered whenever the user posts an invite link to another discord server.
Example:
!strikeconfig invites 1
To delete the strike config:
!strikeconfig invites 0
Config options:
This violation is triggered whenever the user posts a link.
Example:
!strikeconfig links 1
To delete the strike config:
!strikeconfig links 0
Config options:
This violation is triggered whenever the user posts blacklisted words.
Example:
!strikeconfig words 1
To delete the strike config:
!strikeconfig words 0
Config options:
This violation is triggered whenever the user posts a message that is mostly in CAPS.
Example:
!strikeconfig allCaps 1
To delete the strike config:
!strikeconfig allCaps 0
Config options:
This violation is triggered whenever the user posts the same text multiple times.
Example:
!strikeconfig duplicateText 1
To delete the strike config:
!strikeconfig duplicateText 0
Config options:
This violation is triggered whenever the user quickly posts messages.
Example:
!strikeconfig quickMessages 1
To delete the strike config:
!strikeconfig quickMessages 0
Config options:
This violation is triggered whenever the user mentions mutliple users.
Example:
!strikeconfig mentionUsers 1
To delete the strike config:
!strikeconfig mentionUsers 0
Config options:
This violation is triggered whenever the user mentions mutliple roles.
Example:
!strikeconfig mentionRoles 1
To delete the strike config:
!strikeconfig mentionRoles 0
Config options:
This violation is triggered whenever the user posts multiple emojis.
There are many config options that can be set. You don't have to set all of them. If you just added the bot, just run !setup, which will guide you through the most important ones.
The list of moderated channels (this acts as a whitelist, leave empty to moderate all channels, or use autoModIgnoredChannels to ignore certain channels).
Type: Channel[]
Default: ``
Reset to default: !config autoModModeratedChannels default
Examples:
!config autoModModeratedChannels #general
!config autoModModeratedChannels #support,#help
The list of roles that are moderated (this acts as a whitelist, leave empty to moderate all roles, or use autoModIgnoredRoles to ignore certain roles).
Type: Role[]
Default: ``
Reset to default: !config autoModModeratedRoles default
Le temps que l'utilisateur a pour valider le captcha.
Whether or not verification attempts will be logged
The list of roles that are moderated (this acts as a whitelist, leave empty to moderate all roles, or use autoModIgnoredRoles to ignore certain roles).
The list of moderated channels (this acts as a whitelist, leave empty to moderate all channels, or use autoModIgnoredChannels to ignore certain channels).
Selon la commande les valeurs valides peuvent changer. Utilisez !help <command> (ex : !help addRank) pour avoir plus d'informations sur la commande et les valeurs valides pour cette commande.
