IRCReply (IRClib 2.0.0.Alpha3 API)

java.lang.Object
- java.lang.Enum<IRCReply>
- - org.schwering.irc.lib.util.IRCReply

All Implemented Interfaces:

Serializable, Comparable<IRCReply>
```
public enum IRCReply
extends Enum<IRCReply>
```
An enum of IRC reply codes.

Author:

Peter Palaga

Enum Constant Summary

Enum Constants
Enum Constant and Description
`ERR_ALREADYREGISTRED` Format: "You may not reregister".
`ERR_BADCHANMASK` This numeric is no longer in use, reserved for future planned use or anything else.
`ERR_BADCHANNELKEY` Format: "<channel> Cannot join channel (+k)".
`ERR_BANNEDFROMCHAN` Format: "<channel> Cannot join channel (+b)".
`ERR_CANNOTSENDTOCHAN` Format: "<channel name> Cannot send to channel".
`ERR_CANTKILLSERVER` Format: "You cant kill a server!".
`ERR_CHANNELISFULL` Format: "<channel> Cannot join channel (+l)".
`ERR_CHANOPRIVSNEEDED` Format: "<channel> You're not channel operator".
`ERR_ERRONEUSNICKNAME` Format: "<nick> Erroneus nickname".
`ERR_FILEERROR` Format: "File error doing <file op> on <file>".
`ERR_INVITEONLYCHAN` Format: "<channel> Cannot join channel (+i)".
`ERR_KEYSET` Format: "<channel> Channel key already set".
`ERR_NEEDMOREPARAMS` Format: "<command> Not enough parameters".
`ERR_NICKCOLLISION` Format: "<nick> Nickname collision KILL".
`ERR_NICKNAMEINUSE` Format: "<nick> Nickname is already in use".
`ERR_NOADMININFO` Format: "<server> No administrative info available".
`ERR_NOLOGIN` Format: "<user> User not logged in".
`ERR_NOMOTD` Format: "MOTD File is missing".
`ERR_NONICKNAMEGIVEN` Format: "No nickname given".
`ERR_NOOPERHOST` Format: "No O-lines for your host".
`ERR_NOORIGIN` Format: "No origin specified".
`ERR_NOPERMFORHOST` Format: "Your host isn't among the privileged".
`ERR_NOPRIVILEGES` Format: "Permission Denied- You're not an IRC operator".
`ERR_NORECIPIENT` Format: "No recipient given (<command>)".
`ERR_NOSERVICEHOST` This numeric is no longer in use, reserved for future planned use or anything else.
`ERR_NOSUCHCHANNEL` Format: "<channel name> No such channel".
`ERR_NOSUCHNICK` Used to indicate the nickname parameter supplied to a command is currently unused.
`ERR_NOSUCHSERVER` Format: "<server name> No such server".
`ERR_NOTEXTTOSEND` Format: "No text to send".
`ERR_NOTONCHANNEL` Format: "<channel> You're not on that channel".
`ERR_NOTOPLEVEL` Format: "<mask> No toplevel domain specified".
`ERR_NOTREGISTERED` Format: "You have not registered".
`ERR_PASSWDMISMATCH` Format: "Password incorrect".
`ERR_SUMMONDISABLED` Format: "SUMMON has been disabled".
`ERR_TOOMANYCHANNELS` Format: "<channel name> You have joined too many channels".
`ERR_TOOMANYTARGETS` Format: "<target> Duplicate recipients.
`ERR_UMODEUNKNOWNFLAG` Format: "Unknown MODE flag".
`ERR_UNKNOWNCOMMAND` Format: "<command> Unknown command".
`ERR_UNKNOWNMODE` Format: "<char> is unknown mode char to me".
`ERR_USERNOTINCHANNEL` Format: "<nick> <channel> They aren't on that channel".
`ERR_USERONCHANNEL` Format: "<user> <channel> is already on channel".
`ERR_USERSDISABLED` Format: "USERS has been disabled".
`ERR_USERSDONTMATCH` Format: "Cant change mode for other users".
`ERR_WASNOSUCHNICK` Format: "<nickname> There was no such nickname".
`ERR_WILDTOPLEVEL` Format: "<mask> Wildcard in toplevel domain".
`ERR_YOUREBANNEDCREEP` Format: "You are banned from this server".
`ERR_YOUWILLBEBANNED` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_ADMINEMAIL` Format: "<admin info>".
`RPL_ADMINLOC1` Format: "<admin info>".
`RPL_ADMINLOC2` Format: "<admin info>".
`RPL_ADMINME` Format: "<server> Administrative info".
`RPL_AUTHNAME` Deprecated. (1) The value should be 330 instead of 333; (2) moved to `RPL_WHOISAUTHNAME`.
`RPL_AWAY` Format: "<nick> <away message>".
`RPL_BANLIST` Format: "<channel> <banid>" (RFC 1459), or "<channel> <banid> <user or *> <seconds>" where the seconds are the date when the ban was set (this format is not part of any RFC but seems to be used in several networks).
`RPL_CHANNELMODEIS` Format: "<channel> <mode> <mode params>".
`RPL_CLOSEEND` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_CLOSING` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_CREATED` Usually the first replies when you're connected.
`RPL_ENDOFBANLIST` Format: "<channel> End of channel ban list".
`RPL_ENDOFINFO` Format: "End of /INFO list".
`RPL_ENDOFLINKS` Format: "<mask> End of /LINKS list".
`RPL_ENDOFMOTD` Format: "End of /MOTD command".
`RPL_ENDOFNAMES` Format: "<channel> End of /NAMES list".
`RPL_ENDOFSERVICES` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_ENDOFSTATS` Format: "<stats letter> End of /STATS report".
`RPL_ENDOFUSERS` Format: "End of users".
`RPL_ENDOFWHO` Format: "<name> End of /WHO list".
`RPL_ENDOFWHOIS` Format: "<nick> End of /WHOIS list".
`RPL_ENDOFWHOWAS` Format: "<nick> End of WHOWAS".
`RPL_INFO` Format: "<string>".
`RPL_INFOSTART` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_INVITING` Format: "<channel> <nick>".
`RPL_ISON` Format: "[<nick> {<space><nick>}]".
`RPL_ISUPPORT` Usually the first replies when you're connected.
`RPL_KILLDONE` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_LINKS` Format: "<mask> <server> <hopcount> <server info>".
`RPL_LIST` Format: "<channel> <# visible> <topic>".
`RPL_LISTEND` Format: "End of /LIST".
`RPL_LISTSTART` Format: "Channel Users Name".
`RPL_LUSERCHANNELS` Format: "<integer> channels formed".
`RPL_LUSERCLIENT` Format: "There are <integer> users and <integer> invisible on <integer> servers".
`RPL_LUSERME` Format: "I have <integer> clients and <integer> servers".
`RPL_LUSEROP` Format: "<integer> operator(s) online".
`RPL_LUSERUNKNOWN` Format: "<integer> unknown connection(s)".
`RPL_MOTD` Format: "- <text>".
`RPL_MOTDSTART` Format: "- <server> Message of the day - ".
`RPL_MYINFO` Usually the first replies when you're connected.
`RPL_MYPORTIS` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_NAMREPLY` Format: "<channel> [[@\|+]<nick> [[@\|+]<nick> [...]]]" (RFC 1459) or "( "=" / "" / "@" ) <channel> :[ "@" / "+" ] <nick> ( " " [ "@" / "+" ] <nick> )" (RFC2812).
`RPL_NONE` Dummy reply number.
`RPL_NOTOPIC` Format: "<channel> No topic is set".
`RPL_NOUSERS` Format: "Nobody logged in".
`RPL_NOWAWAY` Format: "You have been marked as being away".
`RPL_REHASHING` Format: "<config file> Rehashing".
`RPL_SERVICE` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_SERVICEINFO` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_SERVLIST` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_SERVLISTEND` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_STATSCLINE` Format: "C <host> * <name> <port> <class>".
`RPL_STATSCOMMANDS` Format: "<command> <count>".
`RPL_STATSHLINE` Format: "H <hostmask> * <servername>".
`RPL_STATSILINE` Format: "I <host> * <host> <port> <class>".
`RPL_STATSKLINE` Format: "K <host> * <username> <port> <class>".
`RPL_STATSLINKINFO` Format: "<linkname> <sendq> <sent messages> <sent bytes> <received messages> <received bytes> <time open>".
`RPL_STATSLLINE` Format: "L <hostmask> * <servername> <maxdepth>".
`RPL_STATSNLINE` Format: "N <host> * <name> <port> <class>".
`RPL_STATSOLINE` Format: "O <hostmask> * <name>"
`RPL_STATSQLINE` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_STATSUPTIME` Format: "Server Up %d days %d:%02d:%02d".
`RPL_STATSYLINE` Format: "Y <class> <ping frequency> <connect frequency> <max sendq>".
`RPL_SUMMONING` Format: "<user> Summoning user to IRC".
`RPL_TIME` Format: "<server> <string showing server's local time>".
`RPL_TOPIC` Format: "<channel> <topic>".
`RPL_TOPICINFO` Format: "<channel> <nick-who-set-topic> <seconds>".
`RPL_TRACECLASS` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_TRACECONNECTING` Format: "Try.
`RPL_TRACEHANDSHAKE` Format: "H.S.
`RPL_TRACELINK` Format: "Link <version & debug level> <destination> <next server>".
`RPL_TRACELOG` Format: "File <logfile> <debug level>".
`RPL_TRACENEWTYPE` Format: "<newtype> 0 <client name>".
`RPL_TRACEOPERATOR` Format: "Oper <class> <nick>".
`RPL_TRACESERVER` Format: "Serv <class> <int>S <int>C <server> <nick!user\|!>@<host\|server>".
`RPL_TRACEUNKNOWN` Format: "???? <class> [<client IP address in dot form>]".
`RPL_TRACEUSER` Format: "User <class> <nick>".
`RPL_UMODEIS` Format: "<user mode string>".
`RPL_UNAWAY` Format: "You are no longer marked as being away".
`RPL_USERHOST` Format: "[<reply>{<space><reply>}]".
`RPL_USERS` Format: "%-8s %-9s %-8s".
`RPL_USERSSTART` Format: "UserID Terminal Host".
`RPL_VERSION` Format: "<version>.<debuglevel> <server> <comments>".
`RPL_WELCOME` Usually the first replies when you're connected.
`RPL_WHOISAUTHNAME` Format: "<nick> <authname> is authed as" This is part of /WHOIS on many servers which provide bots to authenticate.
`RPL_WHOISCHANNELS` Format: "<nick> {[@\|+]<channel><space>}".
`RPL_WHOISCHANOP` This numeric is no longer in use, reserved for future planned use or anything else.
`RPL_WHOISIDLE` Format: "<nick> <integer> seconds idle".
`RPL_WHOISOPERATOR` Format: "<nick> is an IRC operator".
`RPL_WHOISSERVER` Format: "<nick> <server> <server info>".
`RPL_WHOISUSER` Format: "<nick> <user> <host> * :<real name>".
`RPL_WHOREPLY` Format: "<channel> <user> <host> <server> <nick> <H\|G>[*][@\|+] <hopcount> <real name>".
`RPL_WHOWASUSER` Format: "<nick> <user> <host> * <real name>".
`RPL_YOUREOPER` Format: "You are now an IRC operator".
`RPL_YOURHOST` Usually the first replies when you're connected.

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`int`	`getCode()`
`static IRCReply`	`valueByCode(int code)`
`static IRCReply`	`valueOf(String name)` Returns the enum constant of this type with the specified name.
`static IRCReply[]`	`values()` Returns an array containing the constants of this enum type, in the order they are declared.

Methods inherited from class java.lang.Enum
clone, compareTo, equals, finalize, getDeclaringClass, hashCode, name, ordinal, toString, valueOf

Methods inherited from class java.lang.Object
getClass, notify, notifyAll, wait, wait, wait

- Enum Constant Detail
  - RPL_WELCOME
```
public static final IRCReply RPL_WELCOME
```
    Usually the first replies when you're connected.
  - RPL_YOURHOST
```
public static final IRCReply RPL_YOURHOST
```
    Usually the first replies when you're connected.
  - RPL_CREATED
```
public static final IRCReply RPL_CREATED
```
    Usually the first replies when you're connected.
  - RPL_MYINFO
```
public static final IRCReply RPL_MYINFO
```
    Usually the first replies when you're connected.
  - RPL_ISUPPORT
```
public static final IRCReply RPL_ISUPPORT
```
    Usually the first replies when you're connected.
  - RPL_NONE
```
public static final IRCReply RPL_NONE
```
    Dummy reply number. Not used.
  - RPL_USERHOST
```
public static final IRCReply RPL_USERHOST
```
    Format: "[<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_ISON
```
public static final IRCReply RPL_ISON
```
    Format: "[<nick> {<space><nick>}]". Reply format used by ISON to list replies to the query list.
  - RPL_AWAY
```
public static final IRCReply RPL_AWAY
```
    Format: "<nick> <away message>".
  - RPL_UNAWAY
```
public static final IRCReply RPL_UNAWAY
```
    Format: "You are no longer marked as being away".
  - RPL_NOWAWAY
```
public static final IRCReply RPL_NOWAWAY
```
    Format: "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_WHOISUSER
```
public static final IRCReply RPL_WHOISUSER
```
    Format: "<nick> <user> <host> * :<real name>". 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
```
public static final IRCReply RPL_WHOISSERVER
```
    Format: "<nick> <server> <server info>". 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
```
public static final IRCReply RPL_WHOISOPERATOR
```
    Format: "<nick> 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_WHOISIDLE
```
public static final IRCReply RPL_WHOISIDLE
```
    Format: "<nick> <integer> 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_ENDOFWHOIS
```
public static final IRCReply RPL_ENDOFWHOIS
```
    Format: "<nick> 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_WHOISCHANNELS
```
public static final IRCReply RPL_WHOISCHANNELS
```
    Format: "<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_WHOISAUTHNAME
```
public static final IRCReply RPL_WHOISAUTHNAME
```
    Format: "<nick> <authname> is authed as" This is part of /WHOIS on many servers which provide bots to authenticate. This is not part of the RFC.
  - RPL_WHOWASUSER
```
public static final IRCReply RPL_WHOWASUSER
```
    Format: "<nick> <user> <host> * <real name>".
  - RPL_ENDOFWHOWAS
```
public static final IRCReply RPL_ENDOFWHOWAS
```
    Format: "<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_LISTSTART
```
public static final IRCReply RPL_LISTSTART
```
    Format: "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_LIST
```
public static final IRCReply RPL_LIST
```
    Format: "<channel> <# visible> <topic>". 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
```
public static final IRCReply RPL_LISTEND
```
    Format: "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_CHANNELMODEIS
```
public static final IRCReply RPL_CHANNELMODEIS
```
    Format: "<channel> <mode> <mode params>".
  - RPL_AUTHNAME
```
public static final IRCReply RPL_AUTHNAME
```
    Deprecated. (1) The value should be 330 instead of 333; (2) moved to RPL_WHOISAUTHNAME.
    
    Format: "<nick> <authname> is authed as" This is part of /WHOIS on many servers which provide bots to authenticate. This is not part of the RFC.
  - RPL_NOTOPIC
```
public static final IRCReply RPL_NOTOPIC
```
    Format: "<channel> 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 public static final int RPL_NOTOPIC.
  - RPL_TOPIC
```
public static final IRCReply RPL_TOPIC
```
    Format: "<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 public static final int RPL_NOTOPIC.
  - RPL_TOPICINFO
```
public static final IRCReply RPL_TOPICINFO
```
    Format: "<channel> <nick-who-set-topic> <seconds>". The seconds are not milliseconds; just multiply it with 1000 and then format a date with it.
  - RPL_INVITING
```
public static final IRCReply RPL_INVITING
```
    Format: "<channel> <nick>". Returned by the server to indicate that the attempted INVITE message was successful and is being passed onto the end client.
  - RPL_SUMMONING
```
public static final IRCReply RPL_SUMMONING
```
    Format: "<user> Summoning user to IRC". Returned by a server answering a SUMMON message to indicate that it is summoning that user.
  - RPL_VERSION
```
public static final IRCReply RPL_VERSION
```
    Format: "<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_WHOREPLY
```
public static final IRCReply RPL_WHOREPLY
```
    Format: "<channel> <user> <host> <server> <nick> <H|G>[*][@|+] <hopcount> <real name>". 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_ENDOFWHO
```
public static final IRCReply RPL_ENDOFWHO
```
    Format: "<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_NAMREPLY
```
public static final IRCReply RPL_NAMREPLY
```
    Format: "<channel> [[@|+]<nick> [[@|+]<nick> [...]]]" (RFC 1459) or "( "=" / "*" / "@" ) <channel> :[ "@" / "+" ] <nick> *( " " [ "@" / "+" ] <nick> )" (RFC2812). 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_ENDOFNAMES
```
public static final IRCReply RPL_ENDOFNAMES
```
    Format: "<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_LINKS
```
public static final IRCReply RPL_LINKS
```
    Format: "<mask> <server> <hopcount> <server info>". 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_ENDOFLINKS
```
public static final IRCReply RPL_ENDOFLINKS
```
    Format: "<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.
  - RPL_BANLIST
```
public static final IRCReply RPL_BANLIST
```
    Format: "<channel> <banid>" (RFC 1459), or "<channel> <banid> <user or *> <seconds>" where the seconds are the date when the ban was set (this format is not part of any RFC but seems to be used in several networks). 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_ENDOFBANLIST
```
public static final IRCReply RPL_ENDOFBANLIST
```
    Format: "<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_INFO
```
public static final IRCReply RPL_INFO
```
    Format: "<string>". 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_ENDOFINFO
```
public static final IRCReply RPL_ENDOFINFO
```
    Format: "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_MOTDSTART
```
public static final IRCReply RPL_MOTDSTART
```
    Format: "- <server> 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_MOTD
```
public static final IRCReply RPL_MOTD
```
    Format: "- <text>". 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_ENDOFMOTD
```
public static final IRCReply RPL_ENDOFMOTD
```
    Format: "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_YOUREOPER
```
public static final IRCReply RPL_YOUREOPER
```
    Format: "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.
  - RPL_REHASHING
```
public static final IRCReply RPL_REHASHING
```
    Format: "<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_TIME
```
public static final IRCReply RPL_TIME
```
    Format: "<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_USERSSTART
```
public static final IRCReply RPL_USERSSTART
```
    Format: "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_USERS
```
public static final IRCReply RPL_USERS
```
    Format: "%-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_ENDOFUSERS
```
public static final IRCReply RPL_ENDOFUSERS
```
    Format: "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_NOUSERS
```
public static final IRCReply RPL_NOUSERS
```
    Format: "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_TRACELINK
```
public static final IRCReply RPL_TRACELINK
```
    Format: "Link <version & debug level> <destination> <next server>". 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_TRACECONNECTING
```
public static final IRCReply RPL_TRACECONNECTING
```
    Format: "Try. <class> <server>". 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_TRACEHANDSHAKE
```
public static final IRCReply RPL_TRACEHANDSHAKE
```
    Format: "H.S. <class> <server>". 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_TRACEUNKNOWN
```
public static final IRCReply RPL_TRACEUNKNOWN
```
    Format: "???? <class> [<client IP address in dot form>]". 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_TRACEOPERATOR
```
public static final IRCReply RPL_TRACEOPERATOR
```
    Format: "Oper <class> <nick>". 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_TRACEUSER
```
public static final IRCReply RPL_TRACEUSER
```
    Format: "User <class> <nick>". 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_TRACESERVER
```
public static final IRCReply RPL_TRACESERVER
```
    Format: "Serv <class> <int>S <int>C <server> <nick!user|*!*>@<host|server>". 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
```
public static final IRCReply RPL_TRACENEWTYPE
```
    Format: "<newtype> 0 <client name>". 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_TRACELOG
```
public static final IRCReply RPL_TRACELOG
```
    Format: "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_STATSLINKINFO
```
public static final IRCReply RPL_STATSLINKINFO
```
    Format: "<linkname> <sendq> <sent messages> <sent bytes> <received messages> <received bytes> <time open>".
  - RPL_STATSCOMMANDS
```
public static final IRCReply RPL_STATSCOMMANDS
```
    Format: "<command> <count>".
  - RPL_STATSCLINE
```
public static final IRCReply RPL_STATSCLINE
```
    Format: "C <host> * <name> <port> <class>".
  - RPL_STATSNLINE
```
public static final IRCReply RPL_STATSNLINE
```
    Format: "N <host> * <name> <port> <class>".
  - RPL_STATSILINE
```
public static final IRCReply RPL_STATSILINE
```
    Format: "I <host> * <host> <port> <class>".
  - RPL_STATSKLINE
```
public static final IRCReply RPL_STATSKLINE
```
    Format: "K <host> * <username> <port> <class>".
  - RPL_STATSYLINE
```
public static final IRCReply RPL_STATSYLINE
```
    Format: "Y <class> <ping frequency> <connect frequency> <max sendq>".
  - RPL_ENDOFSTATS
```
public static final IRCReply RPL_ENDOFSTATS
```
    Format: "<stats letter> End of /STATS report".
  - RPL_STATSLLINE
```
public static final IRCReply RPL_STATSLLINE
```
    Format: "L <hostmask> * <servername> <maxdepth>".
  - RPL_STATSUPTIME
```
public static final IRCReply RPL_STATSUPTIME
```
    Format: "Server Up %d days %d:%02d:%02d".
  - RPL_STATSOLINE
```
public static final IRCReply RPL_STATSOLINE
```
    Format: "O <hostmask> * <name>"
  - RPL_STATSHLINE
```
public static final IRCReply RPL_STATSHLINE
```
    Format: "H <hostmask> * <servername>".
  - RPL_UMODEIS
```
public static final IRCReply RPL_UMODEIS
```
    Format: "<user mode string>". To answer a query about a client's own mode, RPL_UMODEIS is sent back.
  - RPL_LUSERCLIENT
```
public static final IRCReply RPL_LUSERCLIENT
```
    Format: "There are <integer> users and <integer> invisible on <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
```
public static final IRCReply RPL_LUSEROP
```
    Format: "<integer> 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
```
public static final IRCReply RPL_LUSERUNKNOWN
```
    Format: "<integer> 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_LUSERCHANNELS
```
public static final IRCReply RPL_LUSERCHANNELS
```
    Format: "<integer> 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_LUSERME
```
public static final IRCReply RPL_LUSERME
```
    Format: "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_ADMINME
```
public static final IRCReply RPL_ADMINME
```
    Format: "<server> 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_ADMINLOC1
```
public static final IRCReply RPL_ADMINLOC1
```
    Format: "<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_ADMINLOC2
```
public static final IRCReply RPL_ADMINLOC2
```
    Format: "<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_ADMINEMAIL
```
public static final IRCReply RPL_ADMINEMAIL
```
    Format: "<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_TRACECLASS
```
public static final IRCReply RPL_TRACECLASS
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_STATSQLINE
```
public static final IRCReply RPL_STATSQLINE
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_SERVICEINFO
```
public static final IRCReply RPL_SERVICEINFO
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_ENDOFSERVICES
```
public static final IRCReply RPL_ENDOFSERVICES
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_SERVICE
```
public static final IRCReply RPL_SERVICE
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_SERVLIST
```
public static final IRCReply RPL_SERVLIST
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_SERVLISTEND
```
public static final IRCReply RPL_SERVLISTEND
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_WHOISCHANOP
```
public static final IRCReply RPL_WHOISCHANOP
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_KILLDONE
```
public static final IRCReply RPL_KILLDONE
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_CLOSING
```
public static final IRCReply RPL_CLOSING
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_CLOSEEND
```
public static final IRCReply RPL_CLOSEEND
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_INFOSTART
```
public static final IRCReply RPL_INFOSTART
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - RPL_MYPORTIS
```
public static final IRCReply RPL_MYPORTIS
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - ERR_NOSUCHNICK
```
public static final IRCReply ERR_NOSUCHNICK
```
    Used to indicate the nickname parameter supplied to a command is currently unused.
  - ERR_NOSUCHSERVER
