ERR_ALREADYREGISTRED = '462'
[line 257]
You may not reregister
Returned by the server to any link which tries to change part of the registered details (such as password or user details from second USER message).
ERR_BADCHANNELKEY = '475'
[line 312]
<channel> Cannot join channel (+k)
ERR_BANNEDFROMCHAN = '474'
[line 307]
<channel> Cannot join channel (+b)
ERR_CANNOTSENDTOCHAN = '404'
[line 64]
<channel name> Cannot send to channel
Sent to a user who is either (a) not on a channel which is mode +n or (b) not a chanop (or mode +v) on a channel which has mode +m set and is trying to send a PRIVMSG message to that channel.
ERR_CANTKILLSERVER = '483'
[line 337]
You cant kill a server!
Any attempts to use the KILL command on a server are to be refused and this error returned directly to the client.
ERR_CHANNELISFULL = '471'
[line 292]
<channel> Cannot join channel (+l)
ERR_CHANOPRIVSNEEDED = '482'
[line 329]
<channel> You're not channel operator
Any command requiring 'chanop' privileges (such as MODE messages) must return this error if the client making the attempt is not a chanop on the specified channel.
ERR_ERRONEUSNICKNAME = '432'
[line 168]
<nick> Erroneus nickname
Returned after receiving a NICK message which contains characters which do not fall in the defined set. See section x.x.x for details on valid nicknames.
ERR_FILEERROR = '424'
[line 153]
File error doing <file op> on <file>
Generic error message used to report a failed file operation during the processing of a message.
ERR_INVITEONLYCHAN = '473'
[line 302]
<channel> Cannot join channel (+i)
ERR_KEYSET = '467'
[line 287]
<channel> Channel key already set
ERR_NEEDMOREPARAMS = '461'
[line 248]
<command> Not enough parameters
Returned by the server by numerous commands to indicate to the client that it didn't supply enough parameters.
ERR_NICKCOLLISION = '436'
[line 184]
<nick> Nickname collision KILL
Returned by a server to a client when it detects a nickname collision (registered of a NICK that already exists by another server).
ERR_NICKNAMEINUSE = '433'
[line 176]
<nick> Nickname is already in use
Returned when a NICK message is processed that results in an attempt to change to a currently existing nickname.
ERR_NOADMININFO = '423'
[line 145]
<server> No administrative info available
Returned by a server in response to an ADMIN message when there is an error in finding the appropriate information.
ERR_NOLOGIN = '444'
[line 216]
<user> User not logged in
Returned by the summon after a SUMMON command for a user was unable to be performed since they were not logged in.
ERR_NOMOTD = '422'
[line 137]
MOTD File is missing
Server's MOTD file could not be opened by the server.
ERR_NONICKNAMEGIVEN = '431'
[line 160]
No nickname given
Returned when a nickname parameter expected for a command and isn't found.
ERR_NOOPERHOST = '491'
[line 346]
No O-lines for your host
If a client sends an OPER message and the server has not been configured to allow connections from the client's host as an operator, this error must be returned.
ERR_NOORIGIN = '409'
[line 97]
No origin specified
PING or PONG message missing the originator parameter which is required since these commands must work without valid prefixes.
ERR_NOPERMFORHOST = '463'
[line 266]
Your host isn't among the privileged
Returned to a client which attempts to register with a server which does not been setup to allow connections from the host the attempted connection is tried.
ERR_NOPRIVILEGES = '481'
[line 320]
Permission Denied- You're not an IRC operator
Any command requiring operator privileges to operate must return this error to indicate the attempt was unsuccessful.
ERR_NORECIPIENT = '411'
[line 102]
No recipient given (<command>)
ERR_NOSUCHCHANNEL = '403'
[line 55]
<channel name> No such channel
Used to indicate the given channel name is invalid.
ERR_NOSUCHNICK = '401'
[line 41]
<nickname> No such nick/channel
Used to indicate the nickname parameter supplied to a command is currently unused.
ERR_NOSUCHSERVER = '402'
[line 48]
<server name> No such server
Used to indicate the server name given currently doesn't exist.
ERR_NOTEXTTOSEND = '412'
[line 107]
No text to send
ERR_NOTONCHANNEL = '442'
[line 200]
<channel> You're not on that channel
Returned by the server whenever a client tries to perform a channel effecting command for which the client isn't a member.
ERR_NOTOPLEVEL = '413'
[line 112]
<mask> No toplevel domain specified
ERR_NOTREGISTERED = '451'
[line 240]
You have not registered
Returned by the server to indicate that the client must be registered before the server will allow it to be parsed in detail.
ERR_PASSWDMISMATCH = '464'
[line 274]
Password incorrect
Returned to indicate a failed attempt at registering a connection for which a password was required and was either not given or incorrect.
ERR_SUMMONDISABLED = '445'
[line 224]
SUMMON has been disabled
Returned as a response to the SUMMON command. Must be returned by any server which does not implement it.
ERR_TOOMANYCHANNELS = '405'
[line 72]
<channel name> You have joined too many channels
Sent to a user when they have joined the maximum number of allowed channels and they try to join another channel.
ERR_TOOMANYTARGETS = '407'
[line 89]
<target> Duplicate recipients. No message delivered
Returned to a client which is attempting to send PRIVMSG/NOTICE using the user@host destination format and for a user@host which has several occurrences.
ERR_UMODEUNKNOWNFLAG = '501'
[line 354]
Unknown MODE flag
Returned by the server to indicate that a MODE message was sent with a nickname parameter and that the a mode flag sent was not recognized.
ERR_UNKNOWNCOMMAND = '421'
[line 130]
<command> Unknown command
Returned to a registered client to indicate that the command sent is unknown by the server.
ERR_UNKNOWNMODE = '472'
[line 297]
<char> is unknown mode char to me
ERR_USERNOTINCHANNEL = '441'
[line 192]
<nick> <channel> They aren't on that channel
Returned by the server to indicate that the target user of the command is not on the given channel.
ERR_USERONCHANNEL = '443'
[line 208]
<user> <channel> is already on channel
Returned when a client tries to invite a user to a channel they are already on.
ERR_USERSDISABLED = '446'
[line 232]
USERS has been disabled
Returned as a response to the USERS command. Must be returned by any server which does not implement it.
ERR_USERSDONTMATCH = '502'
[line 362]
Cant change mode for other users
Error sent to any user trying to view or change the user mode for a user other than themselves.
ERR_WASNOSUCHNICK = '406'
[line 80]
<nickname> There was no such nickname
Returned by WHOWAS to indicate there is no history information for that nickname.
ERR_WILDTOPLEVEL = '414'
[line 122]
<mask> Wildcard in toplevel domain
412 - 414 are returned by PRIVMSG to indicate that the message wasn't delivered for some reason. ERR_NOTOPLEVEL and ERR_WILDTOPLEVEL are errors that are returned when an invalid use of "PRIVMSG $<server>" or "PRIVMSG #<host>" is attempted.
ERR_YOUREBANNEDCREEP = '465'
[line 282]
You are banned from this server
Returned after an attempt to connect and register yourself with a server which has been setup to explicitly deny connections to you.
RPL_ADMINEMAIL = '259'
[line 854]
<admin info>
When replying to an ADMIN message, a server is expected to use replies RLP_ADMINME through to RPL_ADMINEMAIL and provide a text message with each. For RPL_ADMINLOC1 a description of what city, state and country the server is in is expected, followed by details of the university and department (RPL_ADMINLOC2) and finally the administrative contact for the server (an email address here is required) in RPL_ADMINEMAIL.
RPL_ADMINLOC1 = '257'
[line 837]
<admin info>
RPL_ADMINLOC2 = '258'
[line 842]
<admin info>
RPL_ADMINME = '256'
[line 832]
<server> Administrative info
RPL_AWAY = '301'
[line 390]
<nick> <away message>
RPL_BANLIST = '367'
[line 575]
<channel> <banid>
RPL_CHANNELMODEIS = '324'
[line 485]
<channel> <mode> <mode params>
RPL_ENDOFBANLIST = '368'
[line 585]
<channel> 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 RPL_BANLIST and RPL_ENDOFBANLIST messages. A separate RPL_BANLIST is sent for each active banid. After the banids have been listed (or if none present) a RPL_ENDOFBANLIST must be sent.
RPL_ENDOFINFO = '374'
[line 599]
End of /INFO list
A server responding to an INFO message is required to send all its 'info' in a series of RPL_INFO messages with a RPL_ENDOFINFO reply to indicate the end of the replies.
RPL_ENDOFLINKS = '365'
[line 570]
<mask> End of /LINKS list
In replying to the LINKS message, a server must send replies back using the RPL_LINKS numeric and mark the end of the list using an RPL_ENDOFLINKS reply.v
RPL_ENDOFMOTD = '376'
[line 619]
End of /MOTD command
When responding to the MOTD message and the MOTD file is found, the file is displayed line by line, with each line no longer than 80 characters, using RPL_MOTD format replies. These should be surrounded by a RPL_MOTDSTART (before the RPL_MOTDs) and an RPL_ENDOFMOTD (after).
RPL_ENDOFNAMES = '366'
[line 557]
<channel> 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 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.
RPL_ENDOFSTATS = '219'
[line 769]
<stats letter> End of /STATS report
RPL_ENDOFUSERS = '394'
[line 660]
End of users
RPL_ENDOFWHO = '315'
[line 540]
<name> 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 <name> being the item.
RPL_ENDOFWHOIS = '318'
[line 430]
<nick> End of /WHOIS list
RPL_ENDOFWHOWAS = '369'
[line 461]
<nick> 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).
RPL_INFO = '371'
[line 590]
<string>
RPL_INVITING = '341'
[line 506]
<channel> <nick>
Returned by the server to indicate that the attempted INVITE message was successful and is being passed onto the end client.
RPL_ISON = '303'
[line 385]
[<nick> {<space><nick>}]
Reply format used by ISON to list replies to the query list.
RPL_LINKS = '364'
[line 562]
<mask> <server> <hopcount> <server info>
RPL_LIST = '322'
[line 471]
<channel> <# visible> <topic>
RPL_LISTEND = '323'
[line 480]
End of /LIST
Replies RPL_LISTSTART, RPL_LIST, RPL_LISTEND mark the start, actual replies with data and end of the server's response to a LIST command. If there are no channels available to return, only the start and end reply must be sent.
RPL_LISTSTART = '321'
[line 466]
Channel Users Name
RPL_LUSERCHANNELS = '254'
[line 816]
<integer> channels formed
RPL_LUSERCLIENT = '251'
[line 801]
There are <integer> users and <integer> invisible on <integer> servers
RPL_LUSERME = '255'
[line 827]
I have <integer> clients and <integer> servers
In processing an LUSERS message, the server sends a set of replies from RPL_LUSERCLIENT, RPL_LUSEROP, RPL_USERUNKNOWN, RPL_LUSERCHANNELS and RPL_LUSERME. When replying, a server must send back RPL_LUSERCLIENT and RPL_LUSERME. The other replies are only sent back if a non-zero count is found for them.
RPL_LUSEROP = '252'
[line 806]
<integer> operator(s) online
RPL_LUSERUNKNOWN = '253'
[line 811]
<integer> unknown connection(s)
RPL_MOTD = '372'
[line 609]
- <text>
RPL_MOTDSTART = '375'
[line 604]
- <server> Message of the day -
RPL_NAMREPLY = '353'
[line 545]
<channel> [[@|+]<nick> [[@|+]<nick> [...]]]
RPL_NONE = '300'
[line 367]
Dummy reply number. Not used.
RPL_NOTOPIC = '331'
[line 490]
<channel> No topic is set
RPL_NOUSERS = '395'
[line 670]
Nobody logged in
If the USERS message is handled by a server, the replies RPL_USERSTART, RPL_USERS, RPL_ENDOFUSERS and RPL_NOUSERS are used. RPL_USERSSTART must be sent first, following by either a sequence of RPL_USERS or a single RPL_NOUSER. Following this is RPL_ENDOFUSERS.
RPL_NOWAWAY = '306'
[line 405]
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 client removes and sets an AWAY message.
RPL_REHASHING = '382'
[line 635]
<config file> Rehashing
If the REHASH option is used and an operator sends a REHASH message, an RPL_REHASHING is sent back to the operator.
RPL_STATSCLINE = '213'
[line 744]
C <host> * <name> <port> <class>
RPL_STATSCOMMANDS = '212'
[line 739]
<command> <count>
RPL_STATSHLINE = '244'
[line 789]
H <hostmask> * <servername>
RPL_STATSILINE = '215'
[line 754]
I <host> * <host> <port> <class>
RPL_STATSKLINE = '216'
[line 759]
K <host> * <username> <port> <class>
RPL_STATSLINKINFO = '211'
[line 734]
<linkname> <sendq> <sent messages> <sent bytes> <received messages> <received
bytes> <time open>
RPL_STATSLLINE = '241'
[line 774]
L <hostmask> * <servername> <maxdepth>
RPL_STATSNLINE = '214'
[line 749]
N <host> * <name> <port> <class>
RPL_STATSOLINE = '243'
[line 784]
O <hostmask> * <name>
RPL_STATSUPTIME = '242'
[line 779]
Server Up %d days %d%02d%02d
RPL_STATSYLINE = '218'
[line 764]
Y <class> <ping frequency> <connect frequency> <max sendq>
RPL_SUMMONING = '342'
[line 514]
<user> Summoning user to IRC
Returned by a server answering a SUMMON message to indicate that it is summoning that user.
RPL_TIME = '391'
[line 645]
<server> <string showing server's local time>
When replying to the TIME message, a server must send the reply using the RPL_TIME format above. The string showing the time need only contain the correct day and time there. There is no further requirement for the time string.
RPL_TOPIC = '332'
[line 498]
<channel> <topic>
When sending a TOPIC message to determine the channel topic, one of two replies is sent. If the topic is set, RPL_TOPIC is sent back else RPL_NOTOPIC.
RPL_TRACECONNECTING = '201'
[line 680]
Try. <class> <server>
RPL_TRACEHANDSHAKE = '202'
[line 685]
H.S. <class> <server>
RPL_TRACELINK = '200'
[line 675]
Link <version & debug level> <destination> <next server>
RPL_TRACELOG = '261'
[line 728]
File <logfile> <debug level>
The RPL_TRACE* are all returned by the server in response to the TRACE message. How many are returned is dependent on the the TRACE message and whether it was sent by an operator or not. There is no predefined order for which occurs first. Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and RPL_TRACEHANDSHAKE are all used for connections which have not been fully established and are either unknown, still attempting to connect or in the process of completing the 'server handshake'. RPL_TRACELINK is sent by any server which handles a TRACE message and has to pass it on to another server. The list of RPL_TRACELINKs sent in response to a TRACE command traversing the IRC network should reflect the actual connectivity of the servers themselves along that path. RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACENEWTYPE = '208'
[line 710]
<newtype> 0 <client name>
RPL_TRACEOPERATOR = '204'
[line 695]
Oper <class> <nick>
RPL_TRACESERVER = '206'
[line 705]
Serv <class> <int>S <int>C <server> <nick!user|*!*>@<host|server>
RPL_TRACEUNKNOWN = '203'
[line 690]
???? <class> [<client IP address in dot form>]
RPL_TRACEUSER = '205'
[line 700]
User <class> <nick>
RPL_UMODEIS = '221'
[line 796]
<user mode string>
To answer a query about a client's own mode, RPL_UMODEIS is sent back.
RPL_UNAWAY = '305'
[line 395]
You are no longer marked as being away
RPL_USERHOST = '302'
[line 378]
[<reply>{<space><reply>}]
Reply format used by USERHOST to list replies to the query list. The reply string is composed as follows <reply> = <nick>['*'] '=' <'+'|'-'><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.
RPL_USERS = '393'
[line 655]
%-8s %-9s %-8s
RPL_USERSSTART = '392'
[line 650]
UserID Terminal Host
RPL_VERSION = '351'
[line 525]
<version>.<debuglevel> <server> <comments>
Reply by the server showing its version details. The <version> is the version of the software being used (including any patchlevel revisions) and the <debuglevel> is used to indicate if the server is running in "debug mode". The "comments" field may contain any comments about the version or further version details.
RPL_WHOISCHANNELS = '319'
[line 446]
<nick> {[@|+]<channel><space>}
Replies 311 - 313, 317 - 319 are all replies generated in response to a WHOIS message. Given that there are enough parameters present, the answering 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 the end of processing a WHOIS message.
RPL_WHOISIDLE = '317'
[line 425]
<nick> <integer> seconds idle
RPL_WHOISOPERATOR = '313'
[line 420]
<nick> is an IRC operator
RPL_WHOISSERVER = '312'
[line 415]
<nick> <server> <server info>
RPL_WHOISUSER = '311'
[line 410]
<nick> <user> <host> * <real name>
RPL_WHOREPLY = '352'
[line 530]
<channel> <user> <host> <server> <nick> <H|G>[*][@|+] <hopcount> <real name>
RPL_WHOWASUSER = '314'
[line 451]
<nick> <user> <host> * <real name>
RPL_YOUREOPER = '381'
[line 627]
You are now an IRC operator
RPL_YOUREOPER is sent back to a client which has just successfully issued an OPER message and gained operator status.
