Extended Bans
m (Protected "Extended Bans": Use of html tag ([edit=sysop] (indefinite) [move=sysop] (indefinite))) |
m |
||
| Line 1: | Line 1: | ||
| - | Extended bans, also known as ban | + | Extended bans, also known as ban conditionals, allow different checks than the usual nick!user@host match to determine whether someone should be banned, giving channel operators more flexibility and control over their channel's ban list. |
On DareNET (like a few other networks) extended bans are of the form <code>'''$[!]<type>[:<data>]'''</code>. The <type> is one character (case sensitive) and determines the type of match that is to be used. Currently all types require an extra field <data>. If the exclamation mark (!) is present, the result of the comparison will be negated (discussed below). | On DareNET (like a few other networks) extended bans are of the form <code>'''$[!]<type>[:<data>]'''</code>. The <type> is one character (case sensitive) and determines the type of match that is to be used. Currently all types require an extra field <data>. If the exclamation mark (!) is present, the result of the comparison will be negated (discussed below). | ||
Revision as of 18:44, 20 September 2010
Extended bans, also known as ban conditionals, allow different checks than the usual nick!user@host match to determine whether someone should be banned, giving channel operators more flexibility and control over their channel's ban list.
On DareNET (like a few other networks) extended bans are of the form $[!]<type>[:<data>]. The <type> is one character (case sensitive) and determines the type of match that is to be used. Currently all types require an extra field <data>. If the exclamation mark (!) is present, the result of the comparison will be negated (discussed below).
The following types of extended bans are currently supported:
| Type | Name | Purpose |
|---|---|---|
| $a | Account | If a user's account name matches this ban, (s)he will be unable to join. |
| $c | Channel | If a user is in a channel that matches this ban, (s)he will be unable to join. |
| $j | Shared Bans | If a user matches a ban on the channel who's ban list is being shared, (s)he will be unable to join. |
| $n | Nick Change | If a user matches this ban, (s)he will be unable to change their nickname while in the channel. |
| $q | Quiet | If a user matches this ban, (s)he will be unable to send messages to the channel. |
| $r | Realname | If a user's realname (gecos) matches this ban, (s)he will be unable to join. |
| $t | Text | Allows you to specify text that will be blocked if a user's privmsg or notice to the channel contains it. * and ? wildcards supported. |
In This Guide: |
Quiet and Nick Change
The $q (quiet) and $n (nick change) types are similar to normal bans, except that they allow you to control what a user can do without preventing them from being able to join the channel. The $q type prevents users matching a given mask from sending messages/notices to the channel, while the $n type prevents them from changing their nickname.
| Type | Syntax |
|---|---|
| $q | /mode #channel +b $q:nick!user@host
|
| $n | /mode #channel +b $n:nick!user@host
|
Examples:
A.) If we wanted to allow users connecting from a ".br" host to join the channel, but prevent them from being able to send messages/notices to the channel, we could set the following $q type extended ban:
/mode #ourchannel +b $q:*!*@*.br
B.) If we also wanted to prevent users connecting from a ".br" host from changing their nickname while their in our channel, we could set the following $n type extended ban:
/mode #ourchannel +b $n:*!*@*.br
Channel
The $c (channel) type prevents users who are in a matching channel from joining your channel.
| Type | Syntax |
|---|---|
| $c | /mode #channel +b $c:#channel
|
Example:
A.) If we wanted to prevent users who are currently in a channel with the word warez in its name from joining our channel, we could set the following $c type extended ban:
/mode #ourchannel +b $c:#*warez*
Realname
The $r (realname/gecos) type prevents users with a matching realname from joining your channel.
Note that the $r type treats "_" as both the underscore character and a space.
| Type | Syntax |
|---|---|
| $r | /mode #channel +b $r:realname
|
Example:
A.) If we wanted to prevent users who had the word bot in their realname (gecos) from the joining our channel, we could set the following $r type extended ban:
/mode #ourchannel +b $r:*bot*
Account Bans
The $a (account) type allows you to ban (logged in) users who's username (i.e., account name) matches the specified account mask.
Note, these types of bans can only ever match users logged into their NickServ account.
| Type | Syntax |
|---|---|
| $a | /mode #channel +b $a:account
|
Example:
A.) If we wanted to ban all users who's account name contained the word joe, we could set the following $a type extended ban:
/mode #ourchannel +b $a:*joe*
Account type extended bans act identical to the previous method of banning users based on their account name (i.e., /mode #channel +b *!*@accountname.*); however, negation (reverse logic) can also be used with account type extended bans, which cannot presently be done with the old method. We discuss negation a little later in this guide.
Shared Bans
The $j type allows sharing channel ban lists.
| Type | Syntax |
|---|---|
| $j | /mode #channel +b $j:#channel
|
Example:
A.) For this example, the name of our channel is #ourchannel and we want to use #shared's channel ban list inconjunction with our own. So, to do this we could set the following $j type extended ban:
/mode #ourchannel +b $j:#shared
Now, whenever a user tries to join our channel, #ourchannel, they'll be checked against #shared's ban list in addition to our own ban list. If a match is found in either ban list, the user will be prevented from joining.
Text Bans
The $t (text) type allows channel operators to specify text (wildcards supported) that will be blocked if (1) the user's message or notice to the channel matches it, and (2) the user's host matches the entry as well.
| Type | Syntax |
|---|---|
| $t | /mode #channel +b $t:nick!user@host:text
|
Examples:
A.) Let's say we wanted to block all channel messages and notices that contained the word damn, regardless of the user sending it. To do this we could set the following $t type extended ban:
/mode #ourchannel +b $t:*!*@*:*damn*
B.) Using example A, let's say we only wanted to block such messages from users connected from a ".br" host. To do this we would slightly modify the above $t type extended ban as follows:
/mode #ourchannel +b $t:*!*@*.br:*damn*
Negation / Reverse Logic
If "!" is prepended to the type of an extended ban, then the result of the comparison is negated. In other words, it will have a reversed effect. Negation is currently not possible with quiets. We suggest using excepts in this instance, instead.
Example:
A.) Let's say we wanted to allow users to join our channel ONLY if they're already present in #darenet. To do this, we would set a $c type extended ban, but prepending "!" to the type flag:
/mode #ourchannel +b $!c:#darenet
Assistance
Should you need assistance using the extended bans feature, feel free to stop by #Support