```
public static final IRCReply ERR_NOSUCHSERVER
```
    Format: "<server name> No such server". Used to indicate the server name given currently doesn't exist.
  - ERR_NOSUCHCHANNEL
```
public static final IRCReply ERR_NOSUCHCHANNEL
```
    Format: "<channel name> No such channel". Used to indicate the given channel name is invalid.
  - ERR_CANNOTSENDTOCHAN
```
public static final IRCReply ERR_CANNOTSENDTOCHAN
```
    Format: "<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_TOOMANYCHANNELS
```
public static final IRCReply ERR_TOOMANYCHANNELS
```
    Format: "<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_WASNOSUCHNICK
```
public static final IRCReply ERR_WASNOSUCHNICK
```
    Format: "<nickname> There was no such nickname". Returned by WHOWAS to indicate there is no history information for that nickname.
  - ERR_TOOMANYTARGETS
```
public static final IRCReply ERR_TOOMANYTARGETS
```
    Format: "<target> Duplicate recipients. No message delivered". 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.
  - ERR_NOORIGIN
```
public static final IRCReply ERR_NOORIGIN
```
    Format: "No origin specified". PING or PONG message missing the originator parameter which is required since these commands must work without valid prefixes.
  - ERR_NORECIPIENT
```
public static final IRCReply ERR_NORECIPIENT
```
    Format: "No recipient given (<command>)".
  - ERR_NOTEXTTOSEND
