Channel Modes
Various modes can be set on channels. Use /mode #channel
to list current
channel modes and /msg ChanServ info #channel
to list modes set with MLOCK.
Using /msg ChanServ LISTMODES
will give you the current channel modes and
MLOCK of all channels which you have privileges in, avoiding the need to check
each channel individually.
All channel modes will be lost when a channel becomes empty. Enable GUARD to preserve modes.
To set a mode, use /mode #channel +(mode)
replacing (mode)
with the letter
that corresponds to the mode. To unset a mode, use /mode #channel -(mode)
Available channel modes
Mode (name) | Description |
---|---|
b
channel ban |
Takes a mask as a parameter. Users matching the mask are
prevented from joining or speaking. Sending You can append For example:
|
c
colour filter |
Strip colour and formatting codes from channel messages. |
C
block CTCPs |
Blocks CTCP commands (other than |
e
ban exemption |
Takes a mask as a parameter. Ban exemption matches
override For example:
|
f
forward |
Takes a channel name as a parameter. Users who cannot join the channel
(because of An operator can set Usually you want to set forwards with |
F
enable forwarding |
Allow operators in other channels to forward clients to this channel, without requiring ops in the target channel. |
g
free invite |
Anybody in the channel may invite others (using the |
i
invite only |
Users are unable to join invite-only channels unless they are invited
or match a |
I
invite exemption |
Takes a mask parameter. Matching clients do not need to be
invited to join the channel when it is invite-only ( Commonly used with the $a extban.
|
j
join throttle |
This mode takes one parameter of the form |
k
password |
To enter the channel, you must specify the password on your |
l
join limit |
Takes a positive integer parameter. Limits the number of users who can be in the channel at the same time. |
m
moderated |
Only opped and voiced users can send to the channel. This mode does not prevent users from changing nicks. |
n
prevent external send |
Users outside the channel may not send messages to it. Keep in mind that bans and quiets will not apply to external users. |
p
private |
The |
q
quiet |
Takes a mask parameter. Works like |
Q
block forwarded users |
Users cannot be forwarded (see |
r
block unidentified |
Prevents users who are not identified to services from joining the channel. Users already in the channel are not affected. |
R
silence unidentified |
Prevents users who are not identified to services from sending messages to the channel. |
s
secret |
This channel will not appear on channel lists or |
S
TLS-only |
Only users connected via TLS may join the channel while this mode is set. Users already in the channel are not affected. |
t
ops-topic |
Only channel operators may set the channel topic. |
T
block notice |
Blocks channel notices (other than CTCP replies, see |
u
unfiltered |
Receive messages that are filtered server side by Libera.Chat based on
content, usually spam. Set |
z
reduced moderation |
The effects of |
Restricted channel modes
The following channel modes can only be added by Libera.Chat staff.
Mode (name) | Description |
---|---|
L
large ban list |
Increase maximum number of |
P
permanent |
Channel does not disappear when empty. |
Masks
+b
, +e
, +I
, and +q
all take a mask to determine which users to match.
The common form of a mask is nick!user@host
. The wildcards *
and ?
are
allowed, matching zero-or-more and exactly-one characters, respectively. Bans
set on IP addresses will apply even if the affected user joins with a resolved
hostname, but will not apply if the user has a cloak.
CIDR notation
is supported in bans.
The second form, called extbans, can be used for bans based on user data.
These entries have the general format $X
or $X:data
. Optionally, they can
be negated with a tilde (~
) before the character: for example, $~a
matches
every user that is not identified to services.
Available extban types
Type (name) | Description |
---|---|
$a
account name |
Match users identified to the account specified in the parameter.
Accepts wildcards; an empty |
$g
matching guest |
Takes a parameter that is matched as a normal |
$j
cannot join other channel |
Takes an exact channel name (no wildcards or globbing) as its parameter
and matches any user who is banned from that channel. Due to caching by
the server, a change to the target channel’s ban list may not immediately
affect a user’s ability to send to the channel using |
$r
ircname |
Matches on a client’s ircname, or gecos. The parameter accepts wildcards.
For example: |
$x
full match |
Takes a parameter that is matched on a client’s full
|
$z
connected securely |
Accepts no parameters. Matches users who are connected via SSL/TLS. |
Based on content © 2016-2021 freenode/web7.0’s contributors under Creative Commons BY-NC-SA