If you use anope, we suggest you restrict the modes there too via anope's nomlock feature, see the example below.Įxample to force and restrict channel modes IMPORTANT: Users may evade these restrictions via the MLOCK command from Services. Restrict users to set/unset the channelmodes listed here (don't use + or -).įor example you can set +G in modes-on-join and G in restrict-channelmodes, that way you can force all (new) channels to be +G and unable to do -G. Restrict users to set/unset the modes listed here (don't use + or -).įor example you can set +G in modes-on-connect and G in restrict-usermodes, that way you can force all users to be +G and unable to do -G. You can also specify a letter such as "o". The mode that a user will get when he's the first to join a channel. Not all modes can be set using this command. The modes that will be set on a channel when it is first created. The default value is: +kscfvGqobS in UnrealIRCd 5 and +bBcdfkqsSoO in UnrealIRCd 6. The snomask (server notice mask) that will be set on a user when they /OPER. The modes that will be set on a user when they /oper. The modes that will be set on a user at connection. See also set::reject-message::gline if you want a more custom disconnect message on GLINE/GZLINE. The email address that G:line questions should be sent to. See also set::reject-message::kline if you want a more custom disconnect message on KLINE/ZLINE. The email address that K:line questions should be sent to. We generally don't recommend having more than 2 set blocks because then it is too easy to loose track of them ("what settings is where?"), but technically it is perfectly possible and permitted.Īvailable settings set::kline-address It is perfectly fine to have multiple set blocks! In fact it's quite normal to have one block with network-wide settings, and another set block with server-specific settings. If the above is unclear, then maybe have another read at the Configuration file syntax article. Or you could put them in separate set blocks like this: What we actually mean is that you should write them out like this:
You should NOT write set::options::hide-ulines in the configuration file! It's just a shorthand, an abbreviation. Syntax used in this documentation Īs described in Configuration file syntax we will refer to settings like set::options::hide-ulines or set::auto-join. The set block is an ideal candidate to be shared. If you (already) run multiple IRC servers then have a look at Sharing settings between servers to ease the burden when updating settings. 3.102 set::max-unknown-connections-per-ip.
3.94 set::spamfilter::detect-slow-fatal.3.90 set::spamfilter::virus-help-channel.3.69 set::tls::options::fail-if-no-clientcert.3.45 set::options::allow-part-if-shunned.3.44 set::options::mkpasswd-for-everyone.3.9.1 Example to force and restrict channel modes.
0 kommentar(er)
