#!/bin/sh
# MetaCard 2.4 stack
# The following is not ASCII text,
# so now would be a good time to q out of more
exec mc $0 "$@"
IRC 1 F bd U Lucida Grande U Monaco U Monaco cREVGeometryCache stackID 1037 cREVGeneral
bookmarks
debugObjects handlerList scriptSelection char 1 to 0 prevHandler tempScript script @ d cREVGeometryCacheIDs 1064164370789 10291064164356884 10281064163717875 10251063851621046 10051063851809058 10091064164379049 10301064164777974 10351064163471386 10241063926365621 10141063927935257 10201063851809028 10081064164754411 10331064164764608 10341063851593006 10031063927932637 10191064164786232 10361063926416006 10161064164343687 10271064164794290 10371063853177167 10101063930624701 10211064164012615 10261063892232505 1013 cREVGeometrycache total 23order 1063926365621
nick i` l cREVGeneral revUniqueID
1063851593006
#Xdcc.com Send custom Ep on mouseUp
repeat for each line theLine in field "command"
put theLine & crlf after output
end repeat
write output to socket field "server"
end mouseUp
L R cREVGeneral scriptChecksum $bݸb -+
handlerList mouseUp breakPoints scriptSelection
char 97 to 96 revUniqueID
1063851621046
bookmarks tempScript prevHandler mouseUpscript on mouseUp
repeat for each line theLine in field "command"
put theLine & crlf after output
end repeat
write output to socket field "server"
end mouseUp
server i` cREVGeneral revUniqueID
1063851809028 efnet.demon.co.uk:6666
Field 1 d cREVGeneral revUniqueID
1063851809058 Server: close Ep on mouseUp
write "QUIT :I am finished" & crlf to socket field "server"
close socket field "server"
put "closed socket" &comma& the result & comma & the opensockets & return before field "log"
end mouseUp
R cREVGeneral scriptChecksum B@,ӏ$ revUniqueID
1063853177167
bookmarks handlerList mouseUp tempScript prevHandler mouseUpscriptSelection char 125 to 124script aon mouseUp
write "QUIT :I am finished" & crlf to socket field "server"
close socket field "server"
put "closed socket" &comma& the result & comma & the opensockets & return before field "log"
end mouseUp
Read Epon mouseUp
read from socket field "server" until crlf with message "finished"
end mouseUp
on finished theHost theMessage
if theMessage is not empty then
put theMessage & return before field "log"
if word one of theMessage = "PING" then
write "PONG Bjoernke" & crlf to socket field "server"
put "PONG Bjoernke" & return before field "log"
end if
end if
read from socket field "server" until crlf with message "finished"
end finished
3 R cREVGeneral scriptChecksum pB }ft
bookmarks revUniqueID
1063892232505 handlerList mouseUp
finishedscriptSelection char 386 to 385 prevHandler mouseUp tempScript script on mouseUp
read from socket field "server" until crlf with message "finished"
end mouseUp
on finished theHost theMessage
if theMessage is not empty then
put theMessage & return before field "log"
if word one of theMessage = "PING" then
write "PONG Bjoernke" & crlf to socket field "server"
put "PONG Bjoernke" & return before field "log"
end if
end if
read from socket field "server" until crlf with message "finished"
end finished
log )` [
cREVGeometry Master,movevDistance falseMaster,scalebottomDistance -6Master,expectedRect
4,166,358,370 Master,scaleBottomObjectSide BottomMaster,movehDistance falseMaster trueMaster,scaleRightAbsolute trueMaster,scaleRight true Master,scaleBottomObjectRef cardMaster,scalerightDistance -5 Master,scaleRightObjectSide RightMaster,scaleRightObjectRef cardMaster,scaleBottomAbsolute trueMaster,cardRanking 2Master,scaleBottom trueMaster,scaletopDistance Master,scaleleftDistance cREVGeneral revUniqueID
1063926365621 Click "Connect" to open a socket, then click "Read" (only neccessary once) and finally use the "custon command" button to login. CJoin a channel using the Drop down, send messages in the same way. READ THE RFC OR BE CONFUSED!!! JI advise to not use the LIST command, it generates much too much traffic. ` N connect Epon mouseUp
open socket to field "server"
--write "NICK" && field "nick" && crlf to socket field "server"
--write "PASS" && "PROT" & crlf to socket field "server"
--write "USER" && field "nick" && "bvg.kicks-ass.org localhost" && colon & field "user" & crlf to socket field "server"
--read from socket field "server" until crlf
--put it &comma& the result & comma & the opensockets
beep
end mouseUp
R cREVGeneral scriptChecksum P5߁! nnJKR breakPoints handlerList mouseUpscriptSelection
char 48 to 47
bookmarks revUniqueID
1063926416006 prevHandler mouseUp tempScript script eon mouseUp
open socket to field "server"
--write "NICK" && field "nick" && crlf to socket field "server"
--write "PASS" && "PROT" & crlf to socket field "server"
--write "USER" && field "nick" && "bvg.kicks-ass.org localhost" && colon & field "user" & crlf to socket field "server"
--read from socket field "server" until crlf
--put it &comma& the result & comma & the opensockets
beep
end mouseUp
command i` @ 2 cREVGeneral revUniqueID
1063927932637 PASS 0 NICK Bjoernke )USER Bjoernke 0 bar :Bjoernke von Gierke
Field 1 , z cREVGeneral revUniqueID
1063927935257 Custom Command: Send Ep kon mouseUp
write the label of button "nick" && field "nick" & crlf to socket field "server"
end mouseUp
R cREVGeneral scriptChecksum 9npM7Blv breakPoints handlerList mouseUpscriptSelection
char 45 to 44
bookmarks revUniqueID
1063930624701 prevHandler mouseUp tempScript script 9on mouseUp
write the label of button "nick" && field "nick" & crlf to socket field "server"
end mouseUp
Nick e b JOIN JOIN
PRIVMSG
PART cREVGeneral revUniqueID
1064163471386
Field 1 z cREVGeneral revUniqueID
1064163717875 Log: Show RFC p 9on mouseUp
go to stack "RFC" as modeless
end mouseUp
d R cREVGeneral scriptChecksum T;?ZcPJ=
bookmarks revUniqueID
1064164012615 handlerList mouseUpscriptSelection
char 44 to 43 prevHandler tempScript script on mouseUp
go to stack "RFC" as modeless
end mouseUp
Graphic 1 KF X _ cREVGeneral revUniqueID
1064164343687
Graphic 2 KF } ~ ~ cREVGeneral revUniqueID
1064164356884
Graphic 3 KF b u c cREVGeneral revUniqueID
1064164370789
Graphic 4 KF a ` X b b cREVGeneral revUniqueID
1064164379049
Graphic 5 KF q r ~ cREVGeneral revUniqueID
1064164754411
Graphic 6 KF } ` ~X ~ cREVGeneral revUniqueID
1064164764608
Graphic 7 KF / 0 0 cREVGeneral revUniqueID
1064164777974
Graphic 8 KF / 0 J cREVGeneral revUniqueID
1064164786232
Graphic 9 KF I ^ JZ J cREVGeneral revUniqueID
1064164794290 RFC 1 b cREVGeometryCache stackID 1006 @ cREVGeometryCacheIDs 1064157530754 10051064157540788 10061064157373724 1003 cREVGeometrycache total 3order *1064157373724
1064157530754
1064157540788
rfc )` l
cREVGeometry Master,scaleBottomObjectSide BottomMaster,movehDistance falseMaster trueMaster,scaleTopObjectRef cardMaster,scaleLeftObjectRef card Master,scaleBottomObjectRef cardMaster,scaleBottomAbsolute trueMaster,scaleBottom trueMaster,scaleTopObjectSide TopMaster,scaleLeftObjectSide LeftMaster,expectedRect 4,4,398,398Master,scalebottomDistance -26Master,movevDistance falseMaster,scaleRightAbsolute trueMaster,scaleRight trueMaster,scalerightDistance -2Master,scaleTopAbsolute trueMaster,scaleLeftAbsolute trueMaster,scaleRightObjectRef card Master,scaleRightObjectSide RightMaster,scaleTop trueMaster,scaleLeft trueMaster,cardRanking 4Master,scaleleftDistance 4Master,scaletopDistance 4 cREVGeneral revUniqueID
1064157373724 INetwork Working Group C. Kalt IRequest for Comments: 2812 April 2000 Updates: 1459 Category: Informational 7 Internet Relay Chat: Client Protocol Status of this Memo G This memo provides information for the Internet community. It does G not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice D Copyright (C) The Internet Society (2000). All Rights Reserved. IESG NOTE: I The IRC protocol itself enables several possibilities of transferring F data between clients, and just like with other transfer mechanisms H like email, the receiver of the data has to be careful about how the I data is handled. For more information on security issues with the IRC G protocol, see for example http://www.irchelp.org/irchelp/security/. Abstract E The IRC (Internet Relay Chat) protocol is for use with text based I conferencing; the simplest client being any socket program capable of connecting to the server. C This document defines the Client Protocol, and assumes that the < reader is familiar with the IRC Architecture [IRC-ARCH]. Table of Contents H 1. Labels ..................................................... 3 H 1.1 Servers ................................................ 3 H 1.2 Clients ................................................ 3 H 1.2.1 Users ............................................. 4 H 1.2.1.1 Operators .................................... 4 H 1.2.2 Services .......................................... 4 H 1.3 Channels ............................................... 4 H 2. The IRC Client Specification ............................... 5 H 2.1 Overview ............................................... 5 H 2.2 Character codes ........................................ 5 H 2.3 Messages ............................................... 5 IKalt Informational [Page 1] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 H 2.3.1 Message format in Augmented BNF ................... 6 H 2.4 Numeric replies ........................................ 8 H 2.5 Wildcard expressions ................................... 9 H 3. Message Details ............................................ 9 H 3.1 Connection Registration ................................ 10 H 3.1.1 Password message .................................. 10 H 3.1.2 Nick message ...................................... 10 H 3.1.3 User message ...................................... 11 H 3.1.4 Oper message ...................................... 12 H 3.1.5 User mode message ................................. 12 H 3.1.6 Service message ................................... 13 H 3.1.7 Quit .............................................. 14 H 3.1.8 Squit ............................................. 15 H 3.2 Channel operations ..................................... 15 H 3.2.1 Join message ...................................... 16 H 3.2.2 Part message ...................................... 17 H 3.2.3 Channel mode message .............................. 18 H 3.2.4 Topic message ..................................... 19 H 3.2.5 Names message ..................................... 20 H 3.2.6 List message ...................................... 21 H 3.2.7 Invite message .................................... 21 H 3.2.8 Kick command ...................................... 22 H 3.3 Sending messages ....................................... 23 H 3.3.1 Private messages .................................. 23 H 3.3.2 Notice ............................................ 24 H 3.4 Server queries and commands ............................ 25 H 3.4.1 Motd message ...................................... 25 H 3.4.2 Lusers message .................................... 25 H 3.4.3 Version message ................................... 26 H 3.4.4 Stats message ..................................... 26 H 3.4.5 Links message ..................................... 27 H 3.4.6 Time message ...................................... 28 H 3.4.7 Connect message ................................... 28 H 3.4.8 Trace message ..................................... 29 H 3.4.9 Admin command ..................................... 30 H 3.4.10 Info command ...................................... 31 H 3.5 Service Query and Commands ............................. 31 H 3.5.1 Servlist message .................................. 31 H 3.5.2 Squery ............................................ 32 H 3.6 User based queries ..................................... 32 H 3.6.1 Who query ......................................... 32 H 3.6.2 Whois query ....................................... 33 H 3.6.3 Whowas ............................................ 34 H 3.7 Miscellaneous messages ................................. 34 H 3.7.1 Kill message ...................................... 35 H 3.7.2 Ping message ...................................... 36 H 3.7.3 Pong message ...................................... 37 H 3.7.4 Error ............................................. 37 IKalt Informational [Page 2] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 H 4. Optional features .......................................... 38 H 4.1 Away ................................................... 38 H 4.2 Rehash message ......................................... 39 H 4.3 Die message ............................................ 39 H 4.4 Restart message ........................................ 40 H 4.5 Summon message ......................................... 40 H 4.6 Users .................................................. 41 H 4.7 Operwall message ....................................... 41 H 4.8 Userhost message ....................................... 42 H 4.9 Ison message ........................................... 42 H 5. Replies .................................................... 43 H 5.1 Command responses ...................................... 43 H 5.2 Error Replies .......................................... 53 H 5.3 Reserved numerics ...................................... 59 H 6. Current implementations .................................... 60 H 7. Current problems ........................................... 60 H 7.1 Nicknames .............................................. 60 H 7.2 Limitation of wildcards ................................ 61 H 7.3 Security considerations ................................ 61 H 8. Current support and availability ........................... 61 H 9. Acknowledgements ........................................... 61 H 10. References ................................................ 62 H 11. Author's Address .......................................... 62 H 12. Full Copyright Statement .................................. 63
1. Labels H This section defines the identifiers used for the various components of the IRC protocol. 1.1 Servers F Servers are uniquely identified by their name, which has a maximum D length of sixty three (63) characters. See the protocol grammar F rules (section 2.3.1) for what may and may not be used in a server name. 1.2 Clients F For each client all servers MUST have the following information: a B netwide unique identifier (whose format depends on the type of 7 client) and the server which introduced the client. IKalt Informational [Page 3] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 1.2.1 Users D Each user is distinguished from other users by a unique nickname E having a maximum length of nine (9) characters. See the protocol G grammar rules (section 2.3.1) for what may and may not be used in a
nickname. C While the maximum length is limited to nine characters, clients B SHOULD accept longer strings as they may become used in future evolutions of the protocol. 1.2.1.1 Operators C To allow a reasonable amount of order to be kept within the IRC G network, a special class of users (operators) is allowed to perform F general maintenance functions on the network. Although the powers E granted to an operator can be considered as 'dangerous', they are E nonetheless often necessary. Operators SHOULD be able to perform I basic network tasks such as disconnecting and reconnecting servers as G needed. In recognition of this need, the protocol discussed herein E provides for operators only to be able to perform such functions. 3 See sections 3.1.8 (SQUIT) and 3.4.7 (CONNECT). F A more controversial power of operators is the ability to remove a H user from the connected network by 'force', i.e., operators are able ? to close the connection between any client and server. The C justification for this is very delicate since its abuse is both H destructive and annoying, and its benefits close to inexistent. For E further details on this type of action, see section 3.7.1 (KILL). 1.2.2 Services G Each service is distinguished from other services by a service name I composed of a nickname and a server name. As for users, the nickname B has a maximum length of nine (9) characters. See the protocol G grammar rules (section 2.3.1) for what may and may not be used in a
nickname.
1.3 Channels E Channels names are strings (beginning with a '&', '#', '+' or '!' E character) of length up to fifty (50) characters. Apart from the H requirement that the first character is either '&', '#', '+' or '!', G the only restriction on a channel name is that it SHALL NOT contain H any spaces (' '), a control G (^G or ASCII 7), a comma (','). Space E is used as parameter separator and command is used as a list item D separator by the protocol). A colon (':') can also be used as a H delimiter for the channel mask. Channel names are case insensitive. IKalt Informational [Page 4] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 G See the protocol grammar rules (section 2.3.1) for the exact syntax of a channel name. G Each prefix characterizes a different channel type. The definition F of the channel types is not relevant to the client-server protocol G and thus it is beyond the scope of this document. More details can E be found in "Internet Relay Chat: Channel Management" [IRC-CHAN]. 2. The IRC Client Specification
2.1 Overview C The protocol as described herein is for use only with client to ; server connections when the client registers as a user. 2.2 Character codes F No specific character set is specified. The protocol is based on a C set of codes which are composed of eight (8) bits, making up an G octet. Each message may be composed of any number of these octets; G however, some octet values are used for control codes, which act as message delimiters. F Regardless of being an 8-bit protocol, the delimiters and keywords H are such that protocol is mostly usable from US-ASCII terminal and a telnet connection. A Because of IRC's Scandinavian origin, the characters {}|^ are G considered to be the lower case equivalents of the characters []\~, ? respectively. This is a critical issue when determining the 2 equivalence of two nicknames or channel names.
2.3 Messages F Servers and clients send each other messages, which may or may not B generate a reply. If the message contains a valid command, as D described in later sections, the client should expect a reply as I specified but it is not advised to wait forever for the reply; client ? to server and server to server communication is essentially asynchronous by nature. F Each IRC message may consist of up to three main parts: the prefix C (OPTIONAL), the command, and the command parameters (maximum of I fifteen (15)). The prefix, command, and all parameters are separated - by one ASCII space character (0x20) each. IKalt Informational [Page 5] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 E The presence of a prefix is indicated with a single leading ASCII I colon character (':', 0x3b), which MUST be the first character of the H message itself. There MUST be NO gap (whitespace) between the colon G and the prefix. The prefix is used by servers to indicate the true I origin of the message. If the prefix is missing from the message, it G is assumed to have originated from the connection from which it was B received from. Clients SHOULD NOT use a prefix when sending a E message; if they use one, the only valid prefix is the registered ( nickname associated with the client. G The command MUST either be a valid IRC command or a three (3) digit % number represented in ASCII text. G IRC messages are always lines of characters terminated with a CR-LF D (Carriage Return - Line Feed) pair, and these messages SHALL NOT F exceed 512 characters in length, counting all characters including F the trailing CR-LF. Thus, there are 510 characters maximum allowed B for the command and its parameters. There is no provision for H continuation of message lines. See section 6 for more details about current implementations. &2.3.1 Message format in Augmented BNF I The protocol messages must be extracted from the contiguous stream of H octets. The current solution is to designate two characters, CR and D LF, as message separators. Empty messages are silently ignored, D which permits use of the sequence CR-LF between messages without extra problems. A The extracted message is parsed into the components , 0 and list of parameters (). 2 The Augmented BNF representation for this is: ? message = [ ":" prefix SPACE ] command [ params ] crlf F prefix = servername / ( nickname [ [ "!" user ] "@" host ] ) $ command = 1*letter / 3digit = params = *14( SPACE middle ) [ SPACE ":" trailing ] @ =/ 14( SPACE middle ) [ SPACE [ ":" ] trailing ] B nospcrlfcl = %x01-09 / %x0B-0C / %x0E-1F / %x21-39 / %x3B-FF @ ; any octet except NUL, CR, LF, " " and ":" 3 middle = nospcrlfcl *( ":" / nospcrlfcl ) . trailing = *( ":" / " " / nospcrlfcl ) 0 SPACE = %x20 ; space character = crlf = %x0D %x0A ; "carriage return" "linefeed" IKalt Informational [Page 6] IRFC 2812 Internet Relay Chat: Client Protocol April 2000
NOTES: G 1) After extracting the parameter list, all parameters are equal I whether matched by or . is just a > syntactic trick to allow SPACE within the parameter. I 2) The NUL (%x00) character is not special in message framing, and G basically could end up inside a parameter, but it would cause H extra complexities in normal C string handling. Therefore, NUL ) is not allowed within messages. F Most protocol messages specify additional semantics and syntax for E the extracted parameter strings dictated by their position in the G list. For example, many server commands will assume that the first D parameter after the command is the list of targets, which can be described with: " target = nickname / server % msgtarget = msgto *( "," msgto ) ? msgto = channel / ( user [ "%" host ] "@" servername ) / msgto =/ ( user "%" host ) / targetmask : msgto =/ nickname / ( nickname "!" user "@" host ) C channel = ( "#" / "+" / ( "!" channelid ) / "&" ) chanstring # [ ":" chanstring ] servername = hostname $ host = hostname / hostaddr - hostname = shortname *( "." shortname ) = shortname = ( letter / digit ) *( letter / digit / "-" ) $ *( letter / digit ) 5 ; as specified in RFC 1123 [HNAME] " hostaddr = ip4addr / ip6addr @ ip4addr = 1*3digit "." 1*3digit "." 1*3digit "." 1*3digit / ip6addr = 1*hexdigit 7( ":" 1*hexdigit ) : ip6addr =/ "0:0:0:0:0:" ( "0" / "FFFF" ) ":" ip4addr J nickname = ( letter / special ) *8( letter / digit / special / "-" ) # targetmask = ( "$" / "#" ) mask B ; see details on allowed masks in section 3.3.1 @ chanstring = %x01-07 / %x08-09 / %x0B-0C / %x0E-1F / %x21-2B " chanstring =/ %x2D-39 / %x3B-FF I ; any octet except NUL, BELL, CR, LF, " ", "," and ":" 7 channelid = 5( %x41-5A / digit ) ; 5( A-Z / 0-9 ) IKalt Informational [Page 7] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 Other parameter syntaxes are: F user = 1*( %x01-09 / %x0B-0C / %x0E-1F / %x21-3F / %x41-FF ) > ; any octet except NUL, CR, LF, " " and "@" E key = 1*23( %x01-05 / %x07-08 / %x0C / %x0E-1F / %x21-7F ) 2 ; any 7-bit US_ASCII character, > ; except NUL, CR, LF, FF, h/v TABs, and " " 4 letter = %x41-5A / %x61-7A ; A-Z / a-z . digit = %x30-39 ; 0-9 : hexdigit = digit / "A" / "B" / "C" / "D" / "E" / "F" " special = %x5B-60 / %x7B-7D A ; "[", "]", "\", "`", "_", "^", "{", "|", "}" NOTES: E 1) The syntax is given here for the sole purpose of A indicating the format to follow for IP addresses. This F reflects the fact that the only available implementations of I this protocol uses TCP/IP as underlying network protocol but is : not meant to prevent other protocols to be used. F 2) has a maximum length of 63 characters. This is a > limitation of the protocol as internet hostnames (in C particular) can be longer. Such restriction is necessary G because IRC messages are limited to 512 characters in length. E Clients connecting from a host which name is longer than 63 D characters are registered using the host (numeric) address # instead of the host name. @ 3) Some parameters used in the following sections of this E documents are not defined here as there is nothing specific C about them besides the name that is used for convenience. @ These parameters follow the general syntax defined for . 2.4 Numeric replies D Most of the messages sent to the server generate a reply of some D sort. The most common reply is the numeric reply, used for both E errors and normal replies. The numeric reply MUST be sent as one I message consisting of the sender prefix, the three-digit numeric, and I the target of the reply. A numeric reply is not allowed to originate H from a client. In all other respects, a numeric reply is just like a C normal message, except that the keyword is made up of 3 numeric H digits rather than a string of letters. A list of different replies ' is supplied in section 5 (Replies). IKalt Informational [Page 8] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 2.5 Wildcard expressions G When wildcards are allowed in a string, it is referred as a "mask". D For string matching purposes, the protocol allows the use of two G special characters: '?' (%x3F) to match one and only one character, D and '*' (%x2A) to match any number of any characters. These two = characters can be escaped using the character '\' (%x5C). ) The Augmented BNF syntax for this is: ? mask = *( nowild / noesc wildone / noesc wildmany ) wildone = %x3F wildmany = %x2A . nowild = %x01-29 / %x2B-3E / %x40-FF 5 ; any octet except NUL, "*", "?" $ noesc = %x01-5B / %x5D-FF 3 ; any octet except NUL and "\" matchone = %x01-FF & ; matches wildone matchmany = *matchone ' ; matches wildmany
Examples: G a?c ; Matches any string of 3 characters in length starting , with "a" and ending with "c" G a*c ; Matches any string of at least 2 characters in length 5 starting with "a" and ending with "c" 3. Message Details A On the following pages there are descriptions of each message G recognized by the IRC server and client. All commands described in E this section MUST be implemented by any server for this protocol. C Where the reply ERR_NOSUCHSERVER is returned, it means that the G target of the message could not be found. The server MUST NOT send 8 any other replies after this error for that command. F The server to which a client is connected is required to parse the 8 complete message, and return any appropriate errors. F If multiple parameters is presented, then each MUST be checked for G validity and appropriate responses MUST be sent back to the client. D In the case of incorrect messages which use parameter lists with C comma as an item separator, a reply MUST be sent for each item. IKalt Informational [Page 9] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 3.1 Connection Registration I The commands described here are used to register a connection with an < IRC server as a user as well as to correctly disconnect. B A "PASS" command is not required for a client connection to be ? registered, but it MUST precede the latter of the NICK/USER E combination (for a user connection) or the SERVICE command (for a G service connection). The RECOMMENDED order for a client to register is as follows: + 1. Pass message > 2. Nick message 2. Service message 3. User message G Upon success, the client will receive an RPL_WELCOME (for users) or ? RPL_YOURESERVICE (for services) message indicating that the I connection is now registered and known the to the entire IRC network. H The reply message MUST contain the full client identifier upon which it was registered. 3.1.1 Password message Command: PASS Parameters: A The PASS command is used to set a 'connection password'. The H optional password can and MUST be set before any attempt to register E the connection is made. Currently this requires that user send a : PASS command before sending the NICK/USER combination. Numeric Replies: @ ERR_NEEDMOREPARAMS ERR_ALREADYREGISTRED Example: # PASS secretpasswordhere 3.1.2 Nick message Command: NICK Parameters: G NICK command is used to give user a nickname or change the existing one. IKalt Informational [Page 10] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 Numeric Replies: @ ERR_NONICKNAMEGIVEN ERR_ERRONEUSNICKNAME = ERR_NICKNAMEINUSE ERR_NICKCOLLISION : ERR_UNAVAILRESOURCE ERR_RESTRICTED
Examples: F NICK Wiz ; Introducing new nick "Wiz" if session is D still unregistered, or user changing his - nickname to "Wiz" ' :WiZ!jto@tolsun.oulu.fi NICK Kilroy A ; Server telling that WiZ changed his / nickname to Kilroy. 3.1.3 User message Command: USER 1 Parameters: F The USER command is used at the beginning of connection to specify 6 the username, hostname and realname of a new user. @ The parameter should be a numeric, and can be used to H automatically set user modes when registering with the server. This I parameter is a bitmask, with only 2 bits having any signification: if G the bit 2 is set, the user mode 'w' will be set and if the bit 3 is A set, the user mode 'i' will be set. (See Section 3.1.5 "User Modes"). 0 The may contain space characters. Numeric Replies: @ ERR_NEEDMOREPARAMS ERR_ALREADYREGISTRED Example: H USER guest 0 * :Ronnie Reagan ; User registering themselves with a E username of "guest" and real name 4 "Ronnie Reagan". H USER guest 8 * :Ronnie Reagan ; User registering themselves with a E username of "guest" and real name I "Ronnie Reagan", and asking to be set . invisible. IKalt Informational [Page 11] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 3.1.4 Oper message Command: OPER ! Parameters: F A normal user uses the OPER command to obtain operator privileges. A The combination of and are REQUIRED to gain D Operator privileges. Upon success, the user will receive a MODE > message (see section 3.1.5) indicating the new user modes. Numeric Replies: 9 ERR_NEEDMOREPARAMS RPL_YOUREOPER > ERR_NOOPERHOST ERR_PASSWDMISMATCH Example: H OPER foo bar ; Attempt to register as an operator G using a username of "foo" and "bar" 4 as the password. 3.1.5 User mode message Command: MODE Parameters: C *( ( "+" / "-" ) *( "i" / "w" / "o" / "O" / "r" ) ) E The user MODE's are typically changes which affect either how the I client is seen by others or what 'extra' messages the client is sent. G A user MODE command MUST only be accepted if both the sender of the H message and the nickname given as a parameter are both the same. If H no other parameter is given, then the server will return the current settings for the nick. * The available modes are as follows: ( a - user is flagged as away; + i - marks a users as invisible; & w - user receives wallops; + r - restricted user connection; o - operator flag; $ O - local operator flag; ; s - marks a user for receipt of server notices. / Additional modes may be available later on. IKalt Informational [Page 12] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 I The flag 'a' SHALL NOT be toggled by the user using the MODE command, 0 instead use of the AWAY command is REQUIRED. G If a user attempts to make themselves an operator using the "+o" or F "+O" flag, the attempt SHOULD be ignored as users could bypass the ? authentication mechanisms of the OPER command. There is no H restriction, however, on anyone `deopping' themselves (using "-o" or
"-O"). I On the other hand, if a user attempts to make themselves unrestricted D using the "-r" flag, the attempt SHOULD be ignored. There is no G restriction, however, on anyone `deopping' themselves (using "+r"). @ This flag is typically set by the server upon connection for G administrative reasons. While the restrictions imposed are left up F to the implementation, it is typical that a restricted user not be E allowed to change nicknames, nor make use of the channel operator status on channels. 3 The flag 's' is obsolete but MAY still be used. Numeric Replies: > ERR_NEEDMOREPARAMS ERR_USERSDONTMATCH 7 ERR_UMODEUNKNOWNFLAG RPL_UMODEIS
Examples: @ MODE WiZ -w ; Command by WiZ to turn off B reception of WALLOPS messages. H MODE Angel +i ; Command from Angel to make herself . invisible. G MODE WiZ -o ; WiZ 'deopping' (removing operator , status). 3.1.6 Service message Command: SERVICE ; Parameters: ! F The SERVICE command to register a new service. Command parameters F specify the service nickname, distribution, type and info of a new service. IKalt Informational [Page 13] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 G The parameter is used to specify the visibility of a H service. The service may only be known to servers which have a name G matching the distribution. For a matching server to have knowledge G of the service, the network path between that server and the server G on which the service is connected MUST be composed of servers which names all match the mask. @ The parameter is currently reserved for future usage. Numeric Replies: > ERR_ALREADYREGISTRED ERR_NEEDMOREPARAMS ERR_ERRONEUSNICKNAME 8 RPL_YOURESERVICE RPL_YOURHOST RPL_MYINFO Example: D SERVICE dict * *.fr 0 0 :French Dictionary ; Service registering G itself with a name of "dict". This E service will only be available on F servers which name matches "*.fr". 3.1.7 Quit Command: QUIT " Parameters: [ ] C A client session is terminated with a quit message. The server @ acknowledges this by sending an ERROR message to the client. Numeric Replies: None. Example: ? QUIT :Gone to have lunch ; Preferred message format. E :syrk!kalt@millennium.stealth.net QUIT :Gone to have lunch ; User D syrk has quit IRC to have lunch. IKalt Informational [Page 14] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 3.1.8 Squit Command: SQUIT " Parameters: D The SQUIT command is available only to operators. It is used to I disconnect server links. Also servers can generate SQUIT messages on F error conditions. A SQUIT message may also target a remote server G connection. In this case, the SQUIT message will simply be sent to B the remote server without affecting the servers in between the # operator and the remote server. I The SHOULD be supplied by all operators who execute a SQUIT C for a remote server. The server ordered to disconnect its peer F generates a WALLOPS message with included, so that other 4 users may be aware of the reason of this action. Numeric replies: < ERR_NOPRIVILEGES ERR_NOSUCHSERVER ERR_NEEDMOREPARAMS
Examples: G SQUIT tolsun.oulu.fi :Bad Link ? ; Command to uplink of the server C tolson.oulu.fi to terminate its G connection with comment "Bad Link". E :Trillian SQUIT cm22.eng.umd.edu :Server out of control ; Command D from Trillian from to disconnect H "cm22.eng.umd.edu" from the net with D comment "Server out of control". 3.2 Channel operations I This group of messages is concerned with manipulating channels, their E properties (channel modes), and their contents (typically users). B For this reason, these messages SHALL NOT be made available to
services. H All of these messages are requests which will or will not be granted C by the server. The server MUST send a reply informing the user H whether the request was granted, denied or generated an error. When E the server grants the request, the message is typically sent back H (eventually reformatted) to the user with the prefix set to the user itself. IKalt Informational [Page 15] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 D The rules governing how channels are managed are enforced by the F servers. These rules are beyond the scope of this document. More H details are found in "Internet Relay Chat: Channel Management" [IRC-
CHAN]. 3.2.1 Join message Command: JOIN I Parameters: ( *( "," ) [ *( "," ) ] ) / "0" G The JOIN command is used by a user to request to start listening to I the specific channel. Servers MUST be able to parse arguments in the H form of a list of target, but SHOULD NOT use lists when sending JOIN messages to clients. C Once a user has joined a channel, he receives information about A all commands his server receives affecting the channel. This G includes JOIN, MODE, KICK, PART, QUIT and of course PRIVMSG/NOTICE. B This allows channel members to keep track of the other channel & members, as well as channel modes. @ If a JOIN is successful, the user receives a JOIN message as K confirmation and is then sent the channel's topic (using RPL_TOPIC) and H the list of users who are on the channel (using RPL_NAMREPLY), which " MUST include the user joining. E Note that this message accepts a special argument ("0"), which is J a special request to leave all channels the user is currently a member E of. The server will process this message as if the user had sent F a PART command (See Section 3.2.2) for each channel he is a member of. Numeric Replies: > ERR_NEEDMOREPARAMS ERR_BANNEDFROMCHAN = ERR_INVITEONLYCHAN ERR_BADCHANNELKEY ; ERR_CHANNELISFULL ERR_BADCHANMASK ? ERR_NOSUCHCHANNEL ERR_TOOMANYCHANNELS ? ERR_TOOMANYTARGETS ERR_UNAVAILRESOURCE RPL_TOPIC
Examples: F JOIN #foobar ; Command to join channel #foobar. H JOIN &foo fubar ; Command to join channel &foo using 0 key "fubar". IKalt Informational [Page 16] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 H JOIN #foo,&bar fubar ; Command to join channel #foo using F key "fubar" and &bar using no key. H JOIN #foo,#bar fubar,foobar ; Command to join channel #foo using G key "fubar", and channel #bar using 1 key "foobar". G JOIN #foo,#bar ; Command to join channels #foo and ) #bar. @ JOIN 0 ; Leave all currently joined - channels. G :WiZ!jto@tolsun.oulu.fi JOIN #Twilight_zone ; JOIN message from WiZ = on channel #Twilight_zone 3.2.2 Part message Command: PART ? Parameters: *( "," ) [ ] F The PART command causes the user sending the message to be removed H from the list of active members for all given channels listed in the F parameter string. If a "Part Message" is given, this will be sent I instead of the default message, the nickname. This request is always granted by the server. D Servers MUST be able to parse arguments in the form of a list of B target, but SHOULD NOT use lists when sending PART messages to clients. Numeric Replies: = ERR_NEEDMOREPARAMS ERR_NOSUCHCHANNEL ERR_NOTONCHANNEL
Examples: > PART #twilight_zone ; Command to leave channel 4 "#twilight_zone" D PART #oz-ops,&group5 ; Command to leave both channels < "&group5" and "#oz-ops". 2 :WiZ!jto@tolsun.oulu.fi PART #playzone :I lost > ; User WiZ leaving channel C "#playzone" with the message "I * lost". IKalt Informational [Page 17] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 3.2.3 Channel mode message Command: MODE C Parameters: *( ( "-" / "+" ) * * ) G The MODE command is provided so that users may query and change the F characteristics of a channel. For more details on available modes G and their uses, see "Internet Relay Chat: Channel Management" [IRC- G CHAN]. Note that there is a maximum limit of three (3) changes per , command for modes that take a parameter. Numeric Replies: 6 ERR_NEEDMOREPARAMS ERR_KEYSET @ ERR_NOCHANMODES ERR_CHANOPRIVSNEEDED ; ERR_USERNOTINCHANNEL ERR_UNKNOWNMODE RPL_CHANNELMODEIS < RPL_BANLIST RPL_ENDOFBANLIST ? RPL_EXCEPTLIST RPL_ENDOFEXCEPTLIST ? RPL_INVITELIST RPL_ENDOFINVITELIST RPL_UNIQOPIS H The following examples are given to help understanding the syntax of I the MODE command, but refer to modes defined in "Internet Relay Chat: # Channel Management" [IRC-CHAN].
Examples: F MODE #Finnish +imI *!*@*.fi ; Command to make #Finnish channel I moderated and 'invite-only' with user A with a hostname matching *.fi : automatically invited. I MODE #Finnish +o Kilroy ; Command to give 'chanop' privileges B to Kilroy on channel #Finnish. F MODE #Finnish +v Wiz ; Command to allow WiZ to speak on - #Finnish. E MODE #Fins -s ; Command to remove 'secret' flag 7 from channel #Fins. G MODE #42 +k oulu ; Command to set the channel key to + "oulu". B MODE #42 -k oulu ; Command to remove the "oulu" A channel key on channel "#42". IKalt Informational [Page 18] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 F MODE #eu-opers +l 10 ; Command to set the limit for the > number of users on channel 6 "#eu-opers" to 10. - :WiZ!jto@tolsun.oulu.fi MODE #eu-opers -l G ; User "WiZ" removing the limit for H the number of users on channel "#eu- + opers". G MODE &oulu +b ; Command to list ban masks set for 8 the channel "&oulu". G MODE &oulu +b *!*@* ; Command to prevent all users from , joining. + MODE &oulu +b *!*@*.edu +e *!*@*.bu.edu H ; Command to prevent any user from a I hostname matching *.edu from joining, ? except if matching *.bu.edu ' MODE #bu +be *!*@*.edu *!*@*.bu.edu H ; Comment to prevent any user from a I hostname matching *.edu from joining, ? except if matching *.bu.edu I MODE #meditation e ; Command to list exception masks set B for the channel "#meditation". G MODE #meditation I ; Command to list invitations masks F set for the channel "#meditation". D MODE !12345ircd O ; Command to ask who the channel ? creator for "!12345ircd" is 3.2.4 Topic message Command: TOPIC % Parameters: [ ] G The TOPIC command is used to change or view the topic of a channel. F The topic for channel is returned if there is no C given. If the parameter is present, the topic for that C channel will be changed, if this action is allowed for the user D requesting it. If the parameter is an empty string, the + topic for that channel will be removed. IKalt Informational [Page 19] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 Numeric Replies: < ERR_NEEDMOREPARAMS ERR_NOTONCHANNEL 5 RPL_NOTOPIC RPL_TOPIC ; ERR_CHANOPRIVSNEEDED ERR_NOCHANMODES
Examples: I :WiZ!jto@tolsun.oulu.fi TOPIC #test :New topic ; User Wiz setting the * topic. G TOPIC #test :another topic ; Command to set the topic on #test 7 to "another topic". C TOPIC #test : ; Command to clear the topic on * #test. D TOPIC #test ; Command to check the topic for * #test. 3.2.5 Names message Command: NAMES = Parameters: [ *( "," ) [ ] ] F By using the NAMES command, a user can list all nicknames that are H visible to him. For more details on what is visible and what is not, B see "Internet Relay Chat: Channel Management" [IRC-CHAN]. The H parameter specifies which channel(s) to return information : about. There is no error reply for bad channel names. H If no parameter is given, a list of all channels and their H occupants is returned. At the end of this list, a list of users who I are visible but either not on any channel or not on a visible channel ) are listed as being on `channel' "*". G If the parameter is specified, the request is forwarded to . that server which will generate the reply. 4 Wildcards are allowed in the parameter.
Numerics: < ERR_TOOMANYMATCHES ERR_NOSUCHSERVER : RPL_NAMREPLY RPL_ENDOFNAMES IKalt Informational [Page 20] IRFC 2812 Internet Relay Chat: Client Protocol April 2000
Examples: F NAMES #twilight_zone,#42 ; Command to list visible users on : #twilight_zone and #42 A NAMES ; Command to list all visible 6 channels and users 3.2.6 List message Command: LIST = Parameters: [ *( "," ) [ ] ] G The list command is used to list channels and their topics. If the C parameter is used, only the status of that channel is displayed. G If the parameter is specified, the request is forwarded to . that server which will generate the reply. 4 Wildcards are allowed in the parameter. Numeric Replies: < ERR_TOOMANYMATCHES ERR_NOSUCHSERVER 7 RPL_LIST RPL_LISTEND
Examples: C LIST ; Command to list all channels. > LIST #twilight_zone,#42 ; Command to list channels : #twilight_zone and #42 3.2.7 Invite message Command: INVITE $ Parameters: B The INVITE command is used to invite a user to a channel. The G parameter is the nickname of the person to be invited to C the target channel . There is no requirement that the H channel the target user is being invited to must exist or be a valid I channel. However, if the channel exists, only members of the channel H are allowed to invite other users. When the channel has invite-only > flag set, only channel operators may issue INVITE command. IKalt Informational [Page 21] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 B Only the user inviting and the user being invited will receive B notification of the invitation. Other channel members are not H notified. (This is unlike the MODE changes, and is occasionally the ! source of trouble for users.) Numeric Replies: : ERR_NEEDMOREPARAMS ERR_NOSUCHNICK = ERR_NOTONCHANNEL ERR_USERONCHANNEL ERR_CHANOPRIVSNEEDED 4 RPL_INVITING RPL_AWAY
Examples: ) :Angel!wings@irc.org INVITE Wiz #Dust E ; Message to WiZ when he has been D invited by user Angel to channel ) #Dust > INVITE Wiz #Twilight_Zone ; Command to invite WiZ to 2 #Twilight_zone 3.2.8 Kick command Command: KICK C Parameters: *( "," ) *( "," ) [] H The KICK command can be used to request the forced removal of a user G from a channel. It causes the to PART from the by F force. For the message to be syntactically correct, there MUST be H either one channel parameter and multiple user parameter, or as many G channel parameters as there are user parameters. If a "comment" is I given, this will be sent instead of the default message, the nickname ! of the user issuing the KICK. D The server MUST NOT send KICK messages with multiple channels or ? users to clients. This is necessarily to maintain backward + compatibility with old client software. Numeric Replies: = ERR_NEEDMOREPARAMS ERR_NOSUCHCHANNEL @ ERR_BADCHANMASK ERR_CHANOPRIVSNEEDED < ERR_USERNOTINCHANNEL ERR_NOTONCHANNEL IKalt Informational [Page 22] IRFC 2812 Internet Relay Chat: Client Protocol April 2000
Examples: B KICK &Melbourne Matthew ; Command to kick Matthew from . &Melbourne ( KICK #Finnish John :Speaking English H ; Command to kick John from #Finnish C using "Speaking English" as the 5 reason (comment). . :WiZ!jto@tolsun.oulu.fi KICK #Finnish John F ; KICK message on channel #Finnish H from WiZ to remove John from channel 3.3 Sending messages I The main purpose of the IRC protocol is to provide a base for clients ? to communicate with each other. PRIVMSG, NOTICE and SQUERY I (described in Section 3.5 on Service Query and Commands) are the only H messages available which actually perform delivery of a text message G from one client to another - the rest just make it possible and try = to ensure it happens in a reliable and structured manner. 3.3.1 Private messages Command: PRIVMSG - Parameters: I PRIVMSG is used to send private messages between users, as well as to F send messages to channels. is usually the nickname of 4 the recipient of the message, or a channel name. I The parameter may also be a host mask (#) or server H mask ($). In both cases the server will only send the PRIVMSG H to those who have a server or host matching the mask. The mask MUST G have at least 1 (one) "." in it and no wildcards following the last G ".". This requirement exists to prevent people sending messages to H "#*" or "$*", which would broadcast to all users. Wildcards are the F '*' and '?' characters. This extension to the PRIVMSG command is only available to operators. Numeric Replies: < ERR_NORECIPIENT ERR_NOTEXTTOSEND : ERR_CANNOTSENDTOCHAN ERR_NOTOPLEVEL > ERR_WILDTOPLEVEL ERR_TOOMANYTARGETS ERR_NOSUCHNICK RPL_AWAY IKalt Informational [Page 23] IRFC 2812 Internet Relay Chat: Client Protocol April 2000
Examples: F :Angel!wings@irc.org PRIVMSG Wiz :Are you receiving this message ? @ ; Message from Angel to Wiz. ) PRIVMSG Angel :yes I'm receiving it ! I ; Command to send a message to Angel. ' PRIVMSG jto@tolsun.oulu.fi :Hello ! I ; Command to send a message to a user A on server tolsun.oulu.fi with 6 username of "jto". H PRIVMSG kalt%millennium.stealth.net@irc.stealth.net :Are you a frog? A ; Message to a user on server D irc.stealth.net with username of G "kalt", and connected from the host ; millennium.stealth.net. < PRIVMSG kalt%millennium.stealth.net :Do you like cheese? D ; Message to a user on the local G server with username of "kalt", and ; connected from the host ; millennium.stealth.net. + PRIVMSG Wiz!jto@tolsun.oulu.fi :Hello ! G ; Message to the user with nickname F Wiz who is connected from the host G tolsun.oulu.fi and has the username * "jto". 3 PRIVMSG $*.fi :Server tolsun.oulu.fi rebooting. E ; Message to everyone on a server C which has a name matching *.fi. C PRIVMSG #*.edu :NSFNet is undergoing work, expect interruptions H ; Message to all users who come from D a host which has a name matching * *.edu.
3.3.2 Notice Command: NOTICE " Parameters: D The NOTICE command is used similarly to PRIVMSG. The difference F between NOTICE and PRIVMSG is that automatic replies MUST NEVER be G sent in response to a NOTICE message. This rule applies to servers IKalt Informational [Page 24] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 B too - they MUST NOT send any error reply back to the client on C receipt of a notice. The object of this rule is to avoid loops B between clients automatically sending something in response to something it received. ; This command is available to services as well as users. D This is typically used by services, and automatons (clients with I either an AI or other interactive program controlling their actions). 9 See PRIVMSG for more details on replies and examples. 3.4 Server queries and commands B The server query group of commands has been designed to return C information about any server which is connected to the network. E In these queries, where a parameter appears as , wildcard I masks are usually valid. For each parameter, however, only one query H and set of replies is to be generated. In most cases, if a nickname E is given, it will mean the server to which the user is connected. B These messages typically have little value for services, it is = therefore RECOMMENDED to forbid services from using them. 3.4.1 Motd message Command: MOTD Parameters: [ ] I The MOTD command is used to get the "Message Of The Day" of the given 5 server, or current server if is omitted. 4 Wildcards are allowed in the parameter. Numeric Replies: 4 RPL_MOTDSTART RPL_MOTD 6 RPL_ENDOFMOTD ERR_NOMOTD 3.4.2 Lusers message Command: LUSERS ' Parameters: [ [ ] ] F The LUSERS command is used to get statistics about the size of the G IRC network. If no parameter is given, the reply will be about the B whole net. If a is specified, then the reply will only IKalt Informational [Page 25] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 F concern the part of the network formed by the servers matching the G mask. Finally, if the parameter is specified, the request > is forwarded to that server which will generate the reply. 4 Wildcards are allowed in the parameter. Numeric Replies: 7 RPL_LUSERCLIENT RPL_LUSEROP = RPL_LUSERUNKOWN RPL_LUSERCHANNELS < RPL_LUSERME ERR_NOSUCHSERVER 3.4.3 Version message Command: VERSION Parameters: [ ] B The VERSION command is used to query the version of the server I program. An optional parameter is used to query the version F of the server program which a client is not directly connected to. 4 Wildcards are allowed in the parameter. Numeric Replies: 7 ERR_NOSUCHSERVER RPL_VERSION
Examples: E VERSION tolsun.oulu.fi ; Command to check the version of < server "tolsun.oulu.fi". 3.4.4 Stats message Command: STATS ( Parameters: [ [ ] ] H The stats command is used to query statistics of certain server. If E parameter is omitted, only the end of stats reply is sent back. G A query may be given for any single letter which is only checked by E the destination server and is otherwise passed on by intermediate # servers, ignored and unaltered. 4 Wildcards are allowed in the parameter. IKalt Informational [Page 26] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 ; Except for the ones below, the list of valid queries is C implementation dependent. The standard queries below SHOULD be supported by the server: H l - returns a list of the server's connections, showing how B long each connection has been established and the H traffic over that connection in Kbytes and messages for each direction; G m - returns the usage count for each of commands supported E by the server; commands for which the usage count is % zero MAY be omitted; ? o - returns a list of configured privileged users, operators; F u - returns a string showing how long the server has been up. I It is also RECOMMENDED that client and server access configuration be published this way. Numeric Replies: ERR_NOSUCHSERVER < RPL_STATSLINKINFO RPL_STATSUPTIME ; RPL_STATSCOMMANDS RPL_STATSOLINE RPL_ENDOFSTATS
Examples: H STATS m ; Command to check the command usage G for the server you are connected to 3.4.5 Links message Command: LINKS 5 Parameters: [ [ ] ] G With LINKS, a user can list all servernames, which are known by the H server answering the query. The returned list of servers MUST match @ the mask, or if no mask is given, the full list is returned. G If is given in addition to , the LINKS I command is forwarded to the first server found that matches that name C (if any), and that server is then required to answer the query. Numeric Replies: ERR_NOSUCHSERVER ; RPL_LINKS RPL_ENDOFLINKS IKalt Informational [Page 27] IRFC 2812 Internet Relay Chat: Client Protocol April 2000
Examples: G LINKS *.au ; Command to list all servers which B have a name that matches *.au; F LINKS *.edu *.bu.edu ; Command to list servers matching H *.bu.edu as seen by the first server 3 matching *.edu. 3.4.6 Time message Command: TIME Parameters: [ ] C The time command is used to query local time from the specified H server. If the parameter is not given, the server receiving ( the command must reply to the query. 4 Wildcards are allowed in the parameter. Numeric Replies: 2 ERR_NOSUCHSERVER RPL_TIME
Examples: B TIME tolsun.oulu.fi ; check the time on the server 4 "tolson.oulu.fi" 3.4.7 Connect message Command: CONNECT : Parameters: [ ] A The CONNECT command can be used to request a server to try to I establish a new connection to another server immediately. CONNECT is G a privileged command and SHOULD be available only to IRC Operators. H If a is given and its mask doesn't match name of the E parsing server, the CONNECT attempt is sent to the first match of F remote server. Otherwise the CONNECT attempt is made by the server processing the request. C The server receiving a remote CONNECT command SHOULD generate a D WALLOPS message describing the source and target of the request. Numeric Replies: : ERR_NOSUCHSERVER ERR_NOPRIVILEGES ERR_NEEDMOREPARAMS IKalt Informational [Page 28] IRFC 2812 Internet Relay Chat: Client Protocol April 2000
Examples: I CONNECT tolsun.oulu.fi 6667 ; Command to attempt to connect local I server to tolsun.oulu.fi on port 6667 3.4.8 Trace message Command: TRACE Parameters: [ ] B TRACE command is used to find the route to specific server and I information about its peers. Each server that processes this command F MUST report to the sender about it. The replies from pass-through H links form a chain, which shows route to destination. After sending D this reply back, the query MUST be sent to the next server until % given server is reached. E TRACE command is used to find the route to specific server. Each G server that processes this message MUST tell the sender about it by I sending a reply indicating it is a pass-through link, forming a chain E of replies. After sending this reply back, it MUST then send the G TRACE message to the next server until given server is reached. If C the parameter is omitted, it is RECOMMENDED that TRACE I command sends a message to the sender telling which servers the local $ server has direct connection to. A If the destination given by is an actual server, the F destination server is REQUIRED to report all servers, services and H operators which are connected to it; if the command was issued by an I operator, the server MAY also report all users which are connected to H it. If the destination given by is a nickname, then only a C reply for that nickname is given. If the parameter is B omitted, it is RECOMMENDED that the TRACE command is parsed as & targeted to the processing server. 4 Wildcards are allowed in the parameter. Numeric Replies: ERR_NOSUCHSERVER ? If the TRACE message is destined for another server, all I intermediate servers must return a RPL_TRACELINK reply to indicate C that the TRACE passed through it and where it is going next. RPL_TRACELINK IKalt Informational [Page 29] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 C A TRACE reply may be composed of any number of the following numeric replies. < RPL_TRACECONNECTING RPL_TRACEHANDSHAKE ; RPL_TRACEUNKNOWN RPL_TRACEOPERATOR 9 RPL_TRACEUSER RPL_TRACESERVER : RPL_TRACESERVICE RPL_TRACENEWTYPE 6 RPL_TRACECLASS RPL_TRACELOG RPL_TRACEEND
Examples: @ TRACE *.oulu.fi ; TRACE to a server matching - *.oulu.fi 3.4.9 Admin command Command: ADMIN Parameters: [ ] I The admin command is used to find information about the administrator C of the given server, or current server if parameter is I omitted. Each server MUST have the ability to forward ADMIN messages to other servers. 4 Wildcards are allowed in the parameter. Numeric Replies: ERR_NOSUCHSERVER 7 RPL_ADMINME RPL_ADMINLOC1 8 RPL_ADMINLOC2 RPL_ADMINEMAIL
Examples: A ADMIN tolsun.oulu.fi ; request an ADMIN reply from 2 tolsun.oulu.fi E ADMIN syrk ; ADMIN request for the server to D which the user syrk is connected IKalt Informational [Page 30] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 3.4.10 Info command Command: INFO Parameters: [ ] E The INFO command is REQUIRED to return information describing the F server: its version, when it was compiled, the patchlevel, when it E was started, and any other miscellaneous information which may be considered to be relevant. 4 Wildcards are allowed in the parameter. Numeric Replies: ERR_NOSUCHSERVER 7 RPL_INFO RPL_ENDOFINFO
Examples: @ INFO csd.bu.edu ; request an INFO reply from . csd.bu.edu G INFO Angel ; request info from the server that : Angel is connected to. 3.5 Service Query and Commands C The service query group of commands has been designed to return D information about any service which is connected to the network. 3.5.1 Servlist message Command: SERVLIST % Parameters: [ [ ] ] H The SERVLIST command is used to list services currently connected to A the network and visible to the user issuing the command. The G optional parameters may be used to restrict the result of the query 4 (to matching services names, and services type). Numeric Replies: 9 RPL_SERVLIST RPL_SERVLISTEND IKalt Informational [Page 31] IRFC 2812 Internet Relay Chat: Client Protocol April 2000
3.5.2 Squery Command: SQUERY $ Parameters: I The SQUERY command is used similarly to PRIVMSG. The only difference H is that the recipient MUST be a service. This is the only way for a . text message to be delivered to a service. 8 See PRIVMSG for more details on replies and example.
Examples: SQUERY irchelp :HELP privmsg A ; Message to the service with 5 nickname irchelp. & SQUERY dict@irc.fr :fr2en blaireau F ; Message to the service with name 0 dict@irc.fr. 3.6 User based queries F User queries are a group of commands which are primarily concerned I with finding details on a particular user or group users. When using G wildcards with any of these commands, if they match, they will only I return information on users who are 'visible' to you. The visibility G of a user is determined as a combination of the user's mode and the + common set of channels you are both on. I Although services SHOULD NOT be using this class of message, they are allowed to. 3.6.1 Who query Command: WHO " Parameters: [ [ "o" ] ] I The WHO command is used by a client to generate a query which returns G a list of information which 'matches' the parameter given by D the client. In the absence of the parameter, all visible C (users who aren't invisible (user mode +i) and who don't have a D common channel with the requesting client) are listed. The same I result can be achieved by using a of "0" or any wildcard which , will end up matching every visible user. I The passed to WHO is matched against users' host, server, real < name and nickname if the channel cannot be found. IKalt Informational [Page 32] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 H If the "o" parameter is passed only operators are returned according to the supplied. Numeric Replies: ERR_NOSUCHSERVER 6 RPL_WHOREPLY RPL_ENDOFWHO
Examples: I WHO *.fi ; Command to list all users who match 3 against "*.fi". F WHO jto* o ; Command to list all users with a G match against "jto*" if they are an - operator. 3.6.2 Whois query Command: WHOIS 3 Parameters: [ ] *( "," ) D This command is used to query information about particular user. E The server will answer this command with several numeric messages I indicating different statuses of each user which matches the mask (if D you are entitled to see them). If no wildcard is present in the H , any information about that nick which you are allowed to see is presented. C If the parameter is specified, it sends the query to a H specific server. It is useful if you want to know how long the user H in question has been idle as only local server (i.e., the server the @ user is directly connected to) knows that information, while & everything else is globally known. 4 Wildcards are allowed in the parameter. Numeric Replies: = ERR_NOSUCHSERVER ERR_NONICKNAMEGIVEN ; RPL_WHOISUSER RPL_WHOISCHANNELS 9 RPL_WHOISCHANNELS RPL_WHOISSERVER ; RPL_AWAY RPL_WHOISOPERATOR 8 RPL_WHOISIDLE ERR_NOSUCHNICK RPL_ENDOFWHOIS IKalt Informational [Page 33] IRFC 2812 Internet Relay Chat: Client Protocol April 2000
Examples: G WHOIS wiz ; return available user information 2 about nick WiZ A WHOIS eff.org trillian ; ask server eff.org for user ? information about trillian
3.6.3 Whowas Command: WHOWAS G Parameters: *( "," ) [ [ ] ] H Whowas asks for information about a nickname which no longer exists. H This may either be due to a nickname change or the user leaving IRC. G In response to this query, the server searches through its nickname H history, looking for any nicks which are lexically the same (no wild I card matching here). The history is searched backward, returning the B most recent entry first. If there are multiple entries, up to B replies will be returned (or all of them if no E parameter is given). If a non-positive number is passed as being ( , then a full search is done. 4 Wildcards are allowed in the parameter. Numeric Replies: ; ERR_NONICKNAMEGIVEN ERR_WASNOSUCHNICK 9 RPL_WHOWASUSER RPL_WHOISSERVER RPL_ENDOFWHOWAS
Examples: H WHOWAS Wiz ; return all information in the nick = history about nick "WiZ"; G WHOWAS Mermaid 9 ; return at most, the 9 most recent C entries in the nick history for . "Mermaid"; H WHOWAS Trillian 1 *.edu ; return the most recent history for D "Trillian" from the first server ; found to match "*.edu". 3.7 Miscellaneous messages I Messages in this category do not fit into any of the above categories E but are nonetheless still a part of and REQUIRED by the protocol. IKalt Informational [Page 34] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 3.7.1 Kill message Command: KILL $ Parameters: F The KILL command is used to cause a client-server connection to be B closed by the server which has the actual connection. Servers B generate KILL messages on nickname collisions. It MAY also be > available available to users who have the operator status. F Clients which have automatic reconnect algorithms effectively make H this command useless since the disconnection is only brief. It does H however break the flow of data and can be used to stop large amounts I of 'flooding' from abusive users or accidents. Abusive users usually G don't care as they will reconnect promptly and resume their abusive G behaviour. To prevent this command from being abused, any user may H elect to receive KILL messages generated for others to keep an 'eye' on would be trouble spots. I In an arena where nicknames are REQUIRED to be globally unique at all D times, KILL messages are sent whenever 'duplicates' are detected H (that is an attempt to register two users with the same nickname) in B the hope that both of them will disappear and only 1 reappear. H When a client is removed as the result of a KILL message, the server F SHOULD add the nickname to the list of unavailable nicknames in an D attempt to avoid clients to reuse this name immediately which is E usually the pattern of abusive behaviour often leading to useless F "KILL loops". See the "IRC Server Protocol" document [IRC-SERVER] + for more information on this procedure. G The comment given MUST reflect the actual reason for the KILL. For F server-generated KILLs it usually is made up of details concerning G the origins of the two conflicting nicknames. For users it is left F up to them to provide an adequate reason to satisfy others who see F it. To prevent/discourage fake KILLs from being generated to hide D the identify of the KILLer, the comment also shows a 'kill-path' F which is updated by each server it passes through, each prepending its name to the path. Numeric Replies: < ERR_NOPRIVILEGES ERR_NEEDMOREPARAMS < ERR_NOSUCHNICK ERR_CANTKILLSERVER IKalt Informational [Page 35] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 NOTE: H It is RECOMMENDED that only Operators be allowed to kill other users A with KILL command. This command has been the subject of many : controversies over the years, and along with the above H recommendation, it is also widely recognized that not even operators 6 should be allowed to kill users on remote servers. 3.7.2 Ping message Command: PING ' Parameters: [ ] H The PING command is used to test the presence of an active client or C server at the other end of the connection. Servers send a PING E message at regular intervals if no other activity detected coming B from a connection. If a connection fails to respond to a PING F message within a set amount of time, that connection is closed. A > PING message MAY be sent even if the connection is active. I When a PING message is received, the appropriate PONG message MUST be G sent as reply to (server which sent the PING message out) E as soon as possible. If the parameter is specified, it E represents the target of the ping, and the message gets forwarded
there. Numeric Replies: : ERR_NOORIGIN ERR_NOSUCHSERVER
Examples: G PING tolsun.oulu.fi ; Command to send a PING message to * server E PING WiZ tolsun.oulu.fi ; Command from WiZ to send a PING F message to server "tolsun.oulu.fi" A PING :irc.funet.fi ; Ping message sent by server 2 "irc.funet.fi" IKalt Informational [Page 36] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 3.7.3 Pong message Command: PONG & Parameters: [ ] G PONG message is a reply to ping message. If parameter is H given, this message MUST be forwarded to given target. The I parameter is the name of the entity who has responded to PING message and generated this message. Numeric Replies: : ERR_NOORIGIN ERR_NOSUCHSERVER Example: E PONG csd.bu.edu tolsun.oulu.fi ; PONG message from csd.bu.edu to 2 tolsun.oulu.fi 3.7.4 Error Command: ERROR Parameters: G The ERROR command is for use by servers when reporting a serious or E fatal error to its peers. It may also be sent from one server to E another but MUST NOT be accepted from any normal unknown clients. I Only an ERROR message SHOULD be used for reporting errors which occur I with a server-to-server link. An ERROR message is sent to the server E at the other end (which reports it to appropriate local users and C logs) and to appropriate local users and logs. It is not to be F passed onto any other servers by a server if it is received from a server. > The ERROR message is also used before terminating a client connection. F When a server sends a received ERROR message to its operators, the F message SHOULD be encapsulated inside a NOTICE message, indicating 6 that the client was not responsible for the error.
Numerics: None. IKalt Informational [Page 37] IRFC 2812 Internet Relay Chat: Client Protocol April 2000
Examples: I ERROR :Server *.fi already exists ; ERROR message to the other server < which caused this error. C NOTICE WiZ :ERROR from csd.bu.edu -- Server *.fi already exists E ; Same ERROR message as above but I sent to user WiZ on the other server. 4. Optional features I This section describes OPTIONAL messages. They are not required in a G working server implementation of the protocol described herein. In H the absence of the feature, an error reply message MUST be generated H or an unknown command error. If the message is destined for another B server to answer then it MUST be passed on (elementary parsing A REQUIRED) The allocated numerics for this are listed with the messages below. H From this section, only the USERHOST and ISON messages are available to services. 4.1 Away Command: AWAY Parameters: [ ] H With the AWAY command, clients can set an automatic reply string for I any PRIVMSG commands directed at them (not to a channel they are on). I The server sends an automatic reply to the client sending the PRIVMSG F command. The only replying server is the one to which the sending client is connected to. F The AWAY command is used either with one parameter, to set an AWAY ? message, or with no parameters, to remove the AWAY message. B Because of its high cost (memory and bandwidth wise), the AWAY C message SHOULD only be used for client-server communication. A D server MAY choose to silently ignore AWAY messages received from I other servers. To update the away status of a client across servers, B the user mode 'a' SHOULD be used instead. (See Section 3.1.5) Numeric Replies: 5 RPL_UNAWAY RPL_NOWAWAY IKalt Informational [Page 38] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 Example: D AWAY :Gone to lunch. Back in 5 ; Command to set away message to @ "Gone to lunch. Back in 5". 4.2 Rehash message Command: REHASH Parameters: None H The rehash command is an administrative command which can be used by > an operator to force the server to re-read and process its configuration file. Numeric Replies: : RPL_REHASHING ERR_NOPRIVILEGES Example: E REHASH ; message from user with operator H status to server asking it to reread ; its configuration file. 4.3 Die message Command: DIE Parameters: None E An operator can use the DIE command to shutdown the server. This A message is optional since it may be viewed as a risk to allow F arbitrary people to connect to a server as an operator and execute this command. I The DIE command MUST always be fully processed by the server to which E the sending client is connected and MUST NOT be passed onto other connected servers. Numeric Replies: ERR_NOPRIVILEGES Example: = DIE ; no parameters required. IKalt Informational [Page 39] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 4.4 Restart message Command: RESTART Parameters: None B An operator can use the restart command to force the server to I restart itself. This message is optional since it may be viewed as a H risk to allow arbitrary people to connect to a server as an operator I and execute this command, causing (at least) a disruption to service. G The RESTART command MUST always be fully processed by the server to E which the sending client is connected and MUST NOT be passed onto other connected servers. Numeric Replies: ERR_NOPRIVILEGES Example: = RESTART ; no parameters required. 4.5 Summon message Command: SUMMON 1 Parameters: [ [ ] ] B The SUMMON command can be used to give users who are on a host I running an IRC server a message asking them to please join IRC. This I message is only sent if the target server (a) has SUMMON enabled, (b) E the user is logged in and (c) the server process can write to the user's tty (or similar). H If no parameter is given it tries to summon from the ? server the client is connected to is assumed as the target. < If summon is not enabled in a server, it MUST return the ERR_SUMMONDISABLED numeric. Numeric Replies: 7 ERR_NORECIPIENT ERR_FILEERROR : ERR_NOLOGIN ERR_NOSUCHSERVER 7 ERR_SUMMONDISABLED RPL_SUMMONING IKalt Informational [Page 40] IRFC 2812 Internet Relay Chat: Client Protocol April 2000
Examples: E SUMMON jto ; summon user jto on the server's ( host I SUMMON jto tolsun.oulu.fi ; summon user jto on the host which a D server named "tolsun.oulu.fi" is , running.
4.6 Users Command: USERS Parameters: [ ] I The USERS command returns a list of users logged into the server in a H format similar to the UNIX commands who(1), rusers(1) and finger(1). G If disabled, the correct numeric MUST be returned to indicate this. H Because of the security implications of such a command, it SHOULD be F disabled by default in server implementations. Enabling it SHOULD H require recompiling the server or some equivalent change rather than G simply toggling an option and restarting the server. The procedure G to enable this command SHOULD also include suitable large comments. Numeric Replies: 7 ERR_NOSUCHSERVER ERR_FILEERROR 3 RPL_USERSSTART RPL_USERS 8 RPL_NOUSERS RPL_ENDOFUSERS ERR_USERSDISABLED Disabled Reply: ERR_USERSDISABLED Example: G USERS eff.org ; request a list of users logged in 5 on server eff.org 4.7 Operwall message Command: WALLOPS ! Parameters: B The WALLOPS command is used to send a message to all currently H connected users who have set the 'w' user mode for themselves. (See Section 3.1.5 "User modes"). IKalt Informational [Page 41] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 I After implementing WALLOPS as a user command it was found that it was I often and commonly abused as a means of sending a message to a lot of F people. Due to this, it is RECOMMENDED that the implementation of D WALLOPS allows and recognizes only servers as the originators of WALLOPS. Numeric Replies: ERR_NEEDMOREPARAMS Example: H :csd.bu.edu WALLOPS :Connect '*.uiuc.edu 6667' from Joshua ; WALLOPS H message from csd.bu.edu announcing a D CONNECT message it received from : Joshua and acted upon. 4.8 Userhost message Command: USERHOST 0 Parameters: *( SPACE ) @ The USERHOST command takes a list of up to 5 nicknames, each D separated by a space character and returns a list of information H about each nickname that it found. The returned list has each reply separated by a space. Numeric Replies: < RPL_USERHOST ERR_NEEDMOREPARAMS Example: I USERHOST Wiz Michael syrk ; USERHOST request for information on F nicks "Wiz", "Michael", and "syrk" E :ircd.stealth.net 302 yournick :syrk=+syrk@millennium.stealth.net 9 ; Reply for user syrk 4.9 Ison message Command: ISON 0 Parameters: *( SPACE ) E The ISON command was implemented to provide a quick and efficient H means to get a response about whether a given nickname was currently H on IRC. ISON only takes one (1) type of parameter: a space-separated F list of nicks. For each nickname in the list that is present, the IKalt Informational [Page 42] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 D server adds that to its reply string. Thus the reply string may H return empty (none of the given nicks are present), an exact copy of I the parameter string (all of them present) or any other subset of the I set of nicks given in the parameter. The only limit on the number of I nicks that may be checked is that the combined length MUST NOT be too A large as to cause the server to chop it off so it fits in 512 characters. H ISON is only processed by the server local to the client sending the > command and thus not passed onto other servers for further processing. Numeric Replies: < RPL_ISON ERR_NEEDMOREPARAMS Example: < ISON phone trillian WiZ jarlek Avalon Angel Monstah syrk F ; Sample ISON request for 7 nicks. 5. Replies E The following is a list of numeric replies which are generated in I response to the commands given above. Each numeric is given with its " number, name and reply string. 5.1 Command responses D Numerics in the range from 001 to 099 are used for client-server F connections only and should never travel between servers. Replies I generated in the response to commands are found in the range from 200 to 399. 001 RPL_WELCOME 5 "Welcome to the Internet Relay Network % !@" 002 RPL_YOURHOST A "Your host is , running version " 003 RPL_CREATED / "This server was created " 004 RPL_MYINFO = " * " > - The server sends Replies 001 to 004 to a user upon $ successful registration. IKalt Informational [Page 43] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 005 RPL_BOUNCE = "Try server , port " B - Sent by the server to a user to suggest an alternative > server. This is often used when the connection is 7 refused because the server is already full. 302 RPL_USERHOST , ":*1 *( " " )" < - Reply format used by USERHOST to list replies to < the query list. The reply string is composed as follows: ? reply = nickname [ "*" ] "=" ( "+" / "-" ) hostname ? The '*' indicates whether the client has registered @ as an Operator. The '-' or '+' characters represent = whether the client has set an AWAY message or not respectively. 303 RPL_ISON * ":*1 *( " " )" < - Reply format used by ISON to list replies to the query list. 301 RPL_AWAY ' " :" 305 RPL_UNAWAY 8 ":You are no longer marked as being away" 306 RPL_NOWAWAY 4 ":You have been marked as being away" < - These replies are used with the AWAY command (if ? allowed). RPL_AWAY is sent to any client sending a @ PRIVMSG to a client which is away. RPL_AWAY is only @ sent by the server to which the client is connected. @ Replies RPL_UNAWAY and RPL_NOWAWAY are sent when the 4 client removes and sets an AWAY message. 311 RPL_WHOISUSER 4 " * :" 312 RPL_WHOISSERVER / " :" 313 RPL_WHOISOPERATOR + " :is an IRC operator" IKalt Informational [Page 44] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 317 RPL_WHOISIDLE / " :seconds idle" 318 RPL_ENDOFWHOIS * " :End of WHOIS list" 319 RPL_WHOISCHANNELS 9 " :*( ( "@" / "+" ) " " )" 8 - Replies 311 - 313, 317 - 319 are all replies A generated in response to a WHOIS message. Given that > there are enough parameters present, the answering A server MUST either formulate a reply out of the above > numerics (if the query nick is found) or return an > error reply. The '*' in RPL_WHOISUSER is there as > the literal character and not as a wild card. For = each reply set, only RPL_WHOISCHANNELS may appear = more than once (for long lists of channel names). ? The '@' and '+' characters next to the channel name > indicate whether a client is a channel operator or ? has been granted permission to speak on a moderated > channel. The RPL_ENDOFWHOIS reply is used to mark 2 the end of processing a WHOIS message. 314 RPL_WHOWASUSER 4 " * :" 369 RPL_ENDOFWHOWAS & " :End of WHOWAS" @ - When replying to a WHOWAS message, a server MUST use : the replies RPL_WHOWASUSER, RPL_WHOISSERVER or @ ERR_WASNOSUCHNICK for each nickname in the presented > list. At the end of all reply batches, there MUST @ be RPL_ENDOFWHOWAS (even if there was only one reply ! and it was an error). 321 RPL_LISTSTART " Obsolete. Not used. 322 RPL_LIST / " <# visible> :" 323 RPL_LISTEND ":End of LIST" A - Replies RPL_LIST, RPL_LISTEND mark the actual replies @ with data and end of the server's response to a LIST C command. If there are no channels available to return, , only the end reply MUST be sent. IKalt Informational [Page 45] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 325 RPL_UNIQOPIS % " " 324 RPL_CHANNELMODEIS / " " 331 RPL_NOTOPIC + " :No topic is set" 332 RPL_TOPIC # " :" 9 - When sending a TOPIC message to determine the : channel topic, one of two replies is sent. If 9 the topic is set, RPL_TOPIC is sent back else RPL_NOTOPIC. 341 RPL_INVITING ! " " 7 - Returned by the server to indicate that the : attempted INVITE message was successful and is - being passed onto the end client. 342 RPL_SUMMONING . " :Summoning user to IRC" > - Returned by a server answering a SUMMON message to 4 indicate that it is summoning that user. 346 RPL_INVITELIST ' " " " 347 RPL_ENDOFINVITELIST 6 " :End of channel invite list" E - When listing the 'invitations masks' for a given channel, @ a server is required to send the list back using the ? RPL_INVITELIST and RPL_ENDOFINVITELIST messages. A A separate RPL_INVITELIST is sent for each active mask. C After the masks have been listed (or if none present) a - RPL_ENDOFINVITELIST MUST be sent. 348 RPL_EXCEPTLIST * " " " 349 RPL_ENDOFEXCEPTLIST 9 " :End of channel exception list" IKalt Informational [Page 46] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 C - When listing the 'exception masks' for a given channel, @ a server is required to send the list back using the ? RPL_EXCEPTLIST and RPL_ENDOFEXCEPTLIST messages. A A separate RPL_EXCEPTLIST is sent for each active mask. A After the masks have been listed (or if none present) / a RPL_ENDOFEXCEPTLIST MUST be sent. 351 RPL_VERSION < ". :" < - Reply by the server showing its version details. > The is the version of the software being = used (including any patchlevel revisions) and the = is used to indicate if the server is $ running in "debug mode". ? The "comments" field may contain any comments about 3 the version or further version details. 352 RPL_WHOREPLY 7 " 4 ( "H" / "G" > ["*"] [ ( "@" / "+" ) ] ' : " 315 RPL_ENDOFWHO ( " :End of WHO list" ; - The RPL_WHOREPLY and RPL_ENDOFWHO pair are used > to answer a WHO message. The RPL_WHOREPLY is only < sent if there is an appropriate match to the WHO = query. If there is a list of parameters supplied ; with a WHO message, a RPL_ENDOFWHO MUST be sent = after processing each list item with being the item. 353 RPL_NAMREPLY - "( "=" / "*" / "@" ) C :[ "@" / "+" ] *( " " [ "@" / "+" ] ) < - "@" is used for secret channels, "*" for private ; channels, and "=" for others (public channels). 366 RPL_ENDOFNAMES - " :End of NAMES list" @ - To reply to a NAMES message, a reply pair consisting = of RPL_NAMREPLY and RPL_ENDOFNAMES is sent by the > server back to the client. If there is no channel > found as in the query, then only RPL_ENDOFNAMES is IKalt Informational [Page 47] IRFC 2812 Internet Relay Chat: Client Protocol April 2000 < returned. The exception to this is when a NAMES > message is sent with no parameters and all visible > channels and contents are sent back in a series of @ RPL_NAMEREPLY messages with a RPL_ENDOFNAMES to mark the end. 364 RPL_LINKS : " : " 365 RPL_ENDOFLINKS * " :End of LINKS list" @ - In replying to the LINKS message, a server MUST send A replies back using the RPL_LINKS numeric and mark the : end of the list using an RPL_ENDOFLINKS reply. 367 RPL_BANLIST $ " " 368 RPL_ENDOFBANLIST 3 " :End of channel ban list" ? - When listing the active 'bans' for a given channel, @ a server is required to send the list back using the B RPL_BANLIST and RPL_ENDOFBANLIST messages. A separate C RPL_BANLIST is sent for each active banmask. After the < banmasks have been listed (or if none present) a * RPL_ENDOFBANLIST MUST be sent. 371 RPL_INFO ":