Content deleted Content added
m →See also: already linked |
m Reverted edits by 2600:387:15:2F34:0:0:0:8 (talk) (HG) (3.4.13) |
||
| (66 intermediate revisions by 50 users not shown) | |||
Line 1:
{{short description|none}}
{{Use dmy dates|date=February 2016}}
{{how-to |date=June 2024}}
<!-- ATTENTION EDITORS:
Do NOT include service-specific commands on this list. THEY WILL BE REMOVED.
-->
This is a list of all '''[[Internet Relay Chat]] commands''' from [[Request for Comments|RFC]] 1459, RFC 2812, and extensions added to major IRC daemons. Most IRC clients require commands to be preceded by a slash ("<code>/
Conventions used here: Angle brackets ("<" and ">") are used here to indicate a placeholder for some value, and are not a literal part of a command. Square brackets ("[" and "]") are used to indicate that a value is ''optional''.
== User commands ==
Line 12 ⟶ 16:
:<code>ADMIN [<nowiki><target></nowiki>]</code>
Instructs the [[Server (computing)|server]] to return information about the administrators of the server specified by <nowiki><target></nowiki>, where <nowiki><target></nowiki> is either a server or a user. If <nowiki><target></nowiki> is omitted, the server should return information about the administrators of the current server.<ref>{{cite IETF
| rfc = 1459
| section = 4.3.7
| page = 31
| idanchor = ietf
| title = Admin command
}}</ref>
Line 27 ⟶ 31:
Provides the server with a message to automatically send in reply to a PRIVMSG directed at the user, but not to a channel they are on.<ref>{{cite IETF
| rfc = 1459
|
| section = 5.1
| pages = 38 – 39
| idanchor = ietf
}}</ref>
If <nowiki><message></nowiki> is omitted, the away status is removed. Defined in RFC 1459.
=== CNOTICE ===
Line 41 ⟶ 43:
:<code><nowiki>CNOTICE <nickname> <channel> :<message></nowiki></code>
Sends a channel NOTICE message to <nowiki><nickname></nowiki> on <nowiki><channel></nowiki> that bypasses flood protection limits. The target nickname must be in the same channel as the client issuing the command, and the client must be a channel operator.
Normally an IRC server will limit the number of different targets a client can send messages to within a certain time frame to prevent spammers or bots from mass-messaging users on the network, however this command can be used by channel operators to bypass that limit in their channel. For example, it is often used by help operators that may be communicating with a large number of users in a help channel at one time.
Line 52 ⟶ 54:
:<code><nowiki>CPRIVMSG <nickname> <channel> :<message></nowiki></code>
Sends a private message to <nowiki><nickname></nowiki> on <nowiki><channel></nowiki> that bypasses flood protection limits. The target nickname must be in the same channel as the client issuing the command, and the client must be a channel operator.
Normally an IRC server will limit the number of different targets a client can send messages to within a certain time frame to prevent spammers or bots from mass-messaging users on the network, however this command can be used by channel operators to bypass that limit in their channel. For example, it is often used by help operators that may be communicating with a large number of users in a help channel at one time.
Line 62 ⟶ 64:
Syntax:
:<code><nowiki>CONNECT <target server> [<port> [<remote server>]]</nowiki></code> (RFC 1459)
:<code><nowiki>CONNECT <target server> <port> [<remote server>]</nowiki></code> (
Instructs the server <nowiki><remote server></nowiki> (or the current server, if <nowiki><remote server></nowiki> is omitted) to connect to <nowiki><target server></nowiki> on port <nowiki><port></nowiki>.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.3.5
| pages = 29 – 30
Line 72 ⟶ 74:
}}</ref><ref>{{cite IETF
| rfc = 2812
|
| section = 3.4.7
| pages = 28 – 29
| idanchor = ietf
}}</ref>
This command should only be available to [[IRC Operator|IRC operators]]
=== DIE ===
Line 85:
Syntax:
:<code><nowiki>DIE</nowiki></code>
Instructs the server to shut down.<ref>{{cite IETF
| rfc = 2812
|
| section = 4.3
| page = 39
| idanchor = ietf
}}</ref> This command may only be issued by IRC server operators. Defined in RFC 2812.
=== ENCAP ===
Line 102 ⟶ 99:
:<code><nowiki>:<source> ENCAP <destination> <subcommand> <parameters></nowiki></code>
This command is for use by servers to encapsulate commands so that they will propagate across hub servers not yet updated to support them, and indicates the subcommand and its parameters should be passed unaltered to the destination, where it will be unencapsulated and parsed. This facilitates implementation of new features without a need to restart all servers before they are usable across the network.<ref>
=== ERROR ===
Line 111 ⟶ 108:
This command is for use by servers to report errors to other servers. It is also used before terminating client connections.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.6.4
| page = 38
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== HELP ===
Line 124 ⟶ 119:
:<code><nowiki>HELP</nowiki></code>
Requests the server to display the help file. This command is not formally defined in an RFC, but is in use by most{{which|date=August 2014}} major IRC daemons.
=== INFO ===
Line 135 ⟶ 128:
Returns information about the <nowiki><target></nowiki> server, or the current server if <nowiki><target></nowiki> is omitted.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.3.8
| pages = 31 – 32
| idanchor = ietf
}}</ref> Information returned includes the server's version, when it was [[compiler|compiled]], the [[Patch (computing)|patch level]], when it was started, and any other information which may be considered to be relevant. Defined in RFC 1459.
=== INVITE ===
Line 148 ⟶ 139:
:<code><nowiki>INVITE <nickname> <channel></nowiki></code>
Invites <nowiki><nickname></nowiki> to the channel <nowiki><channel></nowiki>.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.2.7
| page = 25
| idanchor = ietf
}}</ref> <nowiki><channel></nowiki> does not have to exist, but if it does, only members of the channel are allowed to invite other clients. If the channel mode <code>i</code> is set, only channel operators may invite other clients. Defined in RFC 1459.
=== ISON ===
Line 165 ⟶ 154:
Queries the server to see if the clients in the space-separated list <nowiki><nicknames></nowiki> are currently on the network.<ref>{{cite IETF
| rfc = 1459
|
| section = 5.8
| page = 42
| idanchor = ietf
}}</ref> The server returns only the nicknames that are on the network in a space-separated list. If none of the clients are on the network the server returns an empty list. Defined in RFC 1459.
=== JOIN ===
Line 178 ⟶ 165:
:<code><nowiki>JOIN <channels> [<keys>]</nowiki></code>
Makes the client join the channels in the comma-separated list <nowiki><channels></nowiki>, specifying the passwords, if needed, in the comma-separated list <nowiki><keys></nowiki>.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.2.1
| pages = 19 – 20
| idanchor = ietf
}}</ref> If the channel(s) do not exist then they will be created. Defined in RFC 1459.
=== KICK ===
Syntax:
:<code><nowiki>KICK <channel> <client> :[<message>]</nowiki></code>
Forcibly removes <nowiki><client></nowiki> from <nowiki><channel></nowiki>.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.2.8
| pages = 25 – 26
| idanchor = ietf
}}</ref> This command may only be issued by channel operators. Defined in RFC 1459.
=== KILL ===
Line 208 ⟶ 191:
:<code><nowiki>KILL <client> <comment></nowiki></code>
Forcibly removes <nowiki><client></nowiki> from the network.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.6.1
| page = 36
| idanchor = ietf
}}</ref> This command may only be issued by IRC operators. Defined in RFC 1459.
=== KNOCK ===
Line 223 ⟶ 204:
:<code><nowiki>KNOCK <channel> [<message>]</nowiki></code>
Sends a NOTICE to an invitation-only <nowiki><channel></nowiki> with an optional <nowiki><message></nowiki>, requesting an invite. This command is not formally defined by an RFC, but is supported by most{{which|date=August 2014}} major IRC daemons. Support is indicated in a RPL_ISUPPORT reply (numeric 005) with the KNOCK keyword.
=== LINKS ===
Line 232 ⟶ 211:
:<code><nowiki>LINKS [<remote server> [<server mask>]]</nowiki></code>
Lists all server links matching <nowiki><server mask></nowiki>, if given, on <nowiki><remote server></nowiki>, or the current server if omitted.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.3.3
| pages = 28 – 29
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== LIST ===
Line 249 ⟶ 226:
Lists all channels on the server.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.2.6
| pages = 24 – 25
| idanchor = ietf
}}</ref> If the comma-separated list <nowiki><channels></nowiki> is given, it will return the channel topics. If <nowiki><server></nowiki> is given, the command will be forwarded to <nowiki><server></nowiki> for evaluation. Defined in RFC 1459.
=== LUSERS ===
Line 264 ⟶ 239:
Returns statistics about the size of the network.<ref>{{cite IETF
| rfc = 2812
|
| section = 3.4.2
| pages = 25 – 26
| idanchor = ietf
}}</ref> If called with no arguments, the statistics will reflect the entire network. If <nowiki><mask></nowiki> is given, it will return only statistics reflecting the masked subset of the network. If <nowiki><target></nowiki> is given, the command will be forwarded to <nowiki><server></nowiki> for evaluation. Defined in RFC 2812.
=== MODE ===
Line 280 ⟶ 253:
The MODE command is dual-purpose. It can be used to set both user and channel modes.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.2.3
| pages = 21 – 23
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== MOTD ===
Line 295 ⟶ 266:
Returns the message of the day on <nowiki><server></nowiki> or the current server if it is omitted.<ref>{{cite IETF
| rfc = 2812
|
| section = 3.4.1
| page = 25
| idanchor = ietf
}}</ref> Defined in RFC 2812.
=== NAMES ===
Line 307 ⟶ 276:
Syntax:
:<code><nowiki>NAMES [<channels>]</nowiki></code> (RFC 1459)
:<code><nowiki>NAMES [<channels> [<server>]]</nowiki></code> (
Returns a list of who is on the comma-separated list of <nowiki><channels></nowiki>, by channel name.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.2.5
| page = 24
Line 317 ⟶ 286:
}}</ref> If <nowiki><channels></nowiki> is omitted, all users are shown, grouped by channel name with all users who are not on a channel being shown as part of channel "*". If <nowiki><server></nowiki> is specified, the command is sent to <nowiki><server></nowiki> for evaluation.<ref>{{cite IETF
| rfc = 2812
|
| section = 3.2.5
| pages = 20 – 21
| idanchor = ietf
}}</ref> Defined in RFC 1459; the optional <nowiki><server></nowiki> parameter was added in RFC 2812.
The response contains all nicknames in the channel prefixed with the highest channel status prefix of that user, for example like this (with @ being the highest status prefix)
Line 329 ⟶ 296:
:<code>:irc.server.net 353 Phyre = #SomeChannel :@WiZ</code>
If a client wants to receive all the channel status prefixes of a user and not only their current highest one, the IRCv3 multi-prefix extension can be enabled (@ is the channel operator prefix, and + the lower voice status prefix):<ref name="andrewnorthall">{{cite web |url=http://ircv3.atheme.org/extensions/multi-prefix-3.1 |title=IRCv3 – Welcome |author=Andrew Northall
:<code>:irc.server.net 353 Phyre = #SomeChannel :@+WiZ</code>
See also NAMESX below for an alternate, older approach to achieve the same effect. However, by today most clients and servers support the new IRCv3 standard.<ref>{{cite web|url=http://ircv3.atheme.org/|title=IRCv3 – Welcome|author=Andrew Northall
=== NICK ===
Line 358 ⟶ 306:
Syntax:
:<code><nowiki>NICK <nickname> [<hopcount>]</nowiki></code> (RFC 1459)
:<code><nowiki>NICK <nickname></nowiki></code> (
Allows a client to change their IRC nickname. Hopcount is for use between servers to specify how far away a nickname is from its home server.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.1.2
| pages = 14 – 15
Line 368 ⟶ 316:
}}</ref><ref>{{cite IETF
| rfc = 2812
|
| section = 3.1.2
| pages = 10 – 11
| idanchor = ietf
}}</ref> Defined in RFC 1459; the optional <nowiki><hopcount></nowiki> parameter was removed in RFC 2812.
=== NOTICE ===
Line 383 ⟶ 329:
This command works similarly to PRIVMSG, except automatic replies must never be sent in reply to NOTICE messages.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.4.2
| page = 33
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== OPER ===
Line 398 ⟶ 342:
Authenticates a user as an IRC operator on that server/network.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.1.5
| page = 17
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== PART ===
Line 413 ⟶ 355:
Causes a user to leave the channels in the comma-separated list <nowiki><channels></nowiki>.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.2.2
| pages = 20 – 21
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== PASS ===
Line 428 ⟶ 368:
Sets a connection password.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.1.1
| page = 14
| idanchor = ietf
}}</ref> This command must be sent before the NICK/USER registration combination. Defined in RFC 1459.
=== PING ===
Line 443 ⟶ 381:
Tests the presence of a connection.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.6.2
| page = 37
| idanchor = ietf
}}</ref> A PING message results in a PONG reply. If <server2> is specified, the message gets passed on to it. Defined in RFC 1459.
=== PONG ===
Line 458 ⟶ 394:
This command is a reply to the PING command and works in much the same way.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.6.3
| pages = 37 – 38
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== PRIVMSG ===
Syntax:
:<code><nowiki>PRIVMSG <msgtarget> :<message></nowiki></code>
Sends <nowiki><message></nowiki> to <nowiki><msgtarget></nowiki>, which is usually a user or channel.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.4.1
| pages = 32 – 33
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== QUIT ===
Line 488 ⟶ 420:
Disconnects the user from the server.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.1.6
| pages = 17 – 18
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== QUOTE ===
Syntax:
:<code><nowiki>QUOTE</nowiki></code>
Sends a command string to the server as-is, i.e. without parsing it in the client application.
<ref>{{cite web
| url = https://irssi.org/documentation/help/quote/
| title = quote - Irssi help page
| author = [[Irssi]] developers
}}</ref>
<ref><code>/quote</code> is cited in the [[mIRC]] documentation ([https://www.mirc.com/help/html/index.html?mirc_commands.html]) as an equivalent of mIRC's <code>/raw</code> command, but which is supported in the other IRC clients.</ref>
=== REHASH ===
Line 503 ⟶ 445:
Causes the server to re-read and re-process its configuration file(s).<ref>{{cite IETF
| rfc = 1459
|
| section = 5.2
| page = 39
| idanchor = ietf
}}</ref> This command can only be sent by IRC
=== RULES ===
Line 531 ⟶ 456:
:<code><nowiki>RULES</nowiki></code>
Requests the server rules. This command is not formally defined in an RFC, but is used by most{{which|date=August 2014}} major IRC daemons.
=== SERVER ===
Line 542 ⟶ 465:
The server message is used to tell a server that the other end of a new connection is a server.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.1.4
| pages = 16 – 17
| idanchor = ietf
}}</ref> This message is also used to pass server data over the whole network.
<nowiki><hopcount></nowiki> details how many hops (server connections) away <servername> is.
<nowiki><info></nowiki> contains addition human-readable information about the server.
Defined in RFC 1459.
=== SERVICE ===
Syntax:
=== SERVLIST ===
=== SQUERY ===
Line 589 ⟶ 488:
Identical to PRIVMSG except the recipient must be a service.<ref>{{cite IETF
| rfc = 2812
|
| section = 3.5.2
| page = 32
| idanchor = ietf
}}</ref> Defined in RFC 2812.
=== SQUIT ===
Line 604 ⟶ 501:
Causes <nowiki><server></nowiki> to quit the network.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.1.7
| pages = 18 – 19
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== SETNAME ===
Line 639 ⟶ 534:
Returns statistics about the current server, or <nowiki><server></nowiki> if it's specified.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.3.2
| pages = 27 – 28
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== SUMMON ===
Line 651 ⟶ 544:
Syntax:
:<code><nowiki>SUMMON <user> [<server>]</nowiki></code> (RFC 1459)
:<code><nowiki>SUMMON <user> [<server> [<channel>]]</nowiki></code> (
Gives users who are on the same host as <nowiki><server></nowiki> a message asking them to join IRC.<ref>{{cite IETF
| rfc = 1459
|
| section = 5.4
| page = 40
Line 661 ⟶ 554:
}}</ref><ref>{{cite IETF
| rfc = 2812
|
| section = 4.5
| page = 40
| idanchor = ietf
}}</ref> Defined in RFC 1459; the optional <nowiki><channel></nowiki> parameter was added in RFC 2812.
=== TIME ===
Line 676 ⟶ 567:
Returns the local time on the current server, or <nowiki><server></nowiki> if specified.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.3.4
| page = 29
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== TOPIC ===
Line 689 ⟶ 578:
:<code><nowiki>TOPIC <channel> [<topic>]</nowiki></code>
Allows the client to query or set the channel topic on <nowiki><channel></nowiki>.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.2.4
| pages = 23 – 24
| idanchor = ietf
}}</ref> If <nowiki><topic></nowiki> is given, it sets the channel topic to <nowiki><topic></nowiki>. If channel mode +t is set, only a channel operator may set the topic. Defined in RFC 1459.
=== TRACE ===
Line 706 ⟶ 593:
Trace a path across the IRC network to a specific server or client, in a similar method to [[traceroute]].<ref>{{cite IETF
| rfc = 1459
|
| section = 4.3.6
| pages = 30 – 31
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== USER ===
Line 735 ⟶ 603:
Syntax:
:<code><nowiki>USER <username> <hostname> <servername> <realname></nowiki></code> (RFC 1459)
:<code><nowiki>USER <user> <mode> <unused> <realname></nowiki></code> (
This command is used at the beginning of a connection to specify the username, hostname, real name and initial user modes of the connecting client.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.1.3
| pages = 15 – 16
Line 745 ⟶ 613:
}}</ref><ref>{{cite IETF
| rfc = 2812
|
| section = 3.1.3
| page = 11
| idanchor = ietf
}}</ref> <nowiki><realname></nowiki> may contain spaces, and thus must be prefixed with a colon. Defined in RFC 1459, modified in RFC 2812.
=== USERHOST ===
Line 760 ⟶ 626:
Returns a list of information about the nicknames specified.<ref>{{cite IETF
| rfc = 1459
|
| section = 5.7
| page = 42
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== USERIP ===
Line 773 ⟶ 637:
:<code><nowiki>USERIP <nickname></nowiki></code>
Requests the direct [[IP address]] of the user with the specified nickname. This command is often used to obtain the IP of an abusive user to more effectively perform a ban. It is unclear what, if any, privileges are required to execute this command on a server.
This command is not formally defined by an RFC, but is in use by some IRC daemons. Support is indicated in a RPL_ISUPPORT reply (numeric 005) with the USERIP keyword.
Line 786 ⟶ 648:
Returns a list of users and information about those users in a format similar to the [[UNIX]] commands [[who (Unix)|who]], rusers and [[finger (Unix)|finger]].<ref>{{cite IETF
| rfc = 1459
|
| section = 5.5
| pages = 40 – 41
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== VERSION ===
Line 801 ⟶ 661:
Returns the [[software version|version]] of <nowiki><server></nowiki>, or the current server if omitted.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.3.1
| pages = 26 – 27
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== WALLOPS ===
Line 816 ⟶ 674:
Sends <nowiki><message></nowiki> to all operators connected to the server (RFC 1459), or all users with user mode 'w' set (RFC 2812).<ref>{{cite IETF
| rfc = 1459
|
| section = 5.6
| page = 41
Line 822 ⟶ 680:
}}</ref><ref>{{cite IETF
| rfc = 2812
|
| section = 4.7
| pages = 41 – 42
| idanchor = ietf
}}</ref> Defined in RFC 1459.
=== WATCH ===
Line 846 ⟶ 702:
:<code><nowiki>WHO [<name> ["o"]]</nowiki></code>
Returns a list of users who match <nowiki><name></nowiki>.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.5.1
| pages = 33 – 34
| idanchor = ietf
}}</ref> If the flag "o" is given, the server will only return information about IRC
=== WHOIS ===
Line 863 ⟶ 717:
Returns information about the comma-separated list of nicknames masks <nowiki><nicknames></nowiki>.<ref>{{cite IETF
| rfc = 1459
|
| section = 4.5.2
| pages = 34 – 35
| idanchor = ietf
}}</ref> If <nowiki><server></nowiki> is given, the command is forwarded to it for processing. Defined in RFC 1459.
=== WHOWAS ===
Line 878 ⟶ 730:
Used to return information about a nickname that is no longer in use (due to client disconnection, or nickname changes).<ref>{{cite IETF
| rfc = 1459
|
| section = 4.5.3
| page = 35
| idanchor = ietf
}}</ref> If given, the server will return information from the last <nowiki><count></nowiki> times the nickname has been used. If <nowiki><server></nowiki> is given, the command is forwarded to it for processing. In
| rfc = 2812
|
| section = 3.6.3
| page = 34
Line 890 ⟶ 742:
}}</ref>
Defined in RFC 1459.
== See also ==
Line 907 ⟶ 759:
| last1 = Oikarinen
| first1 = Jarkko
|
| last2 = Reed
| first2 = Darren
|
| publisher = [[Internet Engineering Task Force|IETF]]
|
| ref = ietf
}}
Line 921 ⟶ 772:
| last = Kalt
| first = Christophe
|
| publisher = [[Internet Engineering Task Force|IETF]]
|
| ref = ietf
}}
Line 934 ⟶ 784:
| last = Reed
| first = Darren
|
| publisher = [[Internet Engineering Task Force|IETF]]
|
}}
* {{cite IETF
Line 944 ⟶ 793:
| last = Kalt
| first = Christophe
|
| publisher = [[Internet Engineering Task Force|IETF]]
|
}}
* {{cite IETF
Line 954 ⟶ 802:
| last = Kalt
| first = Christophe
|
| publisher = [[Internet Engineering Task Force|IETF]]
|
}}
* {{cite IETF
Line 964 ⟶ 811:
| last = Kalt
| first = Christophe
|
| publisher = [[Internet Engineering Task Force|IETF]]
|
}}
{{IRC topics}}
{{authority control}}
[[Category:
[[Category:Computing commands]]
| |||