pegasus/unrealircd
1
0
Fork 0
mirror of https://github.com/unrealircd/unrealircd.git synced 2026-07-07 04:13:13 +02:00
Code Activity

Update HELPOP EXTBANS on ~t (timed bans), ~m (msgbypass) and ~T (textban)

Browse Source 
since these are loaded by default since UnrealIRCd 4.2.0.
This commit is contained in:
Bram Matthys
2019-01-14 15:08:56 +01:00
parent f4b432ae94
commit 778be86c66
1 changed files with 27 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/conf/help/help.conf
+27 -6
View File
@@ -189,8 +189,15 @@ help Chmodes {
help ExtBans {
" These bans let you ban based on things other than the traditional nick!user@host";
" mask. They also provide support for things like ``quieting'' users (on other IRCds";
" you might do +q <hostmask>, on UnrealIRCd use +b ~q:<hostmask>).";
" mask. These bans start with a tilde, followed by a letter denoting the extban type.";
" For example +b ~q:nick!user@host denotes a quiet extban.";
" -";
" The following ban type can be used in front of any (ext)ban:";
" ==-Type--------Name---------------------------Explanation-----------------------==";
" | | Timed bans are automatically unset by the server after ";
" ~t | timedban | the specified number of minutes. For example: ";
" | | +b ~t:3:*!*@hostname ";
" ==------------------------------------------------------------------------------==";
" -";
" These bantypes specify which actions are affected by a ban:";
" ==-Type--------Name---------------------------Explanation-----------------------==";
@@ -208,6 +215,16 @@ help ExtBans {
" ~j | join | He may perform all other activities if he is already on ";
" | | the channel, such as speaking and changing his nick. ";
"-----------------------------------------------------------------------------------";
" | | Bypass message restrictions. This extended ban is only ";
" | | available as +e and not as +b. Syntax: +e ~m:type:mask. ";
" | | Valid types: 'external' (bypass +n), 'censor' (bypass +G),";
" | | 'moderated' (bypass +m/+M), 'color' (bypass +S/+c), and ";
" ~m | msgbypass | 'notice' (bypass +T). Some examples: ";
" | | +e ~m:moderated:*!*@192.168.* Allow IP to bypass +m ";
" | | +e ~m:external:*!*@192.168.* Allow IP to bypass +n ";
" | | +e ~m:color:~a:ColorBot Allow account 'ColorBot' ";
" | | to bypass +c ";
" ==------------------------------------------------------------------------------==";
" -";
" These bantypes introduce new criteria which can be used:";
" ==-Type--------Name---------------------------Explanation-----------------------==";
@@ -251,12 +268,16 @@ help ExtBans {
" ~S | certfp | (the one you see in /WHOIS). Mostly useful for safe ";
" | | ban exceptions and invite exceptions. ";
" | | Example: +iI ~S:00112233445566778899aabbccddeeff..etc.. ";
"-----------------------------------------------------------------------------------";
" | | Channel-specific text filtering. Supports two actions: ";
" ~T | textban | 'censor' and 'block'. Two examples: ";
" | | +b ~T:censor:*badword* and +b ~T:block:*something* ";
" ==------------------------------------------------------------------------------==";
" -";
"You may stack extended bans from the first group with the second group.";
"For example +b ~q:~c:#lamers would quiet all users who have joined #lamers.";
"Bans from the second group may also be used for invite exceptions (+I),";
"such as +I ~c:#trusted and +I ~a:accountname.";
"You may stack extended bans from the 2nd group with the 3rd group.";
"For example +b ~q:~c:#lamers would quiet all users who are also in #lamers.";
"Bans from the 3rd group may also be used for invite exceptions (+I),";
"such as +I ~c:@#trusted and +I ~a:accountname.";
};
help Chmodef {