mirror of
https://github.com/jlu5/PyLink.git
synced 2025-01-11 20:52:42 +01:00
example-conf: sort clientbot ex. options so that cb-specific ones are at the end
This commit is contained in:
parent
804791b8af
commit
0c2927fb1e
@ -408,13 +408,28 @@ servers:
|
||||
#ssl_certfile: mycert.pem
|
||||
#ssl_keyfile: mycert.pem
|
||||
|
||||
# Autoconnect works as usual.
|
||||
autoconnect: 30
|
||||
|
||||
# Message throttling: when set to a non-zero value, only one message will be sent every X
|
||||
# seconds. If your bot is constantly running into Excess Flood errors, raising this to
|
||||
# something like 0.5 or 1.0 should help. Defaults to 0.005 if not set.
|
||||
throttle_time: 0.3
|
||||
|
||||
# Determines whether messages from unknown clients (servers, clients not sharing in a -n
|
||||
# channel, etc.) should be forwarded via the PyLink server. If this is disabled, these
|
||||
# messages will be silently dropped. This overrides the "accept_weird_senders" option in the
|
||||
# "relay:" configuration block, and defaults to True for consistency with older releases.
|
||||
#relay_weird_senders: false
|
||||
|
||||
### The following options are specific to Clientbot servers:
|
||||
# SASL login: for mechanisms, only EXTERNAL (SSL cert) and PLAIN (username and password)
|
||||
# are supported so far.
|
||||
# SASL PLAIN requires the sasl_username and sasl_password options to be set, while
|
||||
# SASL EXTERNAL requires ssl, ssl_certfile, and ssl_keyfile to work.
|
||||
#sasl_mechanism: "PLAIN"
|
||||
#sasl_username: "mIRCsKripterz"
|
||||
#sasl_password: "DownLoaditn00b!!!"
|
||||
#sasl_password: "somestrangepassword"
|
||||
|
||||
# Defines the SASL timeout - this defaults to 15 seconds.
|
||||
#sasl_timeout: 15
|
||||
@ -425,14 +440,6 @@ servers:
|
||||
# InspIRCd 3.x and charybdis 4+ (and derivatives) are some compatible examples (as of 2016-12-19)
|
||||
#sasl_reauth: true
|
||||
|
||||
# Autoconnect works like usual.
|
||||
autoconnect: 30
|
||||
|
||||
# Message throttling: when set to a non-zero value, only one message will be sent every X
|
||||
# seconds. If your bot is constantly running into Excess Flood errors, raising this to
|
||||
# something like 0.5 or 1.0 should help. Defaults to 0.005 if not set.
|
||||
throttle_time: 0.3
|
||||
|
||||
# Raw IRC messages to send on connect. As of 2.0-alpha2, expansions such as $nick, $ident,
|
||||
# and $host are also supported via Python template strings
|
||||
# (https://docs.python.org/3/library/string.html#template-strings)
|
||||
@ -446,12 +453,6 @@ servers:
|
||||
# This defaults to false if not specified.
|
||||
#track_oper_statuses: false
|
||||
|
||||
# Determines whether messages from unknown clients (servers, clients not sharing in a -n
|
||||
# channel, etc.) should be forwarded via the PyLink server. If this is disabled, these
|
||||
# messages will be silently dropped. This overrides the "accept_weird_senders" option in the
|
||||
# "relay:" configuration block, and defaults to True for consistency with older releases.
|
||||
#relay_weird_senders: false
|
||||
|
||||
# Determines whether the bot should enumerate ban/banexception/invex modes when joining channels.
|
||||
# This is required for relay mode sync to work properly, because the bot will otherwise refuse to
|
||||
# relay unbans (Clientbot only removes modes that it knows are set).
|
||||
|
Loading…
Reference in New Issue
Block a user