Tip of the day: Channel mode +H provides Channel history to modern clients. Optionally, it can be stored on-disk to be preserved between server restarts.
|
Translations:Extended bans/5/en
Jump to navigation
Jump to search
Group 3: selectors
These bantypes introduce new criteria which can be used:
| Letter | Name | Module | Explanation | Example |
|---|---|---|---|---|
| a | account | extbans/account | If a user is logged in to services with this account name, then this ban will match. Note that the account name is not necessarily the same as the nick name. There are also two special bans: |
+e ~a:SomeAccount
+I ~a:SomeAccount |
| c | channel | extbans/inchannel | 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
+e ~c:@#trustedops |
| G | security-group | extbans/securitygroup | If the user matches this security group then (s)he is unable to join. | +b ~G:unknown-users |
| O | operclass | extbans/operclass | 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* |
| r | realname | extbans/realname | 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) | +b ~r:*Stupid_bot_script* |
| S | certfp | extbans/certfp | 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
+I ~S:0000000etc |