```
public static final IRCReply ERR_NOTEXTTOSEND
```
    Format: "No text to send". 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_NOTOPLEVEL
```
public static final IRCReply ERR_NOTOPLEVEL
```
    Format: "<mask> No toplevel domain specified". 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_WILDTOPLEVEL
```
public static final IRCReply ERR_WILDTOPLEVEL
```
    Format: "<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_UNKNOWNCOMMAND
```
public static final IRCReply ERR_UNKNOWNCOMMAND
```
    Format: "<command> Unknown command". Returned to a registered client to indicate that the command sent is unknown by the server.
  - ERR_NOMOTD
```
public static final IRCReply ERR_NOMOTD
```
    Format: "MOTD File is missing". Server's MOTD file could not be opened by the server.
  - ERR_NOADMININFO
```
public static final IRCReply ERR_NOADMININFO
```
    Format: "<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_FILEERROR
```
public static final IRCReply ERR_FILEERROR
```
    Format: "File error doing <file op> on <file>". Generic error message used to report a failed file operation during the processing of a message.
  - ERR_NONICKNAMEGIVEN
```
public static final IRCReply ERR_NONICKNAMEGIVEN
```
    Format: "No nickname given". Returned when a nickname parameter expected for a command and isn't found.
  - ERR_ERRONEUSNICKNAME
