Format: 301 <nick> :<away>
Example: 301 SunSword :auto-away [Since: Aug 6 4:38 PM CDT]
Network: Most
Parameters:
<nick> Nickname of a user.
<away> Information (provided by the user) on why he or she is (or was, for WHOWAS) away.
Info:
This is sent to tell you that a given user is away. (set using the AWAY command.)
It will be returned, if applicable, for a WHOIS or WHOWAS request,
and also if you send a PRIVMSG to a user that is away.
Notes:
The away information is provided by the user and may contain anything.
This is sent, as a reminder, when you send a PRIVMSG to a user,
but will not be returned for a NOTICE, INVITE, or any other sort of interaction.
Variations:
A few servers and networks have started to disable the away feature,
and those networks would of course not return this numeric.
See Also:
The following are sent in response to a WHOIS request:
311, 319 (if applicable),
312, 301 (if applicable),
313 (if applicable), 317 (if applicable),
318
The following are sent in response to a WHOWAS request:
314,
312, 301 (if applicable),
369,
Returned From:
WHOIS, WHOWAS, PRIVMSG
| RAW 302 (RPL_USERHOST) Back to Top |
Format: 302 :<userhosts>
Example: 302 :Gamera=-keekee@dt091n15.san.rr.com pai=+pain@d2052192151.imsday.com
Network: All
Parameters:
<userhosts> A series of USERHOST replies.
Info:
This is returned in reply to a USERHOST request.
Notes:
Each reply is formatted as nickname=+userid@host. 'nickname' is the user's nickname,
'userid' is their userid (identd) and 'host' is their host address. + means that they are here (not away),
and will be a - (hyphen) if they are away.
A USERHOST reply will contain from zero to five replies. When you send the USERHOST request you can include
up to five nicks; the reply will only contain info on the nicks that exist, if any. If none of the nicks
you requested exist, a blank reply will be returned.
Note that the USERHOST reply will contain the proper case for each nickname, regardless of the actual
case used in the original request.
Variations:
Some networks allow more than five nicknames to be requested in a USERHOST request.
If so, the USERHOST replies will be broken across multiple lines.
(not sure if they are compacted five to a line or one line for each five nicks requested...?)
Undernet will return a 401 reply (no such nickname) for each user that you request a userhost for
that does not exist. The USERHOST reply will still be returned with the missing users not present.
Returned From:
USERHOST
|
| RAW 303 (RPL_ISON) Back to Top |
Format: 303 :<nicknames>
Example: 303 Clarice lipstick markNY sweetbabe
Network: All
Parameters:
<nicknames> Nicknames of users that are on IRC.
Info:
This is sent in reply to an ISON request. The reply contains all nicknames that are on IRC out
of the set of nicknames originally requested.
For example, if 'ISON a b c d' was sent, and b and d are on IRC,
then this reply will return 'b d' for 'nicknames'.
Notes:
Note that the ISON reply will contain the proper case for each nickname,
regardless of the actual case used in the original request.
If no nicknames are online from the requested list, a blank 303 reply is returned.
This reply is used by notify lists and features in most clients, including mIRC,
so be careful when using this in a script.
Returned From:
ISON
|
| RAW 305 (RPL_UNAWAY) Back to Top |
Format: 305 :You are no longer marked as being away
Example: 305 :You are no longer marked as being away
Network: All
Info:
This is returned when you return from being AWAY. (by setting a blank away reason.)
Notes:
This reply does not make any mention of why you were AWAY or for how long,
it merely informs you that you are no longer marked as AWAY.
See Also:
When you set an AWAY message, 306 is returned.
Returned From:
AWAY
|
| RAW 306 (RPL_NOWAWAY) Back to Top |
Format: 306 :You have been marked as being away
Example: 306 :You have been marked as being away
Network: All
Info:
This is returned when you set yourself AWAY.
Notes:
This reply does not make any mention of your AWAY reason,
it merely informs you that your AWAY message has been accepted.
See Also:
When you return from away, 305 is returned.
Returned From:
AWAY
|
| RAW 307 (RPL_USERIP) Back to Top |
Format: 307 :<userips>
Example: 307 :Spekkio=-Spekkio@209.86.144.138 T_A=-~tomandre@195.204.242.136
Network: Undernet
Parameters:
<userips> A series of USERIP replies.
Info:
This is returned in reply to a USERIP request.
Notes:
The main difference between this and USERHOST is that a numeric ip is always returned,
even if the user has a resolved (normal) host.
Each reply is formatted as nickname=+userid@ip. 'nickname' is the user's nickname,
'userid' is their userid (identd) and 'ip' is their numeric ip.
+ means that they are here (not away), and will be a - (hyphen) if they are away.
A USERIP reply will contain from zero to five replies.
When you send the USERIP request you can include up to five nicks;
the reply will only contain info on the nicks that exist, if any.
If none of the nicks you requested exist, a blank reply will be returned.
Note that the USERIP reply will contain the proper case for each nickname,
regardless of the actual case used in the original request.
Also note that a 401 reply (no such nickname) will also be returned for each user
that you request a USERIP for that does not exist.
The USERIP reply will still be returned with the missing users not present.
See Also:
The following raw is used for USERHOST:
302
Returned From:
USERIP
|
| RAW 310 (RPL_WHOISHELPOP) Back to Top |
Format: 310 <nick> :looks very helpful
Example: 310 HelpfulOper :looks very helpful
Network: DALnet
Parameters:
<nick> Nickname of a DALnet helpop or IRC operator.
Info:
This is sent as part of a reply to a WHOIS request on DALnet, if the user is a helpop or,
sometimes, if the user is an IRC operator.
Notes:
If you have details on the exact times this message may appear, please contact paiRC.
See Also:
The following are sent in response to a WHOIS request-
311, 319 (if applicable),
312, 301 (if applicable),
313 (if applicable), 310 (if applicable),
317 (if applicable), 318
Returned From:
WHOIS
|
| RAW 311 (RPL_WHOISUSER) Back to Top |
Format: 311 <nick> <username> <address> * :<info>
Example: 311 Gamera keekee dt091n15.san.rr.com * :Justy Ueki Tylor
Network: All
Parameters:
<nick> Nickname of a user you WHOIS'd.
<username> Username (identd) of a user.
<address> The user's full address. (IP or resolved)
<info> The user's 'real name' info.
Info:
This is sent as part of a reply to a WHOIS request.
It contains the user's identd and address as well as their 'real name' information as given by them.
(this could be anything that the user chooses.)
Notes:
To get the user's full address, take the nick, add an exclamation point,
add the username, add an at-sign, and add the address.
So for the above example you'd get Gamera!keekee@dt091n15.san.rr.com.
See Also:
The following are sent in response to a WHOIS request:
311, 319 (if applicable),
312, 301 (if applicable),
313 (if applicable), 310 (if applicable),
317 (if applicable), 318
Returned From:
WHOIS
|
| RAW 312 (RPL_WHOISSERVER) Back to Top |
Format: 312 <nick> <server> :<info>
Example: 312 DrDthmtch NewBrunswick.NJ.US.Undernet.Org :[204.127.145.17] AT&T WorldNet IRC Chat Service
Network: All
Parameters:
<nick> Nickname of a user you WHOIS'd.
<server> The server that the user is connected to.
<info> Some information about the server the user is connected to.
Info:
This is sent as part of a reply to a WHOIS request. It contains the server a user is connected to.
Notes:
The format of the info section may contain anything and is usually of no importance.
See Also:
The following are sent in response to a WHOIS request:
311, 319 (if applicable),
312, 301 (if applicable),
313 (if applicable), 310 (if applicable),
317 (if applicable), 318
Returned From:
WHOIS
Raw 312 - WHOWAS server
Info:
Format: 312 <nick> <server> :<signoff>
Example: 312 mspai los-angeles.ca.us.undernet.org :Thu Aug 6 16:00:35 1998
Network: All
Parameters:
<nick> Nickname of a user you WHOWAS'd.
<server> The server that the user was connected to.
<signoff> The date and time the user signed off or changed nicknames.
Info:
This is sent as part of a reply to a WHOWAS request. It contains the server a user was
connected to, as well as information on when they last were on.
Notes:
The format of the signoff section will not necessarily be in the same format on all servers.
The time should correspond to when the user signed off or changed nicknames.
See Also:
The following are sent in response to a WHOWAS request:
314,
312, 301 (if applicable),
369
Returned From:
WHOWAS
|
| RAW 313 (RPL_WHOISOPERATOR) Back to Top |
Format: 313 <nick> :is an IRC Operator
Example: 313 DieLamers :is an IRC Operator
Network: All
Parameters:
<nick> Nickname of an IRC operator.
Info:
This is sent as part of a reply to a WHOIS request, if the user is an IRC operator.
Variations:
Some servers may change this message or even use if for entirely different reasons, such as
helpers or other officials. The best way to handle this numeric is simply to display it verbatim.
(if scanning for operator status, check for the word 'operator' being present.)
See Also:
The following are sent in response to a WHOIS request:
311, 319 (if applicable),
312, 301 (if applicable),
313 (if applicable), 310 (if applicable),
317 (if applicable), 318
Returned From:
WHOIS
|
| RAW 314 (RPL_WHOWASUSER) Back to Top |
Format: 314 <nick> <username> <address> * :<info>
Example: 314 paipai goddess 12.10.230.191 * :pai-type person
Network: All
Parameters:
<nick> Nickname of a user you WHOWAS'd.
<username> Username (identd) of a user.
<address> The user's full address. (IP or resolved)
<info> The user's "real name" info.
Info:
This is sent as part of a reply to a WHOWAS request. It contains the user's identd and
address as well as their "real name" information as given by them.
(this could be anything that the user chose.)
Notes:
To get the user's full address, take the nick, add an exclamation point,
add the username, add an at-sign, and add the address.
So for the above example you'd get paipai!goddess@12.10.230.191.
Remember that this info is who a user WAS, so if they reconnect later,
the info may be totally different.
See Also:
The following are sent in response to a WHOWAS request:
314,
312, 301 (if applicable),
369
Returned From:
WHOWAS
|
| RAW 315 (RPL_ENDOFWHO) Back to Top |
Format: 315 <request> :End of /WHO list.
Example: 315 #channel :End of /WHO list.
Network: All
Parameters:
<request> The WHO request that was made.
Info:
This is sent at the end of a WHO request.
Notes:
The 'request' parameter will be the exact query you sent, whether a single text string,
wildcards, a channel, etc.
If a single WHO request returns information on multiple users or sets of users,
this numeric is returned only once, at the end of all replies.
Although the other parts of a WHO reply contain the proper case of nicknames,
channels, and other information, this reply will contain the case of the request
exactly as you made it.
See Also:
The following are sent in response to a WHO request:
352 (zero or more lines), 315
Returned From:
WHO
|
| RAW 317 (RPL_WHOISIDLE) Back to Top |
Format: 317 <nick> <seconds> <signon> :<info>
Example: 317 TheUser 1649 902430973 :seconds idle, signon time
Network: All
Parameters:
<nick> Nickname of a user you WHOIS'd.
<seconds> Number of seconds user is idle.
<signon> A timestamp representing when the user signed on to IRC.
<info> A quick description of the previous two parameters.
Info:
This is sent as part of a reply to a WHOIS request, if the user is on the same server as you.
It includes the number of seconds the user is idle as well as when they signed on to IRC.
Notes:
Idle time is measured from the last time the user sent a PRIVMSG.
No other commands will reset a user's idle time.
The signon time can be converted to a standard date and time using $asctime().
The 'info' parameter will not change from WHOIS to WHOIS, but it may differ between
servers or networks. It exists solely to help document the purpose of the values in the reply.
Advanced:
Although this only appears when you are on the same server as a user,
you can still get this information from another server. Simply send WHOIS user user
(with the nickname listed twice, as shown) and the WHOIS reply will be sent from the
user's server and not taken from the information on your current server.
Variations:
A few networks may not return the signon time, but just the idle time.
Most major networks return both, however.
See Also:
The following are sent in response to a WHOIS request:
311, 319 (if applicable),
312, 301 (if applicable),
313 (if applicable), 317 (if applicable),
318
Returned From:
WHOIS
|
| RAW 318 (RPL_ENDOFWHOIS) Back to Top |
Format: 318 <request> :End of /WHOIS list.
Example: 318 pai,mspai :End of /WHOIS list.
Network: All
Parameters:
<request> The WHOIS request that was made.
Info:
This is sent at the end of a WHOIS request.
Notes:
The 'request' parameter will be the exact query you sent, whether a single nickname,
multiple nicknames, or a wildcard string.
If a single WHOIS request returns information on multiple users, this numeric is
returned only once, at the end of all replies.
Although the other parts of a WHOIS reply contain the proper case of nicknames,
this reply will contain the case of the nickname(s) exactly as you originally requested them.
See Also:
The following are sent in response to a WHOIS request:
311, 319 (if applicable),
312, 301 (if applicable),
313 (if applicable), 317 (if applicable),
318
Returned From:
WHOIS
|
| RAW 319 (RPL_WHOISCHANNELS) Back to Top |
Format: 319 <nick> :<channels>
Example: 319 pai :@#peace&protection
Network: All
Parameters:
<nick> Nickname of a user you WHOIS'd.
<channels> One or more channels a user is on.
Info:
This is sent as part of a reply to a WHOIS request. It contains the channels a user is on.
If the user is opped on a channel, the channel name will be prefixed with a @. Likewise,
if a user is opped on a channel, it will be prefixed with a +.
Notes:
Note that secret and private channels will not be listed.
This is the only part of a WHOIS reply that may appear multiple times for a given user.
If a user is on a large number of channels, multiple 319 replies will be returned to
contain all of the channels. This normally should not occur, except for special exceptions
such as X and W on Undernet.
Advanced:
Some networks support the usermode +d, which makes a user "deaf", or unable to see channel text.
If a user is deaf, all channels listed in the WHOIS reply will be prefixed with a -. (hyphen)
Variations:
Certain networks may return @+ prefixing a channel if the user is both opped and voiced on the channel.
Not all networks support deaf mode. (see advanced)
See Also:
The following are sent in response to a WHOIS request-
311, 319 (if applicable),
312, 301 (if applicable),
313 (if applicable), 317 (if applicable),
318
Returned From:
WHOIS
|
| RAW 321 (RPL_LISTSTART) Back to Top |
Format: 321 Channel :Users Name
Example: 321 Channel :Users Name
Network: All
Info:
Sent at the beginning of a LIST reply, before the channels are listed.
Variations:
The actual text of this reply may vary slightly.
See Also:
The following are returned for a LIST request:
321, 322 (zero or more),
323
Returned From:
LIST
|
| RAW 322 (RPL_LIST) Back to Top |
Format: 322 <channel> <users> :<topic>
Example: 322 #chat 12 :The fire in one's soul defines who they are
Network: All
Parameters:
<channel> A channel name.
<users> Number of users on the channel.
<topic> The current channel topic.
Info:
This is returned for each channel in a LIST reply.
Notes:
The user count includes all users, invisible or otherwise.
If no topic is currently set, none will be given, although the colon will still be included.
If no channels match a LIST request, no 322 replies will be returned.
See Also:
The following are returned for a LIST request-
321, 322 (zero or more),
323
Returned From:
LIST
|
| RAW 323 (RPL_LISTEND) Back to Top |
Format: 323 :End of /LIST
Example: 323 :End of /LIST
Network: All
Info:
Sent at the end of a LIST reply, after all matching channels are listed.
See Also:
The following are returned for a LIST request-
321, 322 (zero or more),
323
Returned From:
LIST
|
| RAW 324 (RPL_CHANNELMODEIS) Back to Top |
Format: 324 <channel> <mode>
Example: 324 #mychannel +tn
Network: All
Parameters:
<channel> A channel name.
<mode> The current channel modes.
Info:
This is returned for a MODE request.
Notes:
If the channel has no modes, a single + will be returned.
Keys and limits, if present, will be returned in the MODE reply.
Keys will not be returned in the mode reply if you are not in the channel, of course.
Variations:
Undernet does not return the channel key in a MODE reply unless you are actually opped on the channel.
Some networks do not return the channel limit in a MODE reply unless you are actually on the channel.
See Also:
The following are returned for a MODE reply:
324, 329 (on most networks)
Returned From:
MODE
|
| RAW 325 (RPL_UNIQOPIS) Back to Top |
Format: 325 <channel> <nick>
Example: 325 #mychannel Merlin
Network: All
Parameters:
<channel> A channel name.
<nick> The name of the nick on the channel.
Info:
Notes:
Variations:
See Also:
Returned From:
|
| RAW 328 (RPL_???) Back to Top |
Format: 328 <channel> :<url>
Example: 328 #square :http://www.square.org
Network: DALnet
Parameters:
<channel> A channel you have recently joined.
<url> The ChanServ URL set for that channel.
Info:
This is sent to you by ChanServ when you join a registered channel.
Notes:
Unlike the other information you receive when you join a channel, this raw depends
on how lagged you are to DALnet services.
|
| RAW 329 (RPL_CREATIONTIME) Back to Top |
Format: 329 <channel> <time>
Example: 329 #peace&protection 884921151
Network: Most
Parameters:
<channel> A channel name.
<time> The time the channel was created.
Info:
This is returned as part of a MODE request, giving you the time the channel was created.
Notes:
Use $asctime() to convert 'time' to a readable value.
Variations:
Some networks may not return this reply.
See Also:
The following are returned for a MODE reply:
324, 329 (on most networks)
Returned From:
MODE
|
| RAW 331 (RPL_NOTOPIC) Back to Top |
Format: 331 <channel> :No topic is set.
Example: 331 #hello :No topic is set
Network: All
Parameters:
<channel> A channel name.
Info:
This is returned for a TOPIC request if the channel has no current topic.
On JOIN, if a channel has no topic, this is not returned. Instead, no topic-related
replies are returned.
See Also:
The following are returned for a TOPIC reply, if a topic actually exists:
332, 333
Returned From:
TOPIC
|
| RAW 332 (RPL_TOPIC) Back to Top |
Format: 332 <channel> :<topic>
Example: 332 #mishscript : http://www.mishscript.de
Network: All
Parameters:
<channel> A channel name.
<topic> The current topic on the channel.
Info:
This is returned for a TOPIC request or when you JOIN, if the channel has a topic.
Notes:
If the channel does not have a topic, then TOPIC will return a 331 reply, and JOIN
will not return anything for the topic.
See Also:
The following are returned for a TOPIC reply:
332, 333
The following is returned for a TOPIC request, if no topic exists-
The following are returned, in sequence, when joining a channel-
332 (if a topic is set), 333 (if a topic is set),
353 (one or more), 366
Note that mIRC will also request the channel MODE (replies 324, 329) when joining a channel.
Returned From:
TOPIC, JOIN
|
| RAW 333 (RPL_TOPICWHOTIME) Back to Top |
Format: 333 <channel> <nickname> <time>
Example: 333 #boredom IAmBored 902508764
Network: Most
Parameters:
<channel> A channel name.
<nickname> User who last set the channel topic.
<time> The time the user set the current channel topic.
Info:
This is returned for a TOPIC request or when you JOIN, if the channel has a topic.
Notes:
Use $asctime() to convert 'time' to a readable value.
If the channel does not have a topic, then TOPIC will return a 331 reply, and JOIN
will not return anything for the topic.
Variations:
Certain servers or networks may not return this reply, but the majority of them will.
See Also:
The following are returned for a TOPIC reply:
332, 333
The following is returned for a TOPIC request, if no topic exists:
331
The following are returned, in sequence, when joining a channel-
332 (if a topic is set), 333 (if a topic is set)
353 (one or more), 366
Note that mIRC will also request the channel MODE (replies 324, 329) when joining a channel.
Returned From:
TOPIC, JOIN
|
| RAW 342 (RPL_SUMMONING) Back to Top |
Format: 342 <nick> " :Summoning user to IRC
Example: 342 person Summoning user to IRC
Network: All
Parameters:
<nick> Nickname of a user you summon.
Info:
Returned by a server answering a SUMMON message to indicate that it is summoning that user
Returned From:
SUMMON
|
| RAW 341 (RPL_INVITING) Back to Top |
Format: 341 <nick> <channel>
Example: 341 person #mychannel
Network: All
Parameters:
<nick> Nickname of a user you INVITE'd.
<channel> Channel they were invited to.
Info:
This is returned when you successfully INVITE a user to a channel, to inform you that
the INVITE was sent.
Returned From:
INVITE
|
| RAW 346 (RPL_INVITELIST) Back to Top |
Format: 346 <channel> <invitemask>
Example: 346 #mychannel *.com
Network: All
Parameters:
<channel> Channel they were invited to.
<invitemask> Hostmask
Info:
When listing the 'invitations masks' for a given channel,
a server is required to send the list back using the
RPL_INVITELIST and RPL_ENDOFINVITELIST messages. A
separate RPL_INVITELIST is sent for each active mask.
After the masks have been listed (or if none present) a
RPL_ENDOFINVITELIST MUST be sent.
Returned From:
MODE
|
| RAW 347 (RPL_ENDOFINVITELIST) Back to Top |
Format: 347 <channel> :End of channel invite list
Example: 347 #mychannel End of channel invite list
Network: All
Parameters:
<channel> Channel they were invited to.
<invitemask> Hostmask
Info:
When listing the 'invitations masks' for a given channel,
a server is required to send the list back using the
RPL_INVITELIST and RPL_ENDOFINVITELIST messages. A
separate RPL_INVITELIST is sent for each active mask.
After the masks have been listed (or if none present) a
RPL_ENDOFINVITELIST MUST be sent.
Returned From:
MODE
|
| RAW 348 (RPL_EXCEPTLIST) Back to Top |
Format: 348 <channel> <exceptionmask>
Example: 348 #mychannel *.aol.com
Network: All
Parameters:
<channel> Channel they were listing exception from.
<exceptionmask> Hostmask
Info:
When listing the 'exception masks' for a given channel,
a server is required to send the list back using the
RPL_EXCEPTLIST and RPL_ENDOFEXCEPTLIST messages. A
separate RPL_EXCEPTLIST is sent for each active mask.
After the masks have been listed (or if none present)
a RPL_ENDOFEXCEPTLIST MUST be sent.
Returned From:
MODE
|
| RAW 349 (RPL_ENDOFEXCEPTLIST) Back to Top |
Format: 349 <channel> :End of channel exception list
Example: 349 #mychannel End of channel exception list
Network: All
Parameters:
<channel> Channel they were listing exception from.
Info:
When listing the 'exception masks' for a given channel,
a server is required to send the list back using the
RPL_EXCEPTLIST and RPL_ENDOFEXCEPTLIST messages. A
separate RPL_EXCEPTLIST is sent for each active mask.
After the masks have been listed (or if none present)
a RPL_ENDOFEXCEPTLIST MUST be sent.
Returned From:
MODE
|
| RAW 351 (RPL_VERSION) Back to Top |
Format: 351 <version>.<debug> <server> :<info>
Example: 351 u2.10.04.resolv8. NewBrunswick.NJ.US.Undernet.Org :M20B>ceEIKl2MptX
Network: All
Parameters:
<version> The base version, plus any patches, of IRC the server is running.
<debug> Any debug modes the server is running.
<server> The name of the server.
<info> Any additional info. (?)
Info:
This is returned when you request the VERSION of a server.
Notes:
Returned From:
VERSION
|
| RAW 352 (RPL_WHOREPLY) Back to Top |
Format: 352 <channel> <username> <address> <server> <nick> <flags> :<hops> <info>
Example: 352 #peace&protection IsaacHayes sdn-ar-004mokcitP324.dialsprint.net NewBrunswick.NJ.US.Undernet.Org DrDthmtch H+ :4 Isaac Hayes (QuickScript.ml.org)
Network: All
Parameters:
<channel> A channel the user is on, or * for none visible.
<username> The username (identd) of the user.
<address> The IP or resolved address (host) of the user.
<server> The server the user is connected to.
<nick> The nickname of the user.
<flags> Flags for a user regarding IRCop status, away status, channel op status, etc.
<hops> The number of hops from your server the the user's server.
<info> The user's "real name" info.
Info:
This is returned by a WHO request, one line for each user that is matched.
Notes:
If the user is on multiple channels, only one will be returned. If the WHO was performed on a channel,
this will always be the channel that was requested. Private and secret channels are not returned unless
you are on them as well.
The flags will always start with H (here) if the user is not away, or G (gone) if the user is away.
This is followed by a * (asterisk) if the user is an IRCop, then a @ or + if the user is opped or
voiced on the listed channel. This is then followed by a d (lowercase) if the user is deaf,
such as X and W on Undernet.
The hop count ('hops') is a count of the number of servers between your server and their server.
If they are on your server, this will be 0. If they are on a server directly connected to your server,
this is 1. If there is one intervening server, this is 2, etc.
The info (real name) is provided by the user on signon and may contain anything.
Variations:
Not all servers support deaf mode.
See Also:
The following are sent in response to a WHO request:
352 (zero or more lines), 315
Returned From:
WHO
|
| RAW 353 (RPL_NAMREPLY) Back to Top |
Format: 353 = <channel> :<names>
Example: 353 = #funfactory :chattie dizz takshaka poshgal @LDI Aldebaran Sweet2 James54
Network: All
Parameters:
<channel> The channel you are receiving a NAMES list for.
<names> Nicknames of users on the channel.
Info:
This is returned for a NAMES request for a channel, or when you initially join a channel.
It contains a list of every user on the channel.
Notes:
If a user is opped on a channel, their nickname will be prefixed with a @. If voiced,
it will be prefixed with a +.
Note that a NAMES reply for a channel you are not on will not include invisible users.
If a NAMES reply cannot fit into a single 353 reply, multiple replies are returned until
all users are listed.
Advanced:
If a NAMES request returns only a 366 (end of NAMES) reply without any 353 replies,
then the channel is secret or private, or does not exist.
If a NAMES request returns a single 353 reply that contains no nicknames, then the channel
exists and is not secret or private, however all users on the channel are invisible.
Variations:
Certain networks may return @+ prefixing a nickname if the user is both opped and
voiced on the channel.
See Also:
The following are returned for a NAMES request:
353 (zero or more), 366
The following are returned, in sequence, when joining a channel:
332 (if a topic is set), 333 (if a topic is set),
353 (one or more), 366
Note that mIRC will also request the channel MODE (replies 324324, 329) when joining a channel.
Returned From:
NAMES, JOIN
|
| RAW 364 (RPL_LINKS) Back to Top |
Format: 364 <server> <hub> :<hops> <info>
Example: 364 SaltLake.UT.US.UnderNet.Org Charlotte-R.NC.US.Undernet.org :5 P10 [207.173.16.33] [irc.aros.net] ArosNet UnderNet Se
Network: All
Parameters:
<server> A server name.
<hub> The server that this server is connected to.
<hops> The number of servers between your server and this server.
Info:
A series of these are sent in reply to a LINKS request.
Notes:
Remember that each server will be listed once in the 'server' section, but since 'hub'
is the server connected to, some servers will be listed multiple times in that column,
and some (that are not hubs) will not be listed at all.
The hop count will be 0 for your current server, 1 for servers directly connected to your server,
2 for servers that have one server between your server and them, etc.
See Also:
In response to a LINKS request, the following are sent:
364 (zero or more), 365
Returned From:
LINKS
|
| RAW 365 (RPL_ENDOFLINKS) Back to Top |
Format: 365 <mask> :End of /LINKS list.
Example: 365 * :End of /LINKS list.
Network: All
Parameters:
<mask> The mask requested in the LINKS command.
Info:
This is sent at the end of a LINKS list.
Notes:
If you use LINKS with a mask (such as LINKS *.net) then only matching servers are sent,
and your mask will be returned in this reply. If you don't use a mask, 'mask' will be a *. (asterisk)
See Also:
In response to a LINKS request, the following are sent:
364 (zero or more), 365
Returned From:
LINKS
|
| RAW 366 (RPL_ENDOFNAMES) Back to Top |
Format: 366 <channel> :End of /NAMES list.
Example: 366 #california :End of /NAMES list.
Network: All
Parameters:
<channel> The channel you were receiving a NAMES list for.
Info:
This is returned at the end of a NAMES list, after all visible names are returned.
See Also:
The following are returned for a NAMES request:
353 (zero or more), 366
The following are returned, in sequence, when joining a channel:
332 (if a topic is set), 333 (if a topic is set),
353 (one or more), 366
Note that mIRC will also request the channel MODE (replies 324324, 329) when joining a channel.
Returned From:
NAMES, JOIN
|
| RAW 367 (RPL_BANLIST) Back to Top |
Format: 367 <channel> <ban> <nick> <time>
Example: 367 #mIRC-Scripts *!*RPG@*.dialsprint.net |AZ| 902510598
Network: All
Parameters:
<channel> The channel the bans are on.
<ban> A ban on the channel.
<nick> The user who set the ban.
<time> The time the ban was set.
Info:
A series of these are sent when a channel banlist is requested. (with MODE #chan +b.)
Notes:
Use $asctime() to convert 'time' to a readable value.
For an empty banlist, no 367 replies will be returned- only the final 368 numeric.
Variations:
Some older servers may not support the 'nick' and 'time' parameters.
See Also:
When a banlist is requested, the following are returned:
367 (zero or more), 368
Returned From:
MODE
|
| RAW 368 (RPL_ENDOFBANLIST) Back to Top |
Format: 368 <channel> :End of Channel Ban List
Example: 368 #hentai :End of Channel Ban List
Network: All
Parameters:
<channel> A channel you just viewed a banlist for.
Info:
This is sent at the end of a channel banlist, when requested. (with MODE #chan +b.)
See Also:
When a banlist is requested, the following are returned-
367 (zero or more), 368
Returned From:
MODE
|
| RAW 369 (RPL_ENDOFWHOWAS) Back to Top |
Format: 369 <request> :End of WHOWAS
Example: 369 HeLeft :End of WHOWAS
Network: All
Parameters:
<request> The WHOWAS request that was made.
Info:
This is sent at the end of a WHOWAS request.
Notes:
The 'request' parameter will be the exact query you sent, whether a single nickname
or multiple nicknames.
If a single WHOWAS request returns information on multiple users, this numeric is
returned only once, at the end of all replies.
Although the other parts of a WHOWAS reply contain the proper case of nicknames,
this reply will contain the case of the nickname(s) exactly as you originally requested them.
See Also:
The following are sent in response to a WHOWAS request:
314, 312 (if applicable),
301, 369
Returned From:
WHOWAS
|
| RAW 371 (RPL_INFO) Back to Top |
Format: 371 :<info>
Example: 371 :The UnderNet code is based upon version 2.8.10.
Network: All
Parameters:
<info> A line of information.
Info:
A series of these are sent in reply to an INFO request.
Notes:
An INFO reply usually contains similar information, on any server or network,
about the origins of IRC.
Since the information is usually the same, but not guaranteed to be in any format
or of any use, a script should just display these as-is.
See Also:
The following are sent for an INFO reply:
371 (multiple lines), 374
Returned From:
INFO
|
| RAW 372 (RPL_MOTD) Back to Top |
Format: 372 :- <info>
Example: 372 :- NO BOTS! *** Ports: 6660-6669 *** Problems? --> irc@irc.amug.org
Network: Most
Parameters:
<info> A single line from the server's message of the day.
Info:
This is sent in reply to a MOTD request or on connection. In most cases,
multiple replies will be sent, one for each line in the MOTD.
Variations:
Some servers do not include the hyphen at the beginning of MOTD replies, so you
cannot rely on the actual text starting at the second word.
Some servers use a different numeric for MOTD replies, such as 377 or 378.
The format and purpose remains the same, however.
See Also:
The following are sent for a Message of the Day:
375 (usually), 372 (one or more),
376
Some servers send 377 or 378 replies instead of 372.
Returned From:
MOTD
|
| RAW 374 (RPL_ENDOFINFO) Back to Top |
Format: 374 :End of /INFO list.
Example: 374 :End of /INFO list.
Network: All
Info:
This is sent at the end of an INFO reply.
See Also:
The following are sent for an INFO reply:
371 (multiple lines), 374
Returned From:
INFO
|
| RAW 375 (RPL_MOTDSTART) Back to Top |
Format: 375 :- <server> Message of the Day -
Example: 375 :- NewBrunswick.NJ.US.Undernet.Org Message of the Day -
Network: Most
Parameters:
<server> The server returning the message of the day.
(most likely the one you are connected to)
Info:
This is sent in reply to a MOTD request or on connection, immediately preceding
the text for the actual message of the day.
Notes:
When requesting a MOTD from a server other than your current server,
the 375 may not be sent before the body of the MOTD.
Variations:
Some servers do not include the hyphen at the beginning of MOTD replies, so you
cannot rely on the server name being in the same place.
Some servers do not send a 375 reply prior to the message of the day.
See Also:
The following are sent for a Message of the Day:
375 (usually), 372 (one or more),
376
Some servers send 377 or 378 replies instead of 372.
Returned From:
MOTD
|
| RAW 376 (RPL_ENDOFMOTD) Back to Top |
Format: 376 :End of /MOTD command.
Example: 376 :End of /MOTD command.
Network: All
Info:
This is sent in reply to a MOTD request or on connection. This should be the last
numeric sent in reply, after the text of the message of the day itself.
See Also:
The following are sent for a Message of the Day:
375 (usually), 372 (one or more),
376
Some servers send 377 or 378 replies instead of 372.
Returned From:
MOTD
|
| RAW 377 (RPL_ISASERVICE) Back to Top |
Format: 377 :- <info>
Example: 377 :- 28/6/1998 14:32
Network: Some
Parameters:
<info> A single line from the server's message of the day.
Info:
This is sent in reply to a MOTD request or on connection. In most cases,
multiple replies will be sent, one for each line in the MOTD.
Notes:
The standard reply to MOTD uses 372 numerics, not 377. This numeric is sent by
certain servers instead of 372 to bypass clients and scripts that hide the MOTD,
among other reasons.
Variations:
Some servers do not include the hyphen at the beginning of MOTD replies, so you
cannot rely on the actual text starting at the second word.
Some servers use a different numeric for MOTD replies, such as 378.
(the standard numeric is 372, not this one.) The format and purpose remains the same, however.
See Also:
The following are sent normally for a Message of the Day-
375 (usually), 372 (one or more),
376
Some servers send 377 or 378 replies instead of 372.
Returned From:
MOTD
|
| RAW 378 (RPL_WHOISHOST) Back to Top |
Format: 378 :- <info>
Example: 378 :- Welcome to IRC
Network: Some
Parameters:
<info> A single line from the server's message of the day.
Info:
This is sent in reply to a MOTD request or on connection. In most cases,
multiple replies will be sent, one for each line in the MOTD.
Notes:
The standard reply to MOTD uses 372 numerics, not 378. This numeric is sent by
certain servers instead of 372 to bypass clients and scripts that hide the MOTD,
among other reasons.
Variations:
Some servers do not include the hyphen at the beginning of MOTD replies, so you
cannot rely on the actual text starting at the second word.
Some servers use a different numeric for MOTD replies, such as 377.
(the standard numeric is 372, not this one.) The format and purpose remains the same, however.
See Also:
The following are sent normally for a Message of the Day:
375 (usually), 372 (one or more),
376
Some servers send 377 or 378 replies instead of 372.
Returned From:
MOTD
|
| RAW 381 (RPL_YOUREOPER) Back to Top |
Format: 381 :You are now an IRC Operator
Example: 381 :You are now an IRC Operator
Network: All
Info:
This numeric is returned when you successfuly become an IRC operator using the OPER command.
Notes:
This should be preceded by an automatic usermode change that includes +o or +O. (IRC operator)
Returned From:
OPER
|
| RAW 382 (RPL_REHASHING) Back to Top |
Format: 382 <file> :Rehashing
Example: 382 ircd.conf :Rehashing
Network: All
Info:
This numeric is simply returned when you REHASH (reload) the IRCd configuration file.
Returned From:
REHASH
|
| RAW 391 (RPL_TIME) Back to Top |
Format: 391 <server> :<time>
Example: 391 webbernet.mi.us.dal.net :Friday August 7 1998 -- 17:26 -04:00
Network: All
Parameters:
<server> Any server.
<time> The current date and time at the server.
Info:
This is sent in reply to a TIME request.
Notes:
The reply may be in any format, so unless you are writing for a specific server
or network, it is best not to assume the format is in any one form.
Variations:
Some networks (such as Undernet) add additional fields before 'time', such as a
$ctime style timestamp.
Returned From:
TIME
|
|