1 TS6 protocol description
2 Written by Jilles Tjoelker
3 Edits by Elizabeth Myers to add TS rules described by Lee Harvey.
5 General format: much like rfc1459
6 Maximum parameters for a command: 15 (this does not include the prefix
9 SID: a server's unique ID. It is configured in each server and consists of
10 a digit and two alphanumerics. Sending SIDs with lowercase letters is
13 UID: a client's unique ID. It consists of the server's SID and six
14 alphanumerics (so it is nine characters long). The first of the alphanumerics
15 should be a letter, numbers are legal but reserved for future use.
17 hunted: a parameter type used for various remote requests. From local users,
18 nicknames and server names are accepted, possibly with wildcards; from servers,
19 UIDs/SIDs (sending names or even wildcards is deprecated). This is done with
20 the function hunt_server(). Any rate limiting should be done locally.
23 duration: a parameter type used for ban durations. It is a duration in seconds.
24 A value of 0 means a permanent ban.
26 IP addresses: IP addresses are converted to text in the usual way, including
27 '::' shortening in IPv6, with the exception that a zero is prepended to any
28 IP address that starts with a colon.
30 propagation: to which other servers the command is sent
32 For all commands with a hunted parameter, the propagation is determined by
33 that, and not otherwise specified.
35 For all commands with a target server mask parameter, the propagation is
36 determined by that, and not otherwise specified. The command is sent to all
37 servers with names matching the given mask (for example '*', '*.example.com',
38 'irc.example.com'). Those servers do not have to be directly connected.
39 Targets cannot be SIDs.
41 Propagation broadcast means the command is sent to all servers.
43 Propagation one-to-one means the command is only sent to the target or the
44 server the target is on.
46 Propagation none means the command is never sent to another server if it is
49 For some other commands, the propagation depends on the parameters and is
52 services server: server mentioned in a service{} block. There are no services
55 service: client with umode +S. This implies that it is on a services server.
58 The initiator sends the PASS, CAPAB and SERVER messages. Upon receiving the
59 SERVER, the listener will check the information, and if it is valid, it will
60 send its own PASS, CAPAB and SERVER messages, followed by SVINFO and the burst.
61 Upon receiving the SERVER, the initiator will send SVINFO and the burst. If
62 ziplinks are used, SVINFO is the first compressed message.
64 The burst consists of SID and SERVER messages for all known servers, BAN
65 messages for all propagated bans, UID or EUID messages for all known users
66 (possibly followed by ENCAP REALHOST, ENCAP LOGIN and/or AWAY) and SJOIN
67 messages for all known channels (possibly followed by BMASK and/or TB).
71 +D (deaf: does not receive channel messages)
72 +S (network service) (only settable on burst from a services server)
73 +a (appears as server administrator)
74 +i (invisible, see rfc1459)
75 +o (IRC operator, see rfc1459)
76 +w (wallops, see rfc1459) (always propagated for historical reasons)
78 +Q/+R/+g/+l/+s/+z (only locally effective)
79 +Z (ssl user) (only settable on burst)
80 possibly more added by modules
89 +e (ban exception) (capab: EX)
90 +I (invite exception) (capab: IE)
92 +k (key: password required to join, <= 23 ascii chars, no : or , or whitespace)
94 +l (limit: maximum number of members before further joins are disallowed)
97 +n (no external messages)
98 +p (private: does not appear in /whois to non-members, no /knock allowed)
99 +r (only registered users may join) (only if a services server exists) (capab: SERVICES)
101 +t (only chanops may change topic)
106 +f (forward: channel name <= 30 chars)
107 +j (join throttle: N:T with integer N and T)
109 +F (free target for +f)
111 +P (permanent: does not disappear when empty)
112 +Q (ignore forwards to this)
114 +g (allow any member to /invite)
115 +z (send messages blocked by +m to chanops)
118 A server receiving a command that requires nick TS rules must check for a
119 collision between an existing user, and the nick in the received message.
120 (the "new user"). The collisions must obey the rules specified in Nick TS
123 If the TS received is lower than the TS of the existing user the server will
124 collide the existing user if the clients user@host are different, if the
125 clients user@hosts are identical it will collide the new user.
127 If the TS received is equal to the TS of the existing user both clients are
130 If the TS received is higher than the TS of the existing user, the server
131 will collide the existing user if the user@hosts are identical, if the
132 clients user@host are different it will collide the new user and drop the
136 If both users are to be collided, we must issue a KILL for the existing
137 user to all servers. If the new user has a UID then we must also issue a
138 KILL for that UID back to the server sending us data causing the collision.
140 If only the existing user is being collided, we must issue a KILL for the
141 existing user to all servers except the server sending us data. If the
142 existing user has a UID and the server sending us data supports TS6 then
143 we must also issue a KILL for the existing users UID to the server sending
146 If only the new user is being collided, we must issue a KILL for the new user
147 back to the server sending us data if the new user has a UID.
150 A server receiving a command that requires normal channel TS rules must
151 apply the following rules to the command.
153 If the TS received is lower than our TS of the channel a TS6 server must
154 remove status modes (+ov etc) and channel modes (+nt etc). If the
155 originating server is TS6 capable (ie, it has a SID), the server must
156 also remove any ban modes (+b etc). The new modes and statuses are then
159 If any bans are removed, the server must send to non-TS6, directly connected
160 servers mode changes removing the bans after the command is propagated.
161 This prevents desync with banlists, and has to be sent after as clients are
162 still able to send mode changes before the triggering command arrives.
164 If the TS received is equal to our TS of the channel the server should keep
165 its current modes and accept the received modes and statuses.
167 If the TS received is higher than our TS of the channel the server should keep
168 its current modes and ignore the received modes and statuses. Any statuses
169 given in the received message will be removed. A server must mark clients
170 losing their op (+o) status who do not have a UID as 'deopped'. A server must
171 ignore any "MODE" commands from a user marked as 'deopped'.
173 Simple channel TS rules:
175 A server receiving a command that requires simple channel TS rules must
176 apply the following rules to the command.
178 If the TS received is lower, or equal to our TS of the channel the modes are
179 accepted. If the TS received is higher than our TS of the channel the modes
180 are ignored and dropped.
182 Simple channel TS rules do not affect current modes in the channel except
183 for the modes we are accepting.
188 parameters: target, any...
190 The command name should be three decimal ASCII digits.
192 Propagates a "numeric" command reply, such as from a remote WHOIS request.
194 If the first digit is 0 (indicating a reply about the local connection), it
195 should be changed to 1 before propagation or sending to a user.
197 Numerics to the local server may be sent to opers.
199 To avoid infinite loops, servers should not send any replies to numerics.
203 propagation: one-to-one
205 propagation: all servers with -D users on the channel
207 Numerics to channels are broken in some older servers.
213 Remote ADMIN request.
217 propagation: broadcast
218 parameters: opt. away reason
220 If the away reason is empty or not present, mark the user as not away.
221 Otherwise, mark the user as away.
223 Changing away reason from one non-empty string to another non-empty string
224 may not be propagated.
230 propagation: broadcast (restricted)
231 parameters: type, user mask, host mask, creation TS, duration, lifetime, oper, reason
233 Propagates a network wide ban.
235 The type is K for K:lines, R for resvs and X for X:lines; other types are
236 reserved. The user mask field is only used for K:lines; for resvs and X:lines
237 the field is ignored in input and sent as an asterisk.
239 The creation TS indicates when this ban was last modified. An incoming ban MUST
240 be ignored and not propagated if the creation TS is older than the creation TS
241 of the current ban. If the ban is identical, it SHOULD NOT be propagated to
242 avoid unnecessary network traffic. (Two changes to bans that set the TS to the
243 same value may cause desynchronization.)
245 The duration is 0 for an unban and relative to the creation TS for a ban.
246 When the duration has passed, the ban is no longer active but it may still
247 be necessary to remember it.
249 The lifetime is relative to the creation TS and indicates for how long this
250 ban needs to be remembered and propagated. This MUST be at least the duration.
251 Initially, it is usually set the same as the duration but when the ban is
252 modified later, it SHOULD be set such that the modified ban is remembered at
253 least as long as the original ban. This ensures that the original ban does not
254 revive via split servers. This requirement is only a SHOULD to allow for
255 implementations that only inject bans and do not remember any; implementations
256 that remember and propagate bans MUST set the lifetime appropriately.
258 The oper field indicates the oper that originally set the ban. If this message
259 is the initial propagation of a change, it SHOULD be sent as * (an asterisk).
261 The reason field indicates the reason for the ban. Any part after a | (vertical
262 bar) MUST NOT be shown to normal users. The rest of the field and the creation
263 TS and duration MAY be shown to normal users.
267 propagation: broadcast
268 parameters: channelTS, channel, type, space separated masks
270 If the channelTS in the message is greater (newer) than the current TS of
271 the channel, drop the message and do not propagate it.
273 Type is the mode letter of a ban-like mode. In efnet TS6 this is 'b', 'e' or
274 'I'. In charybdis TS6 additionally 'q' is possible.
276 Add all the masks to the given list of the channel.
278 All ban-like modes must be bursted using this command, not using MODE or TMODE.
281 source: unregistered server
283 parameters: space separated capability list
285 Sends capabilities of the server. This must include QS and ENCAP, and for
286 charybdis TS6 also EX and IE. It is also strongly recommended to include EX,
287 CHW, IE and KNOCK, and for charybdis TS6 also SAVE and EUID. For use with
288 services, SERVICES and RSFNC are strongly recommended.
290 The capabilities may depend on the configuration for the server they are sent
296 propagation: broadcast
297 parameters: client, new hostname
299 Changes the visible hostname of a client.
301 Opers are notified unless the source is a server or a service.
305 parameters: server to connect to, port, hunted
307 Remote connect request. A server WALLOPS should be sent by the receiving
310 The port can be 0 for the default port.
316 parameters: duration, mask, reason
318 Sets a D:line (IP ban checked directly after accepting connection).
320 The mask must be an IP address or CIDR mask.
324 parameters: target server mask, subcommand, opt. parameters...
326 Sends a command to matching servers. Propagation is independent of
327 understanding the subcommand.
329 Subcommands are listed elsewhere with "encap only".
332 source: server or unregistered server
334 parameters: error message
336 Reports a (usually fatal) error with the connection.
338 Error messages may contain IP addresses and have a negative effect on server
344 propagation: broadcast
345 parameters: channelTS, channel, topicTS, topic setter, opt. extensions, topic
347 Propagates a channel topic change or propagates a channel topic as part of a
350 If the channel had no topic yet, the channelTS in the message is lower (older)
351 than the current TS of the channel, or the channelTSes are equal and the
352 topicTS in the message is newer than the topicTS of the current topic on the
353 channel, set the topic with topicTS and topic setter, and propagate the
354 message. Otherwise ignore the message and do not propagate it.
356 Unlike a TB message, an ETB message can change the topicTS without changing
357 the topic text. In this case, the message should be propagated to servers but
358 local users should not be notified.
360 Services can send a channelTS of 0 to force restoring an older topic (unless
361 the channel's TS is 0). Therefore, the channelTS should be propagated as given
362 and should not be replaced by the current TS of the channel.
364 An ETB message with a newer channelTS can still set a topic on a channel
365 without topic. This corresponds to SJOIN not clearing the topic when lowering
368 If ETB comes from a user, it can be propagated to non-EOPMOD servers using
369 TOPIC, TB or a combination of TOPIC to clear the topic and TB to set a new
370 topic with topicTS. However, this can be somewhat noisy. On the other hand, if
371 ETB comes from a server, there is no way to force setting a newer topicTS. It
372 is possible to set the topic text but the incorrect topicTS may lead to desync
375 This document does not document the optional extensions between topic setter
380 encap target: single server
384 Remote ETRACE information request.
390 parameters: nickname, hopcount, nickTS, umodes, username, visible hostname, IP address, UID, real hostname, account name, gecos
391 propagation: broadcast
393 Introduces a client. The client is on the source server of this command.
395 The IP address MUST be '0' (a zero) if the true address is not sent such as
396 because of a spoof. Otherwise, and if there is no dynamic spoof (i.e. the
397 visible and real hostname are equal), the IP address MAY be shown to normal
400 The account name is '*' if the user is not logged in with services.
404 EUID is similar to UID but includes the ENCAP REALHOST and ENCAP LOGIN
411 parameters: space separated capability list
413 Capability list of remote server.
419 parameters: user mask, host mask, reason
420 propagation: broadcast
422 Propagates a G:line vote. Once votes from three different opers (based on
423 user@host mask) on three different servers have arrived, trigger the G:line.
424 Pending G:lines expire after some time, usually ten minutes. Triggered G:lines
425 expire after a configured time which may differ across servers.
427 Requests from server connections must be propagated, unless they are found to
428 be syntactically invalid (e.g. '!' in user mask). Therefore, disabling glines
429 must not affect propagation, and too wide glines, double votes and glines that
430 already exist locally must still be propagated.
432 Of course, servers are free to reject gline requests from their own operators.
439 parameters: user mask, host mask, reason
440 propagation: broadcast
442 Propagates a G:line removal vote. Once three votes have arrived (as with
443 G:lines), remove the G:line. Pending G:lines removals expire after some time,
446 Pending G:line removals do not interact with pending G:lines. Triggering a
447 G:line does not affect a pending G:line removal. Triggering a G:line removal
448 does not affect a pending G:line.
458 parameters: target user, channel, opt. channelTS
459 propagation: one-to-one
461 Invites a user to a channel.
463 If the channelTS is greater (newer) than the current TS of the channel, drop
466 Not sending the channelTS parameter is deprecated.
471 parameters: '0' (one ASCII zero)
472 propagation: broadcast
474 Parts the source user from all channels.
478 parameters: channelTS, channel, '+' (a plus sign)
479 propagation: broadcast
481 Joins the source user to the given channel. If the channel does not exist yet,
482 it is created with the given channelTS and no modes. If the channel already
483 exists and has a greater (newer) TS, wipe all simple modes and statuses and
484 change the TS, notifying local users of this but not servers (note that
485 ban-like modes remain intact; invites may or may not be cleared).
487 A JOIN is propagated with the new TS of the channel.
492 propagation: broadcast (restricted)
493 parameters: target server mask, add or delete, server name, oper, reason
495 Adds or removes a jupe for a server. If the server is presently connected,
496 it MUST be SQUIT by the server's uplink when the jupe is applied.
498 The oper field indicates the oper that originally set the jupe. If this message
499 is the initial propagation of a removal, it SHOULD be sent as * (an asterisk).
501 The reason field indicates the reason for the jupe. It SHOULD be displayed
502 as the linking error message to the juped server if it tries to reconnect.
506 parameters: channel, target user, opt. reason
507 propagation: broadcast
509 Kicks the target user from the given channel.
511 Unless the channel's TS is 0, no check is done whether the source user has ops.
513 Not sending the reason parameter is questionable.
517 parameters: target user, path
518 propagation: broadcast
520 Removes the user from the network.
522 The format of the path parameter is some sort of description of the source of
523 the kill followed by a space and a parenthesized reason. To avoid overflow,
524 it is recommended not to add anything to the path.
530 parameters: duration, user mask, host mask, reason
532 Sets a K:line (ban on user@host).
537 parameters: target server mask, duration, user mask, host mask, reason
539 As form 1, deprecated.
545 propagation: broadcast
547 Requests an invite to a channel that is locked somehow (+ikl). Notifies all
548 operators of the channel. (In charybdis, on +g channels all members are
551 This is broadcast so that each server can store when KNOCK was used last on
556 parameters: hunted, server mask
558 Remote LINKS request. The server mask limits which servers are listed.
566 Sends a message to operators (with umode +l set). This is intended to be
567 used for strict subsets of the network.
572 parameters: target server mask, text
574 As form 1, deprecated.
579 parameters: account name
581 In a burst, states that the source user is logged in as the account.
585 parameters: server mask, hunted
587 Remote LUSERS request. Most servers ignore the server mask, treating it as '*'.
591 source: services server
592 parameters: channelTS, channel, mode letters
593 propagation: broadcast (restricted)
595 Propagates a channel mode lock change.
597 If the channelTS is greater (newer) than the current TS of the channel, drop
600 The final parameter is a list of mode letters that may not be changed by local
601 users. This applies to setting or unsetting simple modes, and changing or
602 removing mode parameters.
604 An MLOCK message with no modes disables the MLOCK, therefore the MLOCK message
605 always contains the literal MLOCK for simplicity.
610 parameters: client, umode changes
611 propagation: broadcast
613 Propagates a user mode change. The client parameter must refer to the same user
616 Not all umodes are propagated to other servers.
620 parameters: channel, cmode changes, opt. cmode parameters...
622 Propagates a channel mode change.
624 This is deprecated because the channelTS is not included. If it is received,
625 it should be propagated as TMODE.
636 parameters: new nickname, new nickTS
637 propagation: broadcast
639 Propagates a nick change.
643 parameters: nickname, hopcount, nickTS, umodes, username, hostname, server, gecos
645 Historic TS5 user introduction. The user is on the server indicated by the
646 server parameter; the source server is meaningless (local link).
652 source: services server
653 parameters: duration, nickname
655 If duration is greater than 0, makes the given nickname unavailable for that
658 If duration is 0, removes a nick delay entry for the given nickname.
660 There may or may not be a client with the given nickname; this does not affect
665 parameters: msgtarget, message
667 As PRIVMSG, except NOTICE messages are sent out, server sources are permitted
668 and most error messages are suppressed.
670 Servers may not send '$$', '$#' and opers@server notices. Older servers may
671 not allow servers to send to specific statuses on a channel.
677 parameters: command name, parameters
679 Reports operspy usage.
684 propagation: broadcast
686 Sends a message to operators (with umode +z set).
690 parameters: comma separated channel list, message
692 Parts the source user from the given channels.
695 source: unregistered server
696 parameters: password, 'TS', TS version, SID
698 Sends the server link password, TS version and SID.
702 parameters: origin, opt. destination server
704 Sends a PING to the destination server, which will reply with a PONG. If the
705 destination server parameter is not present, the server receiving the message
708 The origin field is not used in the server protocol. It is sent as the name
709 (not UID/SID) of the source.
711 Remote PINGs are used for end-of-burst detection, therefore all servers must
716 parameters: origin, destination
718 Routes a PONG back to the destination that originally sent the PING.
722 parameters: msgtarget, message
724 Sends a normal message (PRIVMSG) to the given target.
728 propagation: one-to-one
730 propagation: all servers with -D users on the channel
731 (cmode +m/+n should be checked everywhere, bans should not be checked
733 - a status character ('@'/'+') followed by a channel name, to send to users
734 with that status or higher only.
736 propagation: all servers with -D users with appropriate status
737 - '=' followed by a channel name, to send to chanops only, for cmode +z.
738 capab: CHW and EOPMOD
739 propagation: all servers with -D chanops
740 - a user@server message, to send to users on a specific server. The exact
741 meaning of the part before the '@' is not prescribed, except that "opers"
742 allows IRC operators to send to all IRC operators on the server in an
744 propagation: one-to-one
745 - a message to all users on server names matching a mask ('$$' followed by mask)
746 propagation: broadcast
747 Only allowed to IRC operators.
748 - a message to all users with hostnames matching a mask ('$#' followed by mask).
749 Note that this is often implemented poorly.
750 propagation: broadcast
751 Only allowed to IRC operators.
753 In charybdis TS6, services may send to any channel and to statuses on any
759 encap target: single server
763 Remote PRIVS information request.
769 Propagates quitting of a client. No QUIT should be sent for a client that
770 has been removed as result of a KILL message.
777 parameters: real hostname
779 In a burst, propagates the real host of a dynamically-spoofed user.
785 parameters: opt. rehash type
787 Remote REHASH request. If the rehash type is omitted, it is equivalent to
788 a regular /rehash, otherwise it is equivalent to /rehash <rehash type>.
794 parameters: duration, mask, reason
796 Sets a RESV, making a nickname mask or exact channel unavailable.
801 parameters: target server mask, duration, mask, reason
803 As form 1, deprecated.
808 encap target: single server
809 source: services server
810 parameters: target user, new nickname, new nickTS, old nickTS
812 Forces a nickname change and propagates it.
814 The command is ignored if the nick TS of the user is not equal to the old
815 nickTS parameter. If the new nickname already exists (and is not the target
816 user), it is killed first.
824 parameters: source uid, '*', 'S', sasl mechanism name
826 Requests that a SASL agent (a service) initiate the authentication process.
827 The source uid is that of an unregistered client. This is why it is not sent
831 encap target: single server
833 parameters: source uid, target uid, mode, data
835 Part of a SASL authentication exchange. The mode is 'C' to send some data
836 (base64 encoded), or 'D' to end the exchange (data indicates type of
837 termination: 'A' for abort, 'F' for authentication failure, 'S' for
838 authentication success).
843 propagation: broadcast
844 parameters: target uid, TS
846 Resolve a nick collision by changing a nickname to the UID.
848 The server should verify that the UID belongs to a registered user, the user
849 does not already have their UID as their nick and the TS matches the user's
850 nickTS. If not, drop the message.
852 SAVE should be propagated as a regular NICK change to links without SAVE capab.
857 source: unregistered server
858 parameters: server name, hopcount, server description
860 Registers the connection as a server. PASS and CAPAB must have been sent
861 before, SVINFO should be sent afterwards.
863 If there is no such server configured or authentication failed, the connection
866 This is propagated as a SID message.
870 propagation: broadcast
871 parameters: server name, hopcount, server description
873 Introduces a new TS5 server, directly connected to the source of this command.
874 This is only used for jupes as TS5 servers may do little else than existing.
878 propagation: broadcast
879 parameters: server name, hopcount, sid, server description
881 Introduces a new server, directly connected to the source of this command.
885 propagation: broadcast
886 parameters: new nickname, new username, new visible hostname, new nickTS, new login name
888 Broadcasts a change of several user parameters at once.
890 Currently only sent after an SVSLOGIN.
894 propagation: broadcast
895 parameters: channelTS, channel, simple modes, opt. mode parameters..., nicklist
897 Broadcasts a channel creation or bursts a channel.
899 The nicklist consists of users joining the channel, with status prefixes for
900 their status ('@+', '@', '+' or ''), for example:
901 '@+1JJAAAAAB +2JJAAAA4C 1JJAAAADS'. All users must be behind the source server
902 so it is not possible to use this message to force users to join a channel.
904 The interpretation depends on the channelTS and the current TS of the channel.
905 If either is 0, set the channel's TS to 0 and accept all modes. Otherwise, if
906 the incoming channelTS is greater (newer), ignore the incoming simple modes
907 and statuses and join and propagate just the users. If the incoming channelTS
908 is lower (older), wipe all modes and change the TS, notifying local users of
909 this but not servers (invites may be cleared). In the latter case, kick on
910 split riding may happen: if the key (+k) differs or the incoming simple modes
911 include +i, kick all local users, sending KICK messages to servers.
913 An SJOIN is propagated with the new TS and modes of the channel. The statuses
914 are propagated if and only if they were accepted.
916 SJOIN must be used to propagate channel creation and in netbursts. For regular
917 users joining channels, JOIN must be used. Pseudoservers may use SJOIN to join
924 parameters: snomask letter, text
926 Sends the text as a server notice from the source server to opers with the
930 parameters: target server, comment
932 Removes the target server and all servers and users behind it from the network.
934 If the target server is the receiving server or the local link this came from,
935 this is an announcement that the link is being closed.
937 Otherwise, if the target server is locally connected, the server should send
938 a WALLOPS announcing the SQUIT.
942 parameters: stats letter, hunted
944 Remote STATS request. Privileges are checked on the server executing the
950 source: services server
951 parameters: target user, new login name (optional)
953 If the new login name is not present or empty, mark the target user as not
954 logged in, otherwise mark the target user as logged in as the given account.
959 parameters: current TS version, minimum TS version, '0', current time
961 Verifies TS protocol compatibility and clock. If anything is not in order,
964 The current TS version is the highest version supported by the source server
965 and the minimum TS version is the lowest version supported.
967 The current time is sent as a TS in the usual way.
972 encap target: single server
973 source: services server
974 parameters: target, new nick, new username, new visible hostname, new login name
976 Sent after successful SASL authentication.
978 The target is a UID, typically an unregistered one.
980 Any of the "new" parameters can be '*' to leave the corresponding field
981 unchanged. The new login name can be '0' to log the user out.
983 If the UID is registered on the network, a SIGNON with the changes will be
984 broadcast, otherwise the changes will be stored, to be used when registration
990 propagation: broadcast
991 parameters: channel, topicTS, opt. topic setter, topic
993 Propagates a channel topic as part of a burst.
995 If the channel had no topic yet or the topicTS in the message is older than
996 the topicTS of the current topic on the channel and the topics differ, set
997 the topic with topicTS and topic setter, and propagate the message. Otherwise
998 ignore the message and do not propagate it.
1000 If the topic setter is not present, use a server name instead.
1006 Remote TIME request.
1010 parameters: channelTS, channel, cmode changes, opt. cmode parameters...
1012 Propagates a channel mode change.
1014 If the channelTS is greater (newer) than the current TS of the channel, drop
1017 On input, only the limit on parameters per line restricts how many cmode
1018 parameters can be present. Apart from this, arbitrary modes shall be
1019 processed. Redundant modes may be dropped. For example, +n-n may be applied and
1020 propagated as +n-n, -n or (if the channel was already -n) nothing, but not as
1023 The parameter for mode -k (removing a key) shall be ignored.
1025 On output, at most ten cmode parameters should be sent; if there are more,
1026 multiple TMODE messages should be sent.
1030 propagation: broadcast
1031 parameters: channel, topic
1033 Propagates a channel topic change. The server may verify that the source has
1036 The topicTS shall be set to the current time and the topic setter shall be
1037 set indicating the source user. Note that this means that the topicTS of a
1038 topic set with TOPIC is not necessarily consistent across the network.
1045 Performs a trace to the target, sending 200 numerics from each server passing
1046 the message on. The target server sends a description of the target followed
1049 TRACE, STATS l and STATS L are the only commands using hunt_server that use the
1050 hunted parameter for more than just determining which server the command
1051 should be executed on.
1054 parameters: target name, hunted
1056 Executes a trace command on the target server. No 200 numerics are sent.
1057 The target name is a name, not a UID, and should be on the target server.
1061 propagation: broadcast
1062 parameters: nickname, hopcount, nickTS, umodes, username, visible hostname, IP address, UID, gecos
1063 propagation: broadcast
1065 Introduces a client. The client is on the source server of this command.
1067 The IP address MUST be '0' (a zero) if the true address is not sent such as
1068 because of a spoof. Otherwise, and if there is no dynamic spoof (ENCAP
1069 REALHOST, charybdis TS6 only), the IP address MAY be shown to normal users.
1071 Nick TS rules apply.
1079 Removes a D:line (IP ban checked directly after accepting connection).
1081 The mask must be an IP address or CIDR mask.
1087 parameters: user mask, host mask
1089 Removes a K:line (ban on user@host).
1094 parameters: target server mask, user mask, host mask
1096 As form 1, deprecated.
1109 parameters: target server mask, mask
1111 As form 1, deprecated.
1119 Removes an X:line (ban on realname).
1124 parameters: target server mask, mask
1126 As form 1, deprecated.
1132 Remote USERS request.
1138 Remote VERSION request.
1144 propagation: broadcast
1146 In efnet TS6, sends a message to operators (with umode +z set). This is a
1147 deprecated equivalent to OPERWALL.
1149 In charybdis TS6, sends a message to local users with umode +w set (or possibly
1150 another indication that WALLOPS messages should be sent), including non-opers.
1155 propagation: broadcast
1157 Sends a message to local users with umode +w set (or possibly another
1158 indication that WALLOPS messages should be sent).
1160 In efnet TS6 this may include non-opers, in charybdis TS6 this may only be
1165 parameters: hunted, target nick
1167 Remote WHOIS request.
1171 parameters: nickname, limit, hunted
1173 Remote WHOWAS request. Not implemented in all servers.
1175 Different from a local WHOWAS request, the limit is mandatory and servers should
1176 apply a maximum to it.
1182 parameters: duration, mask, reason
1184 Sets an X:line (ban on realname).
1189 parameters: target server mask, duration, mask, reason
1191 As form 1, deprecated.
1193 Local only commands (charybdis 3.1):