```
public static final IRCReply ERR_ERRONEUSNICKNAME
```
    Format: "<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_NICKNAMEINUSE
```
public static final IRCReply ERR_NICKNAMEINUSE
```
    Format: "<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_NICKCOLLISION
```
public static final IRCReply ERR_NICKCOLLISION
```
    Format: "<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_USERNOTINCHANNEL
```
public static final IRCReply ERR_USERNOTINCHANNEL
```
    Format: "<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_NOTONCHANNEL
```
public static final IRCReply ERR_NOTONCHANNEL
```
    Format: "<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_USERONCHANNEL
```
public static final IRCReply ERR_USERONCHANNEL
```
    Format: "<user> <channel> is already on channel". Returned when a client tries to invite a user to a channel they are already on.
  - ERR_NOLOGIN
```
public static final IRCReply ERR_NOLOGIN
```
    Format: "<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_SUMMONDISABLED
```
public static final IRCReply ERR_SUMMONDISABLED
```
    Format: "SUMMON has been disabled". Returned as a response to the SUMMON command. Must be returned by any server which does not implement it.
  - ERR_USERSDISABLED
```
public static final IRCReply ERR_USERSDISABLED
```
    Format: "USERS has been disabled". Returned as a response to the USERS command. Must be returned by any server which does not implement it.
  - ERR_NOTREGISTERED
