GitHub/PyLink
3
0
Fork 0
mirror of https://github.com/jlu5/PyLink.git synced 2025-02-17 14:01:03 +01:00
Code Issues Projects Releases Wiki Activity

example-conf: describe more thoroughly how antispam handles unsupported punishments

Browse Source
This commit is contained in:
James Lu 2018-10-20 11:58:36 -07:00
parent 5c4fba653f
commit 5a482118b8
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
example-conf.yml
View File

@ -951,8 +951,12 @@ stats:
# Sets the punishment that Antispam's text spamfilter should use. # Sets the punishment that Antispam's text spamfilter should use.
# Valid values include "kill", "kick", "ban", "quiet", and combinations of these strung # Valid values include "kill", "kick", "ban", "quiet", and combinations of these strung
# together with "+" (e.g. "kick+ban"). Defaults to "kick+ban+block" if not set. # together with "+" (e.g. "kick+ban"). Defaults to "kick+ban+block" if not set.
# If you want Antispam to also monitor PM spam, you will want to change this to something # If you want to use Antispam with PM monitoring (see the "watch_pms" option below), you
# not channel-specific (such as "kill" or "block"). # will want to include at least one punishment that is not channel-specific
# ("kill" or "block").
# Punishments not supported in a context or network (e.g. kicking for PM spam or "quiet"
# on a network that doesn't support it) will be silently dropped if others succeed.
# If no punishments succeed, then a warning will be logged.
#punishment: kick+ban+block #punishment: kick+ban+block
# Sets the kick / kill message used when the text spamfilter is triggered. # Sets the kick / kill message used when the text spamfilter is triggered.