org.schwering.irc.lib.util.IRCReply Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of irclib Show documentation
Show all versions of irclib Show documentation
A Java Internet Relay Chat library
The newest version!
/**
* IRClib - A Java Internet Relay Chat library
* Copyright (C) 2006-2015 Christoph Schwering
* and/or other contributors as indicated by the @author tags.
*
* This library and the accompanying materials are made available under the
* terms of the
* - GNU Lesser General Public License,
* - Apache License, Version 2.0 and
* - Eclipse Public License v1.0.
* This library is distributed in the hope that it will be useful, but WITHOUT
* ANY WARRANTY.
*/
package org.schwering.irc.lib.util;
/**
* An enum of IRC reply codes.
*
* @author Peter Palaga
*/
public enum IRCReply {
/**
* Usually the first replies when you're connected.
*/
RPL_WELCOME(001),
/**
* Usually the first replies when you're connected.
*/
RPL_YOURHOST(002),
/**
* Usually the first replies when you're connected.
*/
RPL_CREATED(003),
/**
* Usually the first replies when you're connected.
*/
RPL_MYINFO(004),
/**
* Usually the first replies when you're connected.
*/
RPL_ISUPPORT(005),
/**
* Dummy reply number. Not used.
*/
RPL_NONE(300),
/**
* 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_USERHOST(302),
/**
* Format: "[<nick> {<space><nick>}]".
* Reply format used by ISON to list replies to the
* query list.
*/
RPL_ISON(303),
/**
* Format: "<nick> <away message>".
*/
RPL_AWAY(301),
/**
* Format: "You are no longer marked as being away".
*/
RPL_UNAWAY(305),
/**
* 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_NOWAWAY(306),
/**
* 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_WHOISUSER(311),
/**
* 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_WHOISSERVER(312),
/**
* 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_WHOISOPERATOR(313),
/**
* 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_WHOISIDLE(317),
/**
* 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_ENDOFWHOIS(318),
/**
* 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_WHOISCHANNELS(319),
/**
* 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_WHOISAUTHNAME(330),
/**
* Format: "<nick> <user> <host> * <real name>".
*/
RPL_WHOWASUSER(314),
/**
* 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_ENDOFWHOWAS(369),
/**
* 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_LISTSTART(321),
/**
* 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_LIST(322),
/**
* 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_LISTEND(323),
/**
* Format: "<channel> <mode> <mode params>".
*/
RPL_CHANNELMODEIS(324),
/**
* 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.
* @deprecated (1) The value should be 330 instead of 333; (2) moved to
* RPL_WHOISAUTHNAME.
*/
RPL_AUTHNAME(333),
/**
* 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_NOTOPIC(331),
/**
* 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_TOPIC(332),
/**
* 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_TOPICINFO(333),
/**
* 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_INVITING(341),
/**
* Format: "<user> Summoning user to IRC".
* Returned by a server answering a SUMMON message to
* indicate that it is summoning that user.
*/
RPL_SUMMONING(342),
/**
* 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_VERSION(351),
/**
* 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_WHOREPLY(352),
/**
* 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_ENDOFWHO(315),
/**
* 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_NAMREPLY(353),
/**
* 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_ENDOFNAMES(366),
/**
* 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_LINKS(364),
/**
* 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_ENDOFLINKS(365),
/**
* 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_BANLIST(367),
/**
* 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_ENDOFBANLIST(368),
/**
* 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_INFO(371),
/**
* 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_ENDOFINFO(374),
/**
* 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_MOTDSTART(375),
/**
* 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_MOTD(372),
/**
* 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_ENDOFMOTD(376),
/**
* 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_YOUREOPER(381),
/**
* 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_REHASHING(382),
/**
* 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_TIME(391),
/**
* 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_USERSSTART(392),
/**
* 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_USERS(393),
/**
* 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_ENDOFUSERS(394),
/**
* 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_NOUSERS(395),
/**
* 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_TRACELINK(200),
/**
* 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_TRACECONNECTING(201),
/**
* 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_TRACEHANDSHAKE(202),
/**
* 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_TRACEUNKNOWN(203),
/**
* 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_TRACEOPERATOR(204),
/**
* 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_TRACEUSER(205),
/**
* 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_TRACESERVER(206),
/**
* 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_TRACENEWTYPE(208),
/**
* 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_TRACELOG(261),
/**
* Format: "<linkname> <sendq> <sent messages>
* <sent bytes> <received messages>
* <received bytes> <time open>".
*/
RPL_STATSLINKINFO(211),
/**
* Format: "<command> <count>".
*/
RPL_STATSCOMMANDS(212),
/**
* Format: "C <host> * <name> <port> <class>".
*/
RPL_STATSCLINE(213),
/**
* Format: "N <host> * <name> <port> <class>".
*/
RPL_STATSNLINE(214),
/**
* Format: "I <host> * <host> <port> <class>".
*/
RPL_STATSILINE(215),
/**
* Format: "K <host> * <username> <port> <class>".
*/
RPL_STATSKLINE(216),
/**
* Format: "Y <class> <ping frequency> <connect
* frequency> <max sendq>".
*/
RPL_STATSYLINE(218),
/**
* Format: "<stats letter> End of /STATS report".
*/
RPL_ENDOFSTATS(219),
/**
* Format: "L <hostmask> * <servername> <maxdepth>".
*/
RPL_STATSLLINE(241),
/**
* Format: "Server Up %d days %d:%02d:%02d".
*/
RPL_STATSUPTIME(242),
/**
* Format: "O <hostmask> * <name>"
*/
RPL_STATSOLINE(243),
/**
* Format: "H <hostmask> * <servername>".
*/
RPL_STATSHLINE(244),
/**
* Format: "<user mode string>".
* To answer a query about a client's own mode,
* RPL_UMODEIS is sent back.
*/
RPL_UMODEIS(221),
/**
* 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_LUSERCLIENT(251),
/**
* 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_LUSEROP(252),
/**
* 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_LUSERUNKNOWN(253),
/**
* 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_LUSERCHANNELS(254),
/**
* 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_LUSERME(255),
/**
* 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_ADMINME(256),
/**
* 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_ADMINLOC1(257),
/**
* 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(258),
/**
* 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(259),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_TRACECLASS(209),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_STATSQLINE(217),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_SERVICEINFO(231),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_ENDOFSERVICES(232),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_SERVICE(233),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_SERVLIST(234),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_SERVLISTEND(235),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_WHOISCHANOP(316),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_KILLDONE(361),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_CLOSING(362),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_CLOSEEND(363),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_INFOSTART(373),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
RPL_MYPORTIS(384),
/**
* Used to indicate the nickname parameter supplied to
* a command is currently unused.
*/
ERR_NOSUCHNICK(401),
/**
* Format: "<server name> No such server".
* Used to indicate the server name given currently
* doesn't exist.
*/
ERR_NOSUCHSERVER(402),
/**
* Format: "<channel name> No such channel".
* Used to indicate the given channel name is invalid.
*/
ERR_NOSUCHCHANNEL(403),
/**
* 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_CANNOTSENDTOCHAN(404),
/**
* 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_TOOMANYCHANNELS(405),
/**
* Format: "<nickname> There was no such nickname".
* Returned by WHOWAS to indicate there is no history
* information for that nickname.
*/
ERR_WASNOSUCHNICK(406),
/**
* 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_TOOMANYTARGETS(407),
/**
* Format: "No origin specified".
* PING or PONG message missing the originator parameter
* which is required since these commands must work
* without valid prefixes.
*/
ERR_NOORIGIN(409),
/**
* Format: "No recipient given (<command>)".
*/
ERR_NORECIPIENT(411),
/**
* 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_NOTEXTTOSEND(412),
/**
* 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_NOTOPLEVEL(413),
/**
* 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_WILDTOPLEVEL(414),
/**
* Format: "<command> Unknown command".
* Returned to a registered client to indicate that the
* command sent is unknown by the server.
*/
ERR_UNKNOWNCOMMAND(421),
/**
* Format: "MOTD File is missing".
* Server's MOTD file could not be opened by the server.
*/
ERR_NOMOTD(422),
/**
* 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_NOADMININFO(423),
/**
* 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_FILEERROR(424),
/**
* Format: "No nickname given".
* Returned when a nickname parameter expected for a
* command and isn't found.
*/
ERR_NONICKNAMEGIVEN(431),
/**
* 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_ERRONEUSNICKNAME(432),
/**
* 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_NICKNAMEINUSE(433),
/**
* 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_NICKCOLLISION(436),
/**
* 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_USERNOTINCHANNEL(441),
/**
* 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_NOTONCHANNEL(442),
/**
* Format: "<user> <channel> is already on channel".
* Returned when a client tries to invite a user to a
* channel they are already on.
*/
ERR_USERONCHANNEL(443),
/**
* 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_NOLOGIN(444),
/**
* 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_SUMMONDISABLED(445),
/**
* 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_USERSDISABLED(446),
/**
* 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_NOTREGISTERED(451),
/**
* 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_NEEDMOREPARAMS(461),
/**
* 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_ALREADYREGISTRED(462),
/**
* 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_NOPERMFORHOST(463),
/**
* 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_PASSWDMISMATCH(464),
/**
* 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_YOUREBANNEDCREEP(465),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
ERR_YOUWILLBEBANNED(466),
/**
* Format: "<channel> Channel key already set".
*/
ERR_KEYSET(467),
/**
* Format: "<channel> Cannot join channel (+l)".
*/
ERR_CHANNELISFULL(471),
/**
* Format: "<char> is unknown mode char to me".
*/
ERR_UNKNOWNMODE(472),
/**
* Format: "<channel> Cannot join channel (+i)".
*/
ERR_INVITEONLYCHAN(473),
/**
* Format: "<channel> Cannot join channel (+b)".
*/
ERR_BANNEDFROMCHAN(474),
/**
* Format: "<channel> Cannot join channel (+k)".
*/
ERR_BADCHANNELKEY(475),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
ERR_BADCHANMASK(476),
/**
* 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_NOPRIVILEGES(481),
/**
* 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_CHANOPRIVSNEEDED(482),
/**
* 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_CANTKILLSERVER(483),
/**
* 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_NOOPERHOST(491),
/**
* This numeric is no longer in use, reserved for future planned use or
* anything else.
*/
ERR_NOSERVICEHOST(492),
/**
* 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_UMODEUNKNOWNFLAG(501),
/**
* 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.
*/
ERR_USERSDONTMATCH(502)
;
private static final IRCReply[] CODE_LOOKUP;
private static final int LOWEST_CODE;
static {
IRCReply[] vals = values();
int lowestCode = Integer.MAX_VALUE;
int highestCode = Integer.MIN_VALUE;
for (IRCReply rpl : vals) {
if (rpl.getCode() < lowestCode) {
lowestCode = rpl.getCode();
}
if (rpl.getCode() > highestCode) {
highestCode = rpl.getCode();
}
}
LOWEST_CODE = lowestCode;
CODE_LOOKUP = new IRCReply[highestCode - LOWEST_CODE + 1];
for (IRCReply rpl : vals) {
CODE_LOOKUP[getLookUpIndex(rpl.getCode())] = rpl;
}
}
public static IRCReply valueByCode(int code) {
return CODE_LOOKUP[getLookUpIndex(code)];
}
/**
* @param code2
* @return
*/
private static int getLookUpIndex(int c) {
return c - LOWEST_CODE;
}
private final int code;
/**
* @param code
*/
private IRCReply(int code) {
this.code = code;
}
public int getCode() {
return code;
}
}
© 2015 - 2025 Weber Informatics LLC | Privacy Policy