```
public static final IRCReply ERR_NOTREGISTERED
```
    Format: "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_NEEDMOREPARAMS
```
public static final IRCReply ERR_NEEDMOREPARAMS
```
    Format: "<command> Not enough parameters". Returned by the server by numerous commands to indicate to the client that it didn't supply enough parameters.
  - ERR_ALREADYREGISTRED
```
public static final IRCReply ERR_ALREADYREGISTRED
```
    Format: "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_NOPERMFORHOST
```
public static final IRCReply ERR_NOPERMFORHOST
```
    Format: "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_PASSWDMISMATCH
```
public static final IRCReply ERR_PASSWDMISMATCH
```
    Format: "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_YOUREBANNEDCREEP
```
public static final IRCReply ERR_YOUREBANNEDCREEP
```
    Format: "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.
  - ERR_YOUWILLBEBANNED
```
public static final IRCReply ERR_YOUWILLBEBANNED
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - ERR_KEYSET
```
public static final IRCReply ERR_KEYSET
```
    Format: "<channel> Channel key already set".
  - ERR_CHANNELISFULL
```
public static final IRCReply ERR_CHANNELISFULL
```
    Format: "<channel> Cannot join channel (+l)".
  - ERR_UNKNOWNMODE
```
public static final IRCReply ERR_UNKNOWNMODE
```
    Format: "<char> is unknown mode char to me".
  - ERR_INVITEONLYCHAN
```
public static final IRCReply ERR_INVITEONLYCHAN
```
    Format: "<channel> Cannot join channel (+i)".
  - ERR_BANNEDFROMCHAN
```
public static final IRCReply ERR_BANNEDFROMCHAN
```
    Format: "<channel> Cannot join channel (+b)".
  - ERR_BADCHANNELKEY
```
public static final IRCReply ERR_BADCHANNELKEY
```
    Format: "<channel> Cannot join channel (+k)".
  - ERR_BADCHANMASK
```
public static final IRCReply ERR_BADCHANMASK
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - ERR_NOPRIVILEGES
```
public static final IRCReply ERR_NOPRIVILEGES
```
    Format: "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_CHANOPRIVSNEEDED
