WormbotReporter.WIR_IRCBase

Extends

TcpLink

Modifiers

abstract

Copyright (c) 2005-2007 by Wormbo $Id$

Core.Object
|   
+-- Engine.Actor
   |   
   +-- Engine.Info
      |   
      +-- Engine.InternetInfo
         |   
         +-- IpDrv.InternetLink
            |   
            +-- IpDrv.TcpLink
               |   
               +-- WormbotReporter.WIR_IRCBase

Direct Known Subclasses:

WIR_IRCConnection

ERR_ALREADYREGISTRED Source code

":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 Source code

" :Cannot join channel (+k)"

ERR_BANNEDFROMCHAN Source code

" :Cannot join channel (+b)"

ERR_CANNOTSENDTOCHAN Source code

" :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 Source code

":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 Source code

" :Cannot join channel (+l)"

ERR_CHANOPRIVSNEEDED Source code

" :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 Source code

" :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 Source code

":File error doing on " Generic error message used to report a failed file operation during the processing of a message.

ERR_INVITEONLYCHAN Source code

" :Cannot join channel (+i)"

ERR_KEYSET Source code

" :Channel key already set"

ERR_NEEDMOREPARAMS Source code

" :Not enough parameters" Returned by the server by numerous commands to indicate to the client that it didn't supply enough parameters.

ERR_NICKCOLLISION Source code

" :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 Source code

" :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 Source code

" :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 Source code

" :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 Source code

":MOTD File is missing" Server's MOTD file could not be opened by the server.

ERR_NONICKNAMEGIVEN Source code

":No nickname given" Returned when a nickname parameter expected for a command and isn't found.

ERR_NOOPERHOST Source code

":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 Source code

":No origin specified" PING or PONG message missing the originator parameter which is required since these commands must work without valid prefixes.

ERR_NOPERMFORHOST Source code

":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 Source code

":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 Source code

":No recipient given ()" Returned by PRIVMSG to indicate that the message wasn't delivered for some reason.

ERR_NOSUCHCHANNEL Source code

" :No such channel" Used to indicate the given channel name is invalid.

ERR_NOSUCHNICK Source code

" :No such nick/channel" Used to indicate the nickname parameter supplied to a command is currently unused.

ERR_NOSUCHSERVER Source code

" :No such server" Used to indicate the server name given currently doesn't exist.

ERR_NOTEXTTOSEND Source code

":No text to send" Returned by PRIVMSG to indicate that the message wasn't delivered for some reason.

ERR_NOTONCHANNEL Source code

" :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 Source code

" :No toplevel domain specified" Returned by PRIVMSG to indicate that the message wasn't delivered for some reason. ERR_NOTOPLEVEL is an error that is returned when an invalid use of "PRIVMSG $" or "PRIVMSG #" is attempted.

ERR_NOTREGISTERED Source code

":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 Source code

":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 Source code

":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 Source code

" :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 Source code

" :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 Source code

":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 Source code

" :Unknown command" Returned to a registered client to indicate that the command sent is unknown by the server.

ERR_UNKNOWNMODE Source code

" :is unknown mode char to me"

ERR_USERNOTINCHANNEL Source code

" :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 Source code

" :is already on channel" Returned when a client tries to invite a user to a channel they are already on.

ERR_USERSDISABLED Source code

":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 Source code

":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 Source code

" :There was no such nickname" Returned by WHOWAS to indicate there is no history information for that nickname.

ERR_WILDTOPLEVEL Source code

" :Wildcard in toplevel domain" Returned by PRIVMSG to indicate that the message wasn't delivered for some reason. ERR_WILDTOPLEVEL is an error that is returned when an invalid use of "PRIVMSG $" or "PRIVMSG #" is attempted.

ERR_YOUREBANNEDCREEP Source code

":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 Source code

":" 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 Source code

":" 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_ADMINLOC2 Source code

":" 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_ADMINME Source code

" :Administrative 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_AWAY Source code

" :" This reply is 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.

RPL_BANLIST Source code

