Translations:Extended bans/5/en

These bantypes introduce new criteria which can be used: {| class="wikitable" !Extban !Module !Explanation !Example !a !extbans/account +I ~a:SomeAccount !c !extbans/inchannel ''+e ~c:@#trustedops !O !extbans/operclass !r !extbans/realname !R !extbans/regnick +I ~R:Nick !S !extbans/certfp +I ~S:0000000etc
 * If a user is logged in to services with this account name, then this ban will match. This is slightly different than ~R, in the sense that a user with nick ABC may be logged in under account XYZ. Not all services packages support this, in which case you will have to use ~R instead.
 * +e ~a:SomeAccount
 * If the user is in this channel then (s)he is unable to join. A prefix can also be specified (+/%/@/&/~) which means that it will only match if the user has that rights or higher on the specified channel.
 * +b ~c:#lamers
 * If the user is an IRCOp and the oper::operclass matches this name then the ban/invex will match. You can use this to for example create *admin* only channels.
 * +iI ~O:*admin*
 * If the realname (gecos) of a user matches this then (s)he is unable to join. Since real names may contain spaces you can use a underscore to match a space (and underscore)
 * style=white-space:nowrap|''+b ~r:*Stupid_bot_script*
 * If a user has identified to services for this nick then this ban will match. This means this ban is generally only useful for ban exemptions (+e) and invite exceptions (+I).
 * +e ~R:Nick
 * When a user is using SSL/TLS with a client certificate then you can match the user by his/her SSL fingerprint (the one you see in /WHOIS). Useful for ban exemptions (+e) and invite exceptions (+I).
 * +e ~S:0000000etc