```
public static final IRCReply ERR_CHANOPRIVSNEEDED
```
    Format: "<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_CANTKILLSERVER
```
public static final IRCReply ERR_CANTKILLSERVER
```
    Format: "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_NOOPERHOST
```
public static final IRCReply ERR_NOOPERHOST
```
    Format: "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_NOSERVICEHOST
```
public static final IRCReply ERR_NOSERVICEHOST
```
    This numeric is no longer in use, reserved for future planned use or anything else.
  - ERR_UMODEUNKNOWNFLAG
```
public static final IRCReply ERR_UMODEUNKNOWNFLAG
```
    Format: "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_USERSDONTMATCH
```
public static final IRCReply ERR_USERSDONTMATCH
```
    Format: "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.
- Method Detail
  - values
```
public static IRCReply[] values()
```
    Returns an array containing the constants of this enum type, in the order they are declared. This method may be used to iterate over the constants as follows:
```
for (IRCReply c : IRCReply.values())
    System.out.println(c);
```
    Returns:
    
    an array containing the constants of this enum type, in the order they are declared
  - valueOf
```
public static IRCReply valueOf(String name)
```
    Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
    
    Parameters:
    
    name - the name of the enum constant to be returned.
    
    Returns:
    
    the enum constant with the specified name
    
    Throws:
    
    IllegalArgumentException - if this enum type has no constant with the specified name
    
    NullPointerException - if the argument is null
  - valueByCode