" " 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_CHANNELMODEIS Source code

" "

RPL_ENDOFBANLIST Source code

" :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 Source code

":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 Source code

" :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.

RPL_ENDOFMOTD Source code

":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 Source code

" :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 Source code

" :End of /STATS report"

RPL_ENDOFUSERS Source code

":End of users" 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_ENDOFWHO Source code

" :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.

RPL_ENDOFWHOIS Source code

" :End of /WHOIS list" 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_ENDOFWHOWAS Source code

" :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 Source code

":" 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_INVITING Source code

" " Returned by the server to indicate that the attempted INVITE message was successful and is being passed onto the end client.

RPL_ISON Source code

":[ {}]" Reply format used by ISON to list replies to the query list.

RPL_LINKS Source code

" : " 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.

RPL_LIST Source code

" <# visible> :" 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_LISTEND Source code

":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 Source code

"Channel :Users Name" 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_LUSERCHANNELS Source code

" :channels formed" 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_LUSERCLIENT Source code

":There are users and invisible on 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_LUSERME Source code

":I have clients and 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 Source code

" :operator(s) online" 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_LUSERUNKNOWN Source code

" :unknown connection(s)" 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_MOTD Source code

:- " 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_MOTDSTART Source code

":- Message of the day - " 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_NAMEREPLY Source code

" :[[@|+] [[@|+] [...]]]" 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_NONE Source code

Dummy reply number. Not used.

RPL_NOTOPIC Source code

:No topic is set" 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_NOUSERS Source code

":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 Source code

":You have been marked as being away" This reply is used with the AWAY command (if allowed). RPL_NOWAWAY is sent when the client removes an AWAY message.

RPL_REHASHING Source code

" :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 Source code

"C * "

RPL_STATSCOMMANDS Source code

" "

RPL_STATSILINE Source code

"I * "

RPL_STATSKLINE Source code

"K * "

RPL_STATSLINKINFO Source code

" "

RPL_STATSLLINE Source code

"L * "

RPL_STATSNLINE Source code

"N * "

RPL_STATSOLINE Source code

"O * "

RPL_STATSUPTIME Source code

":Server Up %d days %d:%02d:%02d"

RPL_STATSYLINE Source code

"Y "

RPL_SUMMONING Source code

" :Summoning user to IRC" Returned by a server answering a SUMMON message to indicate that it is summoning that user.

RPL_TIME Source code

" :" 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 Source code

" :" 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 Source code

"Try. " 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_TRACEHANDSHAKE Source code

"H.S. " 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 Source code

"Link " 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. 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_TRACELOG Source code

"File " 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.

RPL_TRACENEWTYPE Source code

" 0 " 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. RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.

RPL_TRACEOPERATOR Source code

"Oper " 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.

RPL_TRACESERVER Source code

"Serv S C @" 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.

RPL_TRACEUNKNOWN Source code

"???? []" 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_TRACEUSER Source code

"User " 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.

RPL_UMODEIS Source code

"" To answer a query about a client's own mode, RPL_UMODEIS is sent back.

RPL_UNAWAY Source code

":You are no longer marked as being away" This reply is used with the AWAY command (if allowed). RPL_UNAWAY is sent when the client sets an AWAY message.

RPL_USERHOST Source code

":[{}]" Reply format used by USERHOST to list replies to the query list. The reply string is composed as follows: ::= ['*'] '=' <'+'|'-'> 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 Source code

":%-8s %-9s %-8s" 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_USERSSTART Source code

":UserID Terminal Host" 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_VERSION Source code

". :" 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 the version or further version details.

RPL_WHOISCHANNELS Source code

:{[@|+]}" 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 Source code

" :seconds idle" 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_WHOISOPERATOR Source code

" :is an IRC operator" 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_WHOISSERVER Source code

" :" 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_WHOISUSER Source code

" * :" 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_WHOREPLY Source code

" [*][@|+] : " 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.

RPL_WHOWASUSER Source code

" * :" 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_YOUREOPER Source code

":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.