| RAW 200 (RPL_TRACELINK) Back to Top |
Format: 201 :Link <version & debug level> <destination>
<next server> V<protocol version>
<link uptime in seconds> <backstream sendq>
<upstream sendq>
Example:
Network:
Parameters:
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See Also:
201
202
203
204
205
206
207
208
209
210
261
262
Returned From:
TRACE
|
| RAW 201 (RPL_TRACECONNECTING) Back to Top |
Format: 201 :Try. <class> <server>
Example:
Network:
Parameters:
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See Also:
200
202
203
204
205
206
207
208
209
210
261
262
Returned From:
TRACE
|
| RAW 202 (RPL_TRACEHANDSHAKE) Back to Top |
Format: 202 :H.S. <class> <server>
Example:
Network:
Parameters:
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See Also:
200
201
203
204
205
206
207
208
209
210
261
262
Returned From:
TRACE
|
| RAW 203 (RPL_TRACEUNKNOWN) Back to Top |
Format: 203 :???? <class> [<client IP address in dot form>]"
Example:
Network:
Parameters:
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See Also:
200
201
202
204
205
206
207
208
209
210
261
262
Returned From:
TRACE
|
| RAW 204 (RPL_TRACEOPERATOR) Back to Top |
Format: 204 :Oper <class> <nick>
Example:
Network:
Parameters:
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See Also:
200
201
202
203
205
206
207
208
209
210
261
262
Returned From:
TRACE
|
| RAW 205 (RPL_TRACEUSER) Back to Top |
Format: 205 :User <class> <nick>
Example:
Network:
Parameters:
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See Also:
200
201
202
203
204
206
207
208
209
210
261
262
Returned From:
TRACE
|
| RAW 206 (RPL_TRACESERVER) Back to Top |
Format: 206 :Serv <class> <int>S <int>C <server>
<nick!user|*!*>@<host|server> V<protocol version>
Example:
Network:
Parameters:
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See Also:
200
201
202
203
204
205
207
208
209
210
261
262
Returned From:
TRACE
|
| RAW 207 (RPL_TRACESERVICE) Back to Top |
Format: 207 :Service <class> <name> <type> <active type>
Example:
Network:
Parameters:
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See Also:
200
201
202
203
204
205
206
208
209
210
261
262
Returned From:
TRACE
|
| RAW 208 (RPL_TRACENEWTYPE) Back to Top |
Format: 208 :<newtype> 0 <client name>
Example:
Network:
Parameters:
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See Also:
200
201
202
203
204
205
206
207
209
210
261
262
Returned From:
TRACE
|
| RAW 209 (RPL_TRACECLASS) Back to Top |
Format: 209 :Class <class> <count>
Example:
Network:
Parameters:
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See Also:
200
201
202
203
204
205
206
207
208
210
261
262
Returned From:
TRACE
|
| RAW 210 (RPL_TRACERECONNECT) Back to Top |
Format: Unused
Example:
Network:
Parameters:
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See Also:
200
201
202
203
204
205
206
207
208
209
261
262
Returned From:
TRACE
|
| RAW 211 (RPL_STATSLINKINFO) Back to Top |
Format: 211 <connection> <sendq> <sentmsg> <sentbyte> <recdmsg> <recdbyte> :<open>
Example: 211 irc1.sprynet.com 0 49243278 3327277 22095880 1208863 :134450
Network: All
Parameters:
<connection> The connection or link name. May include a host or port mask in [brackets] after the server name or address.
<sendq> Number of bytes that are buffered but unsent on this connection. (?)
<sentmsg> Number of messages sent on this connection.
<sentbyte> Number of bytes sent on this connection.
<recdmsg> Number of messages received from this connection.
<recdbyte> Number of bytes received from this connection.
<open> Amount of time (in seconds) this connection has been open.
Info:
A series of these are sent in reply to a STATS l request. (lowercase L)
They represent the ports and connections a server has available for users to connect to.
Notes:
Advanced:
The primary use for this is selecting a good port to connect to your server.
The port will usually be found in the connection parameter, within brackets, as the last
token seperated by periods.
For example,
in "NewBrunswick.NJ.US.Undernet.Org[*.6669]" the port is 6669;
in "irc.cs.cmu.edu[unknown@*@*.6666]" the port is 6666;
in "irc1.sprynet.com[0.0.0.0.9999]" the port is 9999.
If no brackets are found, the port is probably 6667. (the default port.)
If no port is listed,
then you should probably ignore that line.
Also, if the brackets contain other specifics besides a port,
you can probably assume that the port is reserved for certain users.
To determine the best port, you should find the port with the lowest traffic.
This can usually be best estimated by adding together sentmsg and recdmsg or sentbyte and recdbyte.
You may want to divide by the connection open time to get an average throughput.
Variations:
Like most STATS replies, the format of this reply can vary greatly from network to network. Some examples-
* DALnet
211 stlouis.mo.us.dal.net[*.7325] 0 1902 138 1290 24 1132 :0
211 viper.mo.us.dal.net[209.96.0.13] 0 21928 1062 166461 9935 1127 :0
* Undernet
211 NewBrunswick.NJ.US.Undernet.Org[*.6669] 0 106425518 9240002 20983702 1503812 :3240148
211 NewBrunswick.NJ.US.Undernet.Org[*@204.127.145.*.5832] 0 2307876 204111 161880 6159 :3240148
211 Ice_Age[12.69.75.157] 0 2 0 3 0 :22
211 [198.139.11.11] 0 0 0 0 0 :59
* EFnet
211 irc.cs.cmu.edu[unknown@*@*.6666] 0 14555473 1112048 3423266 153641 :1173564 1173564 -
211 irc1.sprynet.com[0.0.0.0.9999] 0 188077 20386 12894 848 :134450
As can be seen, the format of the connection parameter is where the most differences are found.
Usually this is the name of your server, but on Undernet some lines exist without server names.
Usually the name is followed by a mask in brackets. This mask may contain a mask to match against
a user address, a port, or other details.
The sentmsg/recdmsg and sentbyte/recdbyte parameters may differ in actual calculation from server to server.
Some servers may count sentbyte/recdbyte in kilobytes instead of bytes.
Also notice how DALnet servers and at least one EFnet server return additional data.
On DALnet, the final parameter is actually idle time for that connection. (in seconds?)
On EFnet the additional parameter seems to be a duplicate of the open parameter. (?)
As a final note, many networks send a header line before the actual replies, such as:
211 SendQ SendM SendBytes RcveM RcveBytes Open_since :Idle
Remember to account for this possibility when parsing replies.
See Also:
The following are sent in response to a STATS l request (lowercase L):
211 (multiple lines), 219
Returned From:
STATS
|
| RAW 212 (RPL_STATSCOMMANDS) Back to Top |
Format: 212 <command> <uses> <bytes>
Example: 212 PRIVMSG 28931 1446042
Network: All
Parameters:
<command> The name of an IRC command.
<uses> The number of times the command has been used on this server.
<bytes> A measurement of something in bytes or something similar. Not exactly sure on this one. (?)
Info:
A series of these are sent in reply to a STATS m request.
They contain statistics on the commands a server supports.
Notes:
This reply is not yet fully documented;
See Also:
The following are sent in response to a STATS m request:
212 multiple lines), 219
Returned From:
STATS
|
| RAW 213 (RPL_STATSCLINE) Back to Top |
Format: 213 C <address> * <server> <port> <class>
Example: 213 C *@205.150.226.4 * toronto.on.ca.dal.net 0 50
Network: All
Parameters:
<address> IP mask for a server. (?)
<server> Server name or mask.
<port> Port server must connect to, if any. (?)
<class> Unsure. (?)
Info:
A series of these are sent in reply to a STATS c request.
Notes:
A STATS c request lists servers that can and cannot connect to a given server.
Both 213 (C-lines) and 214 (N-lines) may be returned.
This reply is not yet fully documented.
See Also:
The following are sent in response to a STATS c request:
213, 214 (multiple lines), 219
Returned From:
STATS
|
| RAW 214 (RPL_STATSNLINE or RPL_STATSOLDNLINE) Back to Top |
Format: 214 N <address> * <server> <port> <class>>
Example: 214 N *@206.173.136.211 * *.concentric.net 0 10
Network: All
Parameters:
<address> IP mask for a server. (?)
<server> Server name or mask.
<port> Port server cannot connect to, if specified. (?)
<class> Unsure. (?)
Info:
A series of these are sent in reply to a STATS c request.
Notes:
A STATS c request lists servers that can and cannot connect to a given server.
Both 213 (C-lines) and 214 (N-lines) may be returned.
This reply is not yet fully documented; If you have further information on the contents of this reply,
please contact paiRC.
See Also:
The following are sent in response to a STATS c request:
213, 214 (multiple lines), 219
Returned From:
STATS
|
| RAW 215 (RPL_STATSILINE) Back to Top |
Format: 215 I <ipmask> * <hostmask> <port> <class>
Example: 215 I *@204.127.145.* * NOMATCH 0 3
Network: All
Parameters:
<ipmask> Mask applied to a userhost with IP address.
<hostmask> Mask applied to a userhost with a resolved address.
<port> Port user has connected to. (?)
<class> Unsure. (?)
Info:
A series of these are sent in reply to a STATS i request.
Notes:
A STATS i request (I-lines) lists classes of clients that are allowed to connect to a server.
This reply is not yet fully documented.
See Also:
The following are sent in response to a STATS i request:
215 (multiple lines), 219
Returned From:
STATS
|
| RAW 216 (RPL_STATSKLINE) Back to Top |
Format: 216 <k> <address> * <username> <details>
Example: 216 k 147.253.230.* * ~* Temporary K-line 60 min. for Auto-kline, clones (1998/07/22 12.55)
Network: Most
Parameters:
<k> k for a temporary K-line, K for a 'permanent' K-line. (?)
<address> Address to match against user.
<username> Matched against usernames. (identds)
<details> Reason for the K-line.
Info:
A series of these are sent in reply to a STATS k request.
Notes:
A STATS k request (K-lines) lists classes of clients that are not allowed to connect to a server.
This reply is not yet fully documented.
Variations:
Other servers may use another format, for example:
216 K *.mediaone.net MEDIAONE users must run IDENTD to connect 02-10-98 *~* 0 -1
Here, the username parameter is moved to third to last.
(unsure? of the relevance of the 0 and -1)
See Also:
The following are sent in response to a STATS k request:
216 (multiple lines), 219
Returned From:
STATS
|
| RAW 217 (RPL_STATSPLINE) Back to Top |
Format: 217 P <port> <??> <??>
Example: 217 P 6666 181 0x2000
Network: Undernet
Parameters:
<port> Port for connections to a server.
<??> Unsure.
Info:
A series of these are sent in reply to a STATS p request on Undernet.
Notes:
Each line lists a port (other than the default 6667 port) on which clients can connect to the server.
This reply is not yet fully documented.
See Also:
The following are sent in response to a STATS p request on Undernet:
217 (multiple lines), 219
Returned From:
STATS
|
| RAW 218 (RPL_STATSYLINE) Back to Top |
Format: 218 Y <class> <ping> <freq> <maxconnect> <sendq>
Example: 218 Y 100 120 240 1 5000000
Network: All
Parameters:
<class> Connection class. (a numeric ID)
<sendq> Maximum sendq allowed for this class, in bytes.
<ping> The frequency of PINGs sent to an idling client, in seconds.
<freq> Connect frequency. (?)
<maxconnect> The maximum number of concurrent connections allowed for a user.
Info:
A series of these are sent in reply to a STATS y request.
Notes:
Each line lists a Y-line, which details a connection class and their allowed privileges.
Connection classes are used in other lines, such as I-lines, N-lines, and C-lines.
Thanks to Justin H for helping clear up some of this information.
See Also:
The following are sent in response to a STATS y request:
218 (multiple lines), 219
Returned From:
STATS
|
| RAW 219 (RPL_ENDOFSTATS) Back to Top |
Format: 219 <char> :End of /STATS report
Example: 219 u :End of /STATS report
Network: All
Parameters:
<char> The type of stats that were requested.
Info:
Returned at the end of a STATS request.
Notes:
Different types of STATS requests generate different replies, however this numeric will always be returned last,
regardless of the request.
If the server does not recognize a STATS request, this will be returned by itself with an asterisk (*) for char.
See Also:
The following are returned for various STATS requests:
211, 212, 213, 214, 215, 216, 217, 218, 222, 223, 224, 241, 242, 243, 242, 247, 248, 249, 250
Returned From:
STATS
|
| RAW 220 (RPL_STATSBLINE) Back to Top |
Format: Undocumented
Example:
Network:
Parameters:
Info:
Notes:
See Also:
Returned From:
|
| RAW 221 (RPL_UMODEIS) Back to Top |
Format: 221 <mode>
Example: 221 +i
Network: All
Parameters:
<mode> Your usermode.
Info:
This is sent when you request to view your usermode using MODE.
See Also:
Viewing your user mode using MODE will return:
221, 008 (on Undernet only)
Returned From:
MODE
|
| RAW 222 (RPL_SQLINE_NICK) Back to Top |
DALnet Q-line
Format: 222 <nickmask> :<comment>
Example: 222 *H*lp*S*rv* :Reserved for DALnet Services
Network: DALnet
Parameters:
<nickmask> A mask matched against nicknames.
<comment> A comment explaining the reason for the Q-line.
Info:
A series of these are sent in reply to a STATS q request on DALnet.
Notes:
Each line lists a Q-line, which details a nickname that users are not allowed to use.
If a user attempts to use a nickname matching a Q-line,
they receive a 432 raw and are not allowed to use that nickname.
See Also:
The following are sent in response to a STATS q request on DALnet:
222 (multiple lines), 219
Returned From:
STATS
EFnet B-line
Format: 222 B <server> * <??> <??> <??>
Example: 222 B barracuda.sph.emory.edu * ircadmin 0 -1
Network: EFnet
Parameters:
<server> A server name. (?)
<??> Unsure.
Info:
A series of these are sent in reply to a STATS b request on EFnet.
Notes:
This reply is not yet fully documented.
See Also:
The following are sent in response to a STATS b request on EFnet:
222 (zero or more), 219
Returned From:
STATS
|
| RAW 223 (RPL_STATS_E) Back to Top |
Format: 223 E <hostmask> * <username> <??> <??>
Example: 223 E usr??.primenet.com * *mjr 0 -1
Network: EFnet
Parameters:
<hostmask> A hostmask to match addresses against.
<username> A mask to match against usernames. (identds)
<??> Unsure.
Info:
A series of these are sent in reply to a STATS e request on EFnet.
Notes:
This reply is not yet fully documented.
See Also:
The following are sent in response to a STATS e request on EFnet:
223 (one or more), 219
Returned From:
STATS
|
| RAW 224 (RPL_STATS_D) Back to Top |
Format: 224 D <ipmask> * <username> <??> <??>
Example: 224 D 208.132.73.108 * * 0 -1
Network: EFnet
Parameters:
<ipmask> A mask to match IP addresses against.
<username> A mask to match against usernames. (identds) (?)
<??> Unsure.
Info:
A series of these are sent in reply to a STATS d request on EFnet.
Notes:
This reply is not yet fully documented.
See Also:
The following are sent in response to a STATS d request on EFnet:
224 (one or more), 219
Returned From:
STATS
|
| RAW 231 (RPL_SERVICEINFO) Back to Top |
Format: Undocumented
Example:
Network:
Parameters:
Info:
Notes:
See Also:
Returned From:
|
| RAW 232 (RPL_ENDOFSERVICES) Back to Top |
Format: Undocumented
Example:
Network:
Parameters:
Info:
Notes:
See Also:
Returned From:
|
| RAW 233 (RPL_SERVICE) Back to Top |
Format: Undocumented
Example:
Network:
Parameters:
Info:
Notes:
See Also:
Returned From:
|
| RAW 234 (RPL_SERVLIST) Back to Top |
Format: 234 <name> <server> <mask> <type> <hopcount> <info>
Example: 224 ?? ?? 208.132.73.108 ?? ?? ??
Network:
Parameters:
<mask> A mask to match IP addresses against.
<??> Unsure.
Info:
When listing services in reply to a SERVLIST message,
a server is required to send the list back using the
RPL_SERVLIST and RPL_SERVLISTEND (RAW 235)messages. A separate
RPL_SERVLIST is sent for each service. After the
services have been listed (or if none present) a
RPL_SERVLISTEND MUST be sent
Notes:
This reply is not yet fully documented.
See Also:
Returned From:
SERVLIST
|
| RAW 235 (RPL_SERVLISTEND) Back to Top |
Format: 235 <mask> <type> :End of service listing
Example: 235 208.132.73.108 ?
Network:
Parameters:
<pmask> A mask to match IP addresses against.
<type> (?)
<??> Unsure.
Info:
When listing services in reply to a SERVLIST (RAW 234) message,
a server is required to send the list back using the
RPL_SERVLIST and RPL_SERVLISTEND messages. A separate
RPL_SERVLIST is sent for each service. After the
services have been listed (or if none present) a
RPL_SERVLISTEND MUST be sent
Notes:
This reply is not yet fully documented.
See Also:
Returned From:
SERVLISTEND
|
| RAW 241 (RPL_STATSLLINE) Back to Top |
Format: 241 L <address> * <server> <??> <??>
Example: 241 L <NULL> * irc2.sprynet.com 0 -1
Network: All
Parameters:
<address> IP mask for a server. (?)
<server> Server name or mask.
<??> Unsure.
Info:
A series of these are sent in reply to a STATS h request.
Notes:
A STATS h request lists servers that are treated as hubs and servers that are treated as leaves.
Both 241 (L-lines) and 244 (H-lines) may be returned.
This reply is not yet fully documented.
See Also:
The following are sent in response to a STATS h request:
241, 244 (multiple lines), 219
Returned From:
STATS
|
| RAW 242 (RPL_STATSUPTIME) Back to Top |
Format: 242 :Server Up <num> days, <time>
Example: 242 :Server Up 37 days, 9:20:39
Network: All
Parameters:
<num> The number of days the server has been up.
<time> The amount of time the server has been up.
Info:
Returned for a STATS u request.
Notes:
The time is in addition to the number of days listed. (the example would mean 37 days and a bit over 9 hours)
This time is since the last time the server was rebooted or reset.
A simple netsplit will not reset the time.
See Also:
The following are sent in sequence for a STATS u request:
242, 250 (on most servers), 219
Returned From:
STATS u
|
| RAW 243 (RPL_STATSOLINE) Back to Top |
Format: 243 <o> <mask> <password> <user> <??> <class>
Example: 243 O *@calley.stlnet.com * konjump 4293328895 1
Network: Most
Parameters:
<o> Capital O for a global operator, lowercase o for a local operator.
<mask> Mask matched against userhost.
<password> This is technically the password field, but it is shown as an asterisk for obvious reasons.
<user> Name of the operator.
<class> The connection class of the operator. (Y-lines)
<??> Unsure.
Info:
A series of these are sent in reply to a STATS o request.
Notes:
A STATS o request lists O-lines, which determine which hosts are allowed to become IRC operators.
A user must have both a userhost matching an O-line and the appropriate password to become an operator.
Thanks to Justin H for helping clear up some of this information.
This reply is not yet fully documented.
Variations:
Some servers or networks will not list O-lines, to help prevent hacking attempts.
See Also:
The following are sent in response to a STATS o request:
243 (multiple lines), 219
Returned From:
STATS
|
| RAW 244 (RPL_STATSHLINE) Back to Top |
Format: 244 H <address> * <server> <??> <??>
Example: 244 H * * indy.in.us.dal.net 0 -1
Network: All
Parameters:
<address> IP mask for a server. (?)
<server> Server name or mask.
<??> Unsure.
Info:
A series of these are sent in reply to a STATS h request.
Notes:
A STATS h request lists servers that are treated as hubs and servers that are treated as leaves.
Both 241 (L-lines) and 244 (H-lines) may be returned.
This reply is not yet fully documented.
See Also:
The following are sent in response to a STATS h request:
241 and 244 (multiple lines), 219
Returned From:
STATS
|
| RAW 245 (RPL_STATSSLINE) Back to Top |
Format: 245 S
Example: 245 S
Network: All
Parameters:
<address> IP mask for a server. (?)
<server> Server name or mask.
<??> Unsure.
Info:
A series of these are sent in reply to a STATS s request.
Notes:
This reply is not yet fully documented.
See Also:
The following are sent in response to a STATS h request:
241 and 244 (multiple lines), 219
Returned From:
STATS
|
| RAW 246 (RPL_STATSGLINE) Back to Top |
Format: 246 G <address> <timestamp> :<reason>
Example: 246 G panzer@scscomm.com 900964094 :flood bots
Network: All
Parameters:
<address> IP mask for a server. (?)
<server> Server name or mask.
<??> Unsure.
Info:
A series of these are sent in reply to a STATS g request. Hosts which are not allowed on any Undernet Servers
Notes:
A STATS h request lists servers that are treated as hubs and servers that are treated as leaves.
Both 241 (L-lines) and 244 (H-lines) may be returned.
This reply is not yet fully documented.
See Also:
The following are sent in response to a STATS h request:
241 and 244 (multiple lines), 219
Returned From:
STATS
|
| RAW 247 (RPL_STATSXLINE) Back to Top |
Format: 247 G <address> <timestamp> :<reason>
Example: 247 G panzer@scscomm.com 900964094 :flood bots
Network: Some
Parameters:
<address> Address mask matched against userhosts.
<timestamp> Timestamp for when the ban will expire. (??)
<reason> Reason for the ban.
Info:
A series of these are sent in reply to a STATS g request.
Notes:
A STATS g request lists G-lines, which are bans global to an entire network.
Users who match a G-line will be denied access to all servers on the network.
Most G-lines last for a relatively short period of time, such as a week.
This reply is not yet fully documented.
Variations:
Some servers or networks will not list G-lines.
See Also:
The following are sent in response to a STATS g request:
247 (multiple lines), 219
Returned From:
STATS
|
| RAW 248(RPL_STATSULINE) Back to Top |
Format: 248 U <host> * <??> <??> <??>
Example: 248 U Uworld2.Undernet.Org * * 0 -1
Network: Some
Parameters:
<host> The address that corresponds to the U-line.
<??> Unsure.
Info:
A series of these are sent in reply to a STATS U request (uppercase U) on networks that support U-lines.
Notes:
A STATS U request lists U-lines, which give certain hosts special priviliges.
These privledges allow the changing of modes on channels without being an op on the channel or even on the channel.
U-lines are used for special services intended for channel management or channel rescue and other related activities,
such as UWorld on Undernet and ChanServ on DALnet.
U-lines are generally global to all servers on a network.
This reply is not yet fully documented.
See Also:
The following are sent in response to a STATS U request on supported networks:
248 (one or more lines), 219
Returned From:
STATS
|
| RAW 249 (RPL_STATSDEBUG) Back to Top |
Format: 249 :<info>
Example: 249 :nick collisions 1879 unknown closes 11383991
Network: All
Parameters:
<info> Various information.
Info:
A series of these are sent in reply to a STATS t or STATS z request,
containing various debug and other information and statistics.
Notes:
The actual contents of each reply are not yet documented.
See Also:
The following are sent in response to a STATS t or z request:
249 (multiple lines), 219
Returned From:
STATS
|
| RAW 250(RPL_STATSCONN) Back to Top |
Format: 250 :Highest connection count: <total> (<num> clients)
Example: 250 :Highest connection count: 2997 (2996 clients)
Network: Most
Parameters:
<total> The highest total number of connections.
<num> The highest total number of client connections.
Info:
Returned for a STATS u request.
Also returned on some networks during the connection process.
Notes:
These numbers signify the highest count the server has had at any time since it was last rebooted.
The total number of client connections includes all users and operators on the server.
The total number of connections includes users and operators as well, but also includes server-to-server connections.
Advanced:
If you subtract the second number from the first, you will get the highest count of server-to-server connections.
For many servers, this will only be one. However, servers that host services or that are hubs will have higher counts.
Variations:
On some servers (such as many EFnet servers) this will not be returned for any reason. Instead, replies 265 and 266 are sent on connection.
See Also:
The following are sent in sequence for a STATS u request:
242,250 (most servers), 219
The following are sent in sequence on connection and in response to a LUSERS command:
251, 252, 253 (most servers), 254, 255, followed by either:
265 and 266, just 250, or a server notice
Returned From:
STATS u
|
| RAW 251 (RPL_LUSERCLIENT) Back to Top |
Format: 251 :There are <user> users and <invis> invisible on <serv> servers
Example: 251 :There are 5161 users and 33030 invisible on 58 servers
Network: All
Parameters:
<user> The number of non-invisible users currently online.
<invis> The number of invisible users currently online.
Info:
Sent to all clients once a connection has been established and the user has successfully registered.
Also sent in response to a LUSERS command.
Notes:
These numbers are for the entire network, not just one server. Adding the first two numbers together
will give you the current total user count on the entire network.
See Also:
The following are sent in sequence on connection and in response to a LUSERS command:
251, 252, 253 (most servers), 254, 255, followed by either:
265 and 266, just 250, or a server notice
Returned From:
LUSERS
|
| RAW 252 (RPL_LUSEROP) Back to Top |
Format: 252 <num> :operator(s) online
Example: 252 40 :operator(s) online
Network: All
Parameters:
<num> The number of IRC operators online
Info:
Sent to all clients once a connection has been established and the user has successfully registered.
Also sent in response to a LUSERS command.
Notes:
These numbers are for the entire network, not just one server.
Note that if a network has no operators online, this will not be sent.
See Also:
The following are sent in sequence on connection and in response to a LUSERS command:
251, 252, 253 (most servers), 254, 255, followed by either:
265 and 266, just 250, or a server notice
Returned From:
LUSERS
|
| RAW 253 (RPL_LUSERUNKNOWN) Back to Top |
Format: 253 <num> :unknown connection(s)
Example: 253 11 :unknown connection(s)
Network: Most
Parameters:
<num> The number of unknown connections
Info:
Sent to all clients once a connection has been established and the user has successfully registered.
Also sent in response to a LUSERS command.
Notes:
(?) is it server only or network wide? what exactly is it?
Note that if there are no unknown connections, this will not be sent.
Variations:
On certain servers this will not be returned.
See Also:
The following are sent in sequence on connection and in response to a LUSERS command:
251, 252, 253 (most servers), 254, 255, followed by either:
265 and 266, just 250, or a server notice
Returned From:
LUSERS
|
| RAW 254 (RPL_LUSERCHANNELS) Back to Top |
Format: 254 <num> :channels formed
Example: 254 6206 :channels formed
Network: All
Parameters:
<num> The number of channels currently formed
Info:
Sent to all clients once a connection has been established and the user has successfully registered.
Also sent in response to a LUSERS command.
Notes:
This number is for the entire network.
(?) does it include secret and private channels? (seems not)
(?) does it include &local channels? (seems so)
Note that if a network has no visible channels, this will not be sent.
See Also:
The following are sent in sequence on connection and in response to a LUSERS command:
251, 252, 253 (most servers), 254, 255, followed by either:
265 and 266, just 250, or a server notice
Returned From:
LUSERS
|
| RAW 255 (RPL_LUSERME) Back to Top |
Format: 255 :I have <user> clients and <serv> servers
Example: 255 :I have 1195 clients and 1 servers
Network: All
Parameters:
<user> The number of users connected to this server
<serv> The number of other servers connected to this server
Info:
Sent to all clients once a connection has been established and the user has successfully registered.
Also sent in response to a LUSERS command.
Notes:
These numbers are for the current server only.
Note that the server count does not include the current server, it is a count of all OTHER servers connected to it.
See Also:
The following are sent in sequence on connection and in response to a LUSERS command:
251, 252, 253 (most servers), 254, 255, followed by either:
265 and 266, just 250, or a server notice
Returned From:
LUSERS
|
| RAW 256 (RPL_ADMINME) Back to Top |
Format: 256 :Administrative info about <server>
Example: 256 :Administrative info about irc1.sprynet.com
Network: All
Info:
Returned in reply to an ADMIN request.
When replying to an ADMIN message, a server
is expected to use replies RPL_ADMINME
through to RPL_ADMINEMAIL and provide a text
message with each. For RPL_ADMINLOC1 a
description of what city, state and country
the server is in is expected, followed by
details of the institution (RPL_ADMINLOC2)
and finally the administrative contact for the
server (an email address here is REQUIRED)
in RPL_ADMINEMAIL
See Also:
The following are sent in order in reply to an ADMIN command-
256, 257, 258, 259
Returned From:
ADMIN
|
| RAW 257 (RPL_ADMINLOC1) Back to Top |
Format: 257 :<info>
Example: 257 :Emory University - Rollins School of Public Health
Network: All
Parameters:
<info> Administrative info: Server description. (line 1)
When replying to an ADMIN message, a server
is expected to use replies RPL_ADMINME
through to RPL_ADMINEMAIL and provide a text
message with each. For RPL_ADMINLOC1 a
description of what city, state and country
the server is in is expected, followed by
details of the institution (RPL_ADMINLOC2)
and finally the administrative contact for the
server (an email address here is REQUIRED)
in RPL_ADMINEMAIL
Info:
Returned in reply to an ADMIN request.
Notes:
This may contain e-mail, web addresses, nicknames, postal addresses, corporation names, etc.
You cannot rely on any specific information being in any single line or even the entire reply as a whole.
See Also:
The following are sent in order in reply to an ADMIN command:
256, 257, 258, 259
Returned From:
ADMIN
|
| RAW 258 (RPL_ADMINLOC2) Back to Top |
Format: 258 :<info>
Example: 258 :Tim Flavin (BigTim)
Network: All
Parameters:
<info> Administrative info. (line 2)
Info:
Returned in reply to an ADMIN request.
When replying to an ADMIN message, a server
is expected to use replies RPL_ADMINME
through to RPL_ADMINEMAIL and provide a text
message with each. For RPL_ADMINLOC1 a
description of what city, state and country
the server is in is expected, followed by
details of the institution (RPL_ADMINLOC2)
and finally the administrative contact for the
server (an email address here is REQUIRED)
in RPL_ADMINEMAIL
Notes:
This may contain e-mail, web addresses, nicknames, postal addresses, corporation names, etc.
You cannot rely on any specific information being in any single line or even the entire reply as a whole.
See Also:
The following are sent in order in reply to an ADMIN command:
256, 257, 258, 259
Returned From:
ADMIN
|
| RAW 259 (RPL_ADMINEMAIL) Back to Top |
Format: 259 :<info>
Example: 259 :Email att@undernet.org
Network: All
Parameters:
<info> Administrative info. (line 2)
Info:
Returned in reply to an ADMIN request.
When replying to an ADMIN message, a server
is expected to use replies RPL_ADMINME
through to RPL_ADMINEMAIL and provide a text
message with each. For RPL_ADMINLOC1 a
description of what city, state and country
the server is in is expected, followed by
details of the institution (RPL_ADMINLOC2)
and finally the administrative contact for the
server (an email address here is REQUIRED)
in RPL_ADMINEMAIL
Notes:
This may contain e-mail, web addresses, nicknames, postal addresses, corporation names, etc.
You cannot rely on any specific information being in any single line or even the entire reply as a whole.
See Also:
The following are sent in order in reply to an ADMIN command:
256, 257, 258, 259
Returned From:
ADMIN
|
| RAW 261 (RPL_TRACELOG) Back to Top |
Format: 261 :File <logfile> <debug level>
Example: 261 :
Network: Some
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See also:
200
201
202
203
204
205
206
207
208
209
210
262
Returned From:
TRACE
|
| RAW 262 (RPL_TRACEPING) Back to Top |
Format: 262 :
Example: 262 :
Network: Some
Info:
The RPL_TRACE* are all returned by the server in
response to the TRACE message. How many are
returned is dependent on the TRACE message and
whether it was sent by an operator or not. There
is no predefined order for which occurs first.
Replies RPL_TRACEUNKNOWN, RPL_TRACECONNECTING and
RPL_TRACEHANDSHAKE are all used for connections
which have not been fully established and are either
unknown, still attempting to connect or in the
process of completing the 'server handshake'.
RPL_TRACELINK is sent by any server which handles
a TRACE message and has to pass it on to another
server. The list of RPL_TRACELINKs sent in
response to a TRACE command traversing the IRC
network should reflect the actual connectivity of
the servers themselves along that path.
RPL_TRACENEWTYPE is to be used for any connection which does not fit in the other categories but is being displayed anyway.
RPL_TRACEEND is sent to indicate the end of the list.
Notes:
See also:
200
201
202
203
204
205
206
207
208
209
210
261
Returned From:
TRACE
|
| RAW 263 (RPL_LOAD2HI or RPL_TRYAGAIN) Back to Top |
Format 1: 263 :Server load is temporarily too heavy. Please wait a while and try again.
Example 1: 263 :Server load is temporarily too heavy. Please wait a while and try again.
Format 2: 263 :<command> :Please wait a while and try again.
Example 2: 263 :List :Please wait a while and try again.
Network: Some
Info:
Returned on some networks when the server has too much traffic to send a reply to a command.
Notes:
Although the text implies that it is the server's load in general that causes this reply,
in practice it seems to be sent on a user-to-user basis when a user attempts to request
too much information from a server.
For example, if you attempt too many STATS requests in a short period of time, you will get this error.
Format 2: When a server drops a command without processing it,
it MUST use the reply RPL_TRYAGAIN to inform the originating client.
|
| RAW 265 (RPL_LUSERSC) Back to Top |
Format: 265 :Current local users: <curr> Max: <max>
Example: 265 :Current local users: 2292 Max: 3017
Network: Some
Parameters:
<curr> The number of users connected to this server
<max> The highest number of users ever connected to this server
Info:
Returned on some networks during the connection process.
Also sent in response to a LUSERS command on these networks.
Notes:
These numbers are just for the current server.
The maximum count signifies the highest count of users the server has
had at any time since it was last rebooted.
Variations:
On many servers, these replies are not used- instead,
a 250 reply or server notice is sent.
See Also:
The following are sent in sequence on connection and in response to a LUSERS
command:
251, 252, 253 (most servers), 254, 255, followed by either:
265 and 266, just 250, or a server notice
Returned From:
LUSERS
|
| RAW 266 (RPL_LUSERSG) Back to Top |
Format: 266 :Current global users: <curr> Max: <max>
Example: 266 :Current global users: 21759 Max: 26097
Network: Some
Parameters:
<curr> The number of users connected to the entire network
<max> The highest number of users ever connected to the entire network
Info:
Returned on some networks during the connection process.
Also sent in response to a LUSERS command on these networks.
Notes:
These numbers are for the entire network.
The maximum count signifies the highest count of users that the entire NETWORK
has had at any time since the SERVER was last rebooted.
Different servers within the same net may return different values for this,
even though it is a network-wide value.
Variations:
On many servers, these replies are not used- instead, a 250 reply or server notice is sent.
See Also:
The following are sent in sequence on connection and in response to a LUSERS command:
251, 252, 253 (most servers), 254, 255, followed by either:
265 and 266, just 250, or a server notice
Returned From:
LUSERS
|
| RAW 271 (RPL_SILELIST) Back to Top |
Format: 271 <nick> <mask>
Example: 271 DeafGuy *!*@*.aol.com
Network: Some
Parameters:
<nick> The nickname whose SILENCE list is being viewed.
<mask> An entry in the user's SILENCE list.
Info:
These are returned when listing your or another user's SILENCE list.
Notes:
You can view another user's SILENCE list, but you will only see masks
that your current server knows about.
Your server will only know about an entry if someone matching that
entry sent a message via your server to that person.
For example, if a user has a *!*@*.aol.com entry and you are on AOL,
message the user before checking their SILENCE list
to be sure that your server knows about any silence list entries.
See Also:
The following are sent in response to a SILENCE list request:
271 (zero or more lines), 272
Returned From:
SILENCE
|
| RAW 272 (RPL_ENDOFSILELIST) Back to Top |
Format: 272 :End of Silence List
Example: 272 :End of Silence List
Network: Some
Info:
This is returned at the end of a SILENCE list.
Advanced:
Even if you requested another user's SILENCE list, their nick will not
be in the usual part of the raw reply.
However, the user's nickname WILL be in the reply where YOUR nick would
usually be. ($1 in mIRC remotes.)
See Also:
The following are sent in response to a SILENCE list request:
271 (zero or more lines), 272
Returned From:
SILENCE
|
| RAW 275 (RPL_STATSDLINE) Back to Top |
Format: 275 :
Example: 275 :
Network: Undernet Extension
Info:
See Also:
Returned From:
STATS
|
| RAW 280 (RPL_GLIST) Back to Top |
Format: 280 <address> <timestamp> <reason>
Example: 280 *@www.* 902579316 Do not IRC from WWW machines
Network: Undernet
Parameters:
<address> Address mask matched against userhosts.
<timestamp> Timestamp for when the ban will expire. (??)
<reason> Reason for the ban.
Info:
A series of these are sent in reply to a GLINE list.
Notes:
GLINE by itself (or with a mask) lists matching G-lines,
which are bans global to an entire network.
Users who match a G-line will be denied access to all servers on the network.
Most G-lines last for a relatively short period of time, such as a week.
See Also:
The following are sent in response to a GLINE listing on Undernet:
280 (one or more lines), 281
Returned From:
GLINE
|
| RAW 281 (RPL_ENDOFGLIST) Back to Top |
Format: 281 :End of G-line List
Example: 281 :End of G-line List
Network: Undernet
Info:
This is returned at the end of a GLINE list.
See Also:
The following are sent in response to a GLINE listing on Undernet:
280 (one or more lines), 281
Returned From:
GLINE
|
| RAW 290 (RPL_HELPHDR) Back to Top |
Format: 290 :<num> ***** <topic> *****
Example: 290 :0 ***** .ircd Help. *****
Network: DALnet
Parameters:
<num> A number, always seemed to be zero. Not sure what it's purpose. (?)
<topic> A help topic.
Info:
This is sent at the beginning of a HELPOP help request,
stating the help topic you are receiving info on.
See Also:
The following raws are used by HelpOp:
290, 291, 292, 293, 294, 295
Returned From:
HELPOP
|
| RAW 291 (RPL_HELPOP) Back to Top |
Format: 291 :<text>
Example: 291 :.NickServ. permits users to .'register'. a nickname, and stop
Network: DALnet
Parameters:
<text> Text returned by DALnet's HelpOp.
Info:
This is used for the main section of a HELPOP help response,
and contains the actual help info.
See Also:
The following raws are used by HelpOp:
290, 291, 292, 293, 294, 295
Returned From:
HELPOP
|
| RAW 292 (RPL_HELPTLR) Back to Top |
Format: 292 : ***** Go to .#dalnethelp. if you have any further questions *****
Example: 292 : ***** Go to .#dalnethelp. if you have any further questions *****
Network: DALnet
Info:
This is sent at the end of any HELPOP help request.
See Also:
The following raws are used by HelpOp:
290, 291, 292, 293, 294, 295
Returned From:
HELPOP
|
| RAW 293 (RPL_HELPHLP) Back to Top |
Format: 293 :<text>
Example: 293 :If you need help on DALnet services, try...
Network: DALnet
Parameters:
<text> Text returned by DALnet's HelpOp.
Info:
A series of these are returned as a generic response to an unrecognized
HELPOP request on DALnet, or in response to 'HELPOP index'.
See Also:
The following raws are used by HelpOp:
290, 291, 292, 293, 294, 295
Returned From:
HELPOP
|
| RAW 294 (RPL_HELPFWD) Back to Top |
Format: 294 :Your help-request has been forwarded to Help Operators
Example: 294 :Your help-request has been forwarded to Help Operators
Network: DALnet
Info:
This is sent at the end of a HELPOP request when your request was forwarded
to Help Operators.
Notes:
A request will be forwarded if no info was available,
or you specifically requested it to be forwarded.
See HelpOp on DALnet for details.
See Also:
The following raws are used by HelpOp:
290, 291, 292, 293, 294, 295
Returned From:
HELPOP
|
| RAW 295 (RPL_HELPIGN) Back to Top |
Format: Undocumented
Example:
Network: DALnet
Info:
Notes:
See HelpOp on DALnet for details.
See Also:
The following raws are used by HelpOp:
290, 291, 292, 293, 294, 295
Returned From:
HELPOP
|
| RAW 298 (RPL_NEWNICK) Back to Top |
Format: 298 <nick> :Nickname conflict has been resolved
Example: 298 pai :Nickname conflict has been resolved
Network: ChatSpace
Parameters:
<nick> The new nickname you have selected
Info:
This is returned when you have chosen a new nickname in response to a nickname
conflict.
Notes:
This seems to be specific to servers running ChatSpace server software.
See Also:
The following raws relate to nickname conflicts on ChatSpace:
298, 510, 512
Returned From:
NICK
|
|