Thresher 1.2 Class Documentation

ReplyCode Enumeration

Numeric message codes taken from RFC 2812

[Visual Basic]
Public Enum ReplyCode
public enum ReplyCode


Member NameDescription
RPL_WELCOME IRC: Welcome to the Internet Relay Networ [nick]![user]@[host]
RPL_YOURHOST IRC: Your host is [servername], running version [ver]
RPL_CREATED IRC: This server was created [date]
RPL_MYINFO IRC: [servername] [version] [available user modes [available channel modes] Description: The server sends Replies 001 to 004 to a user upon successful registration.
RPL_BOUNCE IRC: Try server [server name], port [port number] Description: Sent by the server to a user to suggest an alternative server. This is often used when the connection is refused because the server is already full.
RPL_USERHOST IRC: :*1[reply] *( " " [reply] ) Description: 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.
RPL_ISON IRC: :*1[nick] *( " " [nick] ) Description: Reply format used by ISON to list replies to the query list.
RPL_AWAY IRC: [nick] :[away message]
RPL_UNAWAY IRC: :You are no longer marked as being away
RPL_NOWAWAY IRC: :You have been marked as being away Description: 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_WHOISUSER IRC: [nick] [user] [host] * :[real name]
RPL_WHOISSERVER IRC: [nick] [server] :[server info]
RPL_WHOISOPERATOR IRC: [nick] :is an IRC operator
RPL_WHOISIDLE IRC: [nick] [integer] :seconds idle
RPL_ENDOFWHOIS IRC: [nick] :End of WHOIS list
RPL_WHOISCHANNELS IRC: [nick] :*( ( "@" / "+" ) [channel] " " ) Description: 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_WHOWASUSER IRC: [nick] [user] [host] * :[real name]
RPL_ENDOFWHOWAS IRC: [nick] :End of WHOWAS Description: 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_LISTSTART Description: Obsolete. Not used.
RPL_LIST IRC: [channel] [# visible] :[topic]
RPL_LISTEND IRC: :End of LIST Description: Replies RPL_LIST, RPL_LISTEND mark the 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 end reply MUST be sent.
RPL_UNIQOPIS IRC: [channel] [nickname]
RPL_CHANNELMODEIS IRC: [channel] [mode] [mode params]
RPL_NOTOPIC IRC: [channel] :No topic is set
RPL_TOPIC IRC: [channel] :[topic] Description: 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_INVITING IRC: [channel] [nick] Description: Returned by the server to indicate that the attempted INVITE message was successful and is being passed onto the end client.
RPL_SUMMONING IRC: [user] :Summoning user to IRC Description: Returned by a server answering a SUMMON message to indicate that it is summoning that user.
RPL_INVITELIST IRC: [channel] [invitemask]
RPL_ENDOFINVITELIST IRC: [channel] :End of channel invite list Description: 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 separate RPL_INVITELIST is sent for each active mask. After the masks have been listed (or if none present) a RPL_ENDOFINVITELIST MUST be sent.
RPL_EXCEPTLIST IRC: [channel] [exceptionmask]
RPL_ENDOFEXCEPTLIST IRC: [channel] :End of channel exception list Description: 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 separate RPL_EXCEPTLIST is sent for each active mask. After the masks have been listed (or if none present) a RPL_ENDOFEXCEPTLIST MUST be sent.
RPL_VERSION IRC: [version].[debuglevel] [server] :[comments] Description: 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_WHOREPLY IRC: [channel] [user] [host] [server] [nick ( "H" / "G" ] ["*"] [ ( "@" / "+" ) :[hopcount] [real name]
RPL_ENDOFWHO IRC: [name] :End of WHO list Description: 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_NAMREPLY IRC: ( "=" / "*" / "@" ) [channel :[ "@" / "+" ] [nick] *( " " [ "@" / "+" ] [nick] Description: "@" is used for secret channels, "*" for private channels, and "=" for others (public channels).
RPL_ENDOFNAMES IRC: [channel] :End of NAMES list Description: 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_LINKS IRC: [mask] [server] :[hopcount] [server info]
RPL_ENDOFLINKS IRC: [mask] :End of LINKS list Description: 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_BANLIST IRC: [channel] [banmask]
RPL_ENDOFBANLIST IRC: [channel] :End of channel ban list Description: 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 banmask. After the banmasks have been listed (or if none present) a RPL_ENDOFBANLIST MUST be sent.
RPL_INFO IRC: :[string]
RPL_ENDOFINFO IRC: :End of INFO list Description: 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_MOTDSTART IRC: :- [server] Message of the day -
RPL_MOTD IRC: :- [text]
RPL_ENDOFMOTD IRC: :End of MOTD command Description: 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 MUST be surrounded by a RPL_MOTDSTART (before the RPL_MOTDs) and an RPL_ENDOFMOTD (after).
RPL_YOUREOPER IRC: :You are now an IRC operator Description: RPL_YOUREOPER is sent back to a client which has just successfully issued an OPER message and gained operator status.
RPL_REHASHING IRC: [config file] :Rehashing Description: If the REHASH option is used and an operator sends a REHASH message, an RPL_REHASHING is sent back to the operator.
RPL_YOURESERVICE IRC: You are service [servicename] Description: Sent by the server to a service upon successful registration.
RPL_TIME IRC: [server] :[string showing server's local time] Description: 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_USERS IRC: :[username] [ttyline] [hostname]
RPL_NOUSERS IRC: :Nobody logged in Description: 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_TRACELINK IRC: Link [version and debug level] [destination [next server] V[protocol version [link uptime in seconds] [backstream sendq [upstream sendq]
RPL_TRACECONNECTING IRC: Try. [class] [server]
RPL_TRACEHANDSHAKE IRC: H.S. [class] [server]
RPL_TRACEUNKNOWN IRC: ???? [class] [[client IP address in dot form]]
RPL_TRACEOPERATOR IRC: Oper [class] [nick]
RPL_TRACEUSER IRC: User [class] [nick]
RPL_TRACESERVER IRC: Serv [class] [int]S [int]C [server [nick!user|*!*]@[host|server] V[protocol version]
RPL_TRACESERVICE IRC: Service [class] [name] [type] [active type]
RPL_TRACENEWTYPE IRC: [newtype] 0 [client name]
RPL_TRACECLASS IRC: Class [class] [count]
RPL_TRACERECONNECT IRC: Class [class] [count] Unused
RPL_TRACELOG IRC: File [logfile] [debug level]
RPL_TRACEEND IRC: [server name] [version and debug level] :End of TRACE Description: The RPL_TRACE are all returned by the server in response to the TRACE message. How many are returned is dependent on 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_TRACEEND is sent to indicate the end of the list.
RPL_STATSLINKINFO IRC: [linkname] [sendq] [sent messages [sent Kbytes] [received messages [received Kbytes] [time open] Description: reports statistics on a connection. [linkname] identifies the particular connection, [sendq] is the amount of data that is queued and waiting to be sent [sent messages] the number of messages sent, and [sent Kbytes] the amount of data sent, in Kbytes. [received messages] and [received Kbytes] are the equivalent of [sent messages] and [sent Kbytes] for received data, respectively. [time open] indicates how long ago the connection was opened, in seconds.
RPL_STATSCOMMANDS IRC: [command] [count] [byte count] [remote count] Description: reports statistics on commands usage.
RPL_ENDOFSTATS IRC: [stats letter] :End of STATS report
RPL_STATSUPTIME IRC: :Server Up %d days %d:%02d:%02d Description: reports the server uptime.
RPL_STATSOLINE IRC: O [hostmask] * [name] Description: reports the allowed hosts from where user may become IRC operators.
RPL_UMODEIS IRC: [user mode string] Description: To answer a query about a client's own mode, RPL_UMODEIS is sent back.
RPL_SERVLIST IRC: [name] [server] [mask] [type] [hopcount] [info]
RPL_SERVLISTEND IRC: [mask] [type] :End of service listing Description: When listing services in reply to a SERVLIST message, a server is required to send the list back using the RPL_SERVLIST and RPL_SERVLISTEND messages. A separate RPL_SERVLIST is sent for each service. After the services have been listed (or if none present) a RPL_SERVLISTEND MUST be sent.
RPL_LUSERCLIENT IRC: :There are [integer] users and [integer services on [integer] servers
RPL_LUSEROP IRC: [integer] :operator(s) online
RPL_LUSERUNKNOWN IRC: [integer] :unknown connection(s)
RPL_LUSERCHANNELS IRC: [integer] :channels formed
RPL_LUSERME IRC: :I have [integer] clients and [integer servers Description: 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 and RPL_LUSERME. The other replies are only sent back if a non-zero count is found for them.
RPL_ADMINME IRC: [server] :Administrative info
RPL_ADMINLOC1 IRC: :[admin info]
RPL_ADMINLOC2 IRC: :[admin info]
RPL_ADMINEMAIL IRC: :[admin info] Description: When replying to an ADMIN message, a server is expected to use replies RPL_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 institution (RPL_ADMINLOC2) and constly the administrative contact for the server (an email address here is REQUIRED) in RPL_ADMINEMAIL.
RPL_TRYAGAIN IRC: [command] :Please wait a while and try again. Description: When a server drops a command without processing it, it MUST use the reply RPL_TRYAGAIN to inform the originating client.
ERR_NOSUCHNICK IRC: [nickname] :No such nick/channel Description: Used to indicate the nickname parameter supplied to a command is currently unused.
ERR_NOSUCHSERVER IRC: [server name] :No such server Description: Used to indicate the server name given currently does not exist.
ERR_NOSUCHCHANNEL IRC: [channel name] :No such channel Description: Used to indicate the given channel name is invalid.
ERR_CANNOTSENDTOCHAN IRC: [channel name] :Cannot send to channel Description: 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 or where the user is banned and is trying to send a PRIVMSG message to that channel.
ERR_TOOMANYCHANNELS IRC: [channel name] :You have joined too many channels Description: Sent to a user when they have joined the maximum number of allowed channels and they try to join another channel.
ERR_WASNOSUCHNICK IRC: [nickname] :There was no such nickname Description: Returned by WHOWAS to indicate there is no history information for that nickname.
ERR_TOOMANYTARGETS IRC: [target] :[error code] recipients. [abort message] Description: Returned to a client which is attempting to send a PRIVMSG/NOTICE using the user@host destination format and for a user@host which has several occurrences. Returned to a client which trying to send a PRIVMSG/NOTICE to too many recipients. Returned to a client which is attempting to JOIN a safe channel using the shortname when there are more than one such channel.
ERR_NOSUCHSERVICE IRC: [service name] :No such service Description: Returned to a client which is attempting to send a SQUERY to a service which does not exist.
ERR_NOORIGIN IRC: :No origin specified Description: PING or PONG message missing the originator parameter.
ERR_NORECIPIENT IRC: :No recipient given ([command])
ERR_NOTEXTTOSEND IRC: :No text to send
ERR_NOTOPLEVEL IRC: [mask] :No toplevel domain specified
ERR_WILDTOPLEVEL IRC: [mask] :Wildcard in toplevel domain
ERR_BADMASK IRC: PRIVMSG $[server]" or "PRIVMSG #[host]" is attempted Description: 412 - 415 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
ERR_TOOMANYLINES A query returned too many results. This is not an offical part of the RFC but added since it seems to be in use.
ERR_UNKNOWNCOMMAND IRC: [command] :Unknown command Description: Returned to a registered client to indicate that the command sent is unknown by the server.
ERR_NOMOTD IRC: :MOTD File is missing Description: Server's MOTD file could not be opened by the server.
ERR_NOADMININFO IRC: [server] :No administrative info available Description: Returned by a server in response to an ADMIN message when there is an error in finding the appropriate information.
ERR_FILEERROR IRC: :File error doing [file op] on [file] Description: Generic error message used to report a failed file operation during the processing of a message.
ERR_NONICKNAMEGIVEN IRC: :No nickname given Description: Returned when a nickname parameter expected for a command and isn't found.
ERR_ERRONEUSNICKNAME IRC: [nick] :Erroneous nickname Description: Returned after receiving a NICK message which contains characters which do not fall in the defined set. See section 2.3.1 for details on valid nicknames.
ERR_NICKNAMEINUSE IRC: [nick] :Nickname is already in use Description: Returned when a NICK message is processed that results in an attempt to change to a currently existing nickname.
ERR_NICKCOLLISION IRC: [nick] :Nickname collision KILL from [user]@[host] Description: Returned by a server to a client when it detects a nickname collision (registered of a NICK that already exists by another server).
ERR_UNAVAILRESOURCE IRC: [nick/channel] :Nick/channel is temporarily unavailable Description: Returned by a server to a user trying to join a channel currently blocked by the channel delay mechanism. Returned by a server to a user trying to change nickname when the desired nickname is blocked by the nick delay mechanism.
ERR_USERNOTINCHANNEL IRC: [nick] [channel] :They aren't on that channel Description: Returned by the server to indicate that the target user of the command is not on the given channel.
ERR_NOTONCHANNEL IRC: [channel] :You're not on that channel Description: Returned by the server whenever a client tries to perform a channel affecting command for which the client isn't a member.
ERR_USERONCHANNEL IRC: [user] [channel] :is already on channel Description: Returned when a client tries to invite a user to a channel they are already on.
ERR_NOLOGIN IRC: [user] :User not logged in Description: Returned by the summon after a SUMMON command for a user was unable to be performed since they were not logged in.
ERR_SUMMONDISABLED IRC: :SUMMON has been disabled Description: Returned as a response to the SUMMON command. MUST be returned by any server which doesn't implement it.
ERR_USERSDISABLED IRC: :USERS has been disabled Description: Returned as a response to the USERS command. MUST be returned by any server which does not implement it.
ERR_NOTREGISTERED IRC: :You have not registered Description: Returned by the server to indicate that the client MUST be registered before the server will allow it to be parsed in detail.
ERR_NEEDMOREPARAMS IRC: [command] :Not enough parameters Description: Returned by the server by numerous commands to indicate to the client that it didn't supply enough parameters.
ERR_ALREADYREGISTRED IRC: :Unauthorized command (already registered) Description: 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_NOPERMFORHOST IRC: :Your host isn't among the privileged Description: 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_PASSWDMISMATCH IRC: :Password incorrect Description: Returned to indicate a failed attempt at registering a connection for which a password was required and was either not given or incorrect.
ERR_YOUREBANNEDCREEP IRC: :You are banned from this server Description: Returned after an attempt to connect and register yourself with a server which has been setup to explicitly deny connections to you.
ERR_YOUWILLBEBANNED IRC: :You are banned from this server Description: Sent by a server to a user to inform that access to the server will soon be denied.
ERR_KEYSET IRC: [channel] :Channel key already set
ERR_CHANNELISFULL IRC: [channel] :Cannot join channel (+l)
ERR_UNKNOWNMODE IRC: [char] :is unknown mode char to me for [channel]
ERR_INVITEONLYCHAN IRC: [channel] :Cannot join channel (+i)
ERR_BANNEDFROMCHAN IRC: [channel] :Cannot join channel (+b)
ERR_BADCHANNELKEY IRC: [channel] :Cannot join channel (+k)
ERR_BADCHANMASK IRC: [channel] :Bad Channel Mask
ERR_NOCHANMODES IRC: [channel] :Channel doesn't support modes
ERR_BANLISTFULL IRC: [channel] [char] :Channel list is full
ERR_NOPRIVILEGES IRC: :Permission Denied- You're not an IRC operator Description: Any command requiring operator privileges to operate MUST return this error to indicate the attempt was unsuccessful.
ERR_CHANOPRIVSNEEDED IRC: [channel] :You're not channel operator Description: 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_CANTKILLSERVER IRC: :You can't kill a server! Description: Any attempts to use the KILL command on a server are to be refused and this error returned directly to the client.
ERR_RESTRICTED IRC: :Your connection is restricted! Description: Sent by the server to a user upon connection to indicate the restricted nature of the connection (user mode "+r").
ERR_UNIQOPPRIVSNEEDED IRC: :You're not the original channel operator Description: Any MODE requiring "channel creator" privileges MUST return this error if the client making the attempt is not a chanop on the specified channel.
ERR_NOOPERHOST IRC: :No O-lines for your host Description: 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_UMODEUNKNOWNFLAG IRC: :Unknown MODE flag Description: 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_USERSDONTMATCH IRC: :Cannot change mode for other users Description: Error sent to any user trying to view or change the user mode for a user other than themselves.
ConnectionFailed When the TCP/IP connection unexpectedly fails.
IrcServerError The IRC server sent an 'ERROR' message for some reason.
BadDccEndpoint When the socket connection information sent by the remote user in a DCC request is bad.
UnparseableMessage A message from the IRC server that cannot be parsed. This may be because the message is intended to cause problems, it may be an unsupported protocol such as DCC Voice, or it may be that the Thresher parser simply cannot understand it.
UnableToResume Normally a DCC Resume message is sent in response to a DCC Send. This error is signaled when a DCC Resume message is received without a previous Send or the Send session has timed out.
UnknownEncryptionProtocol Signaled when a DCC Get or SEND contains an encryption protocol that Thresher does not support.
BadDccAcceptValue When trying to resume a DCC transfer the remote user is supposed to send an Accept message with the same starting position in the file. If these numbers differ this error is raised.
BadResumePosition If the remote user sends a DCC resume request which asks for a start position greater than or equals to the file size then this error is raised.
DccConnectionRefused When attempting to connect to another machine using DCC and the target machine refuses the connection this error is raised.


Namespace: Sharkbite.Irc

Assembly: Sharkbite.Thresher (in Sharkbite.Thresher.dll)

See Also

Sharkbite.Irc Namespace