```
public static IRCReply valueByCode(int code)
```
  - getCode
```
public int getCode()
```

Enum IRCReply

Enum Constant Summary

Method Summary

Methods inherited from class java.lang.Enum

Methods inherited from class java.lang.Object

Enum Constant Detail

RPL_WELCOME

RPL_YOURHOST

RPL_CREATED

RPL_MYINFO

RPL_ISUPPORT

RPL_NONE

RPL_USERHOST

RPL_ISON

RPL_AWAY

RPL_UNAWAY

RPL_NOWAWAY

RPL_WHOISUSER

RPL_WHOISSERVER

RPL_WHOISOPERATOR

RPL_WHOISIDLE

RPL_ENDOFWHOIS

RPL_WHOISCHANNELS

RPL_WHOISAUTHNAME

RPL_WHOWASUSER

RPL_ENDOFWHOWAS

RPL_LISTSTART

RPL_LIST

RPL_LISTEND

RPL_CHANNELMODEIS

RPL_AUTHNAME

RPL_NOTOPIC

RPL_TOPIC

RPL_TOPICINFO

RPL_INVITING

RPL_SUMMONING

RPL_VERSION

RPL_WHOREPLY

RPL_ENDOFWHO

RPL_NAMREPLY

RPL_ENDOFNAMES

RPL_LINKS

RPL_ENDOFLINKS

RPL_BANLIST

RPL_ENDOFBANLIST

RPL_INFO

RPL_ENDOFINFO

RPL_MOTDSTART

RPL_MOTD

RPL_ENDOFMOTD

RPL_YOUREOPER

RPL_REHASHING

RPL_TIME

RPL_USERSSTART

RPL_USERS

RPL_ENDOFUSERS

RPL_NOUSERS

RPL_TRACELINK

RPL_TRACECONNECTING

RPL_TRACEHANDSHAKE

RPL_TRACEUNKNOWN

RPL_TRACEOPERATOR

RPL_TRACEUSER

RPL_TRACESERVER

RPL_TRACENEWTYPE

RPL_TRACELOG

RPL_STATSLINKINFO

RPL_STATSCOMMANDS

RPL_STATSCLINE

RPL_STATSNLINE

RPL_STATSILINE

RPL_STATSKLINE

RPL_STATSYLINE

RPL_ENDOFSTATS

RPL_STATSLLINE

RPL_STATSUPTIME

RPL_STATSOLINE

RPL_STATSHLINE

RPL_UMODEIS

RPL_LUSERCLIENT