List of IRC commands

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.

[1] Syntax: 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.

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.

This command is not formally defined in an RFC, but is in use by some IRC networks.

Support is indicated in a RPL_ISUPPORT reply (numeric 005) with the CNOTICE keyword Syntax: Sends a private message to on that bypasses flood protection limits.

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.

This command is not formally defined in an RFC, but is in use by some IRC networks.

Syntax: 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.

Syntax: Queries the server to see if the clients in the space-separated list are currently on the network.

Syntax: Sends a NOTICE to an invitation-only with an optional , requesting an invite.

[16] If called with no arguments, the statistics will reflect the entire network.

Syntax: Sends a command string to the server as-is, i.e. without parsing it in the client application.

Syntax: Allows a client to change the "real name" specified when registering a connection.

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 SETNAME keyword Syntax: Adds or removes a host mask to a server-side ignore list that prevents matching users from sending the client messages.

More than one mask may be specified in a space-separated list, each item prefixed with a "+" or "-" to designate whether it is being added or removed.

Sending the command with no parameters returns the entries in the client's ignore list.

Support is indicated in a RPL_ISUPPORT reply (numeric 005) with the SILENCE keyword and the maximum number of entries a client may have in its ignore list.

Syntax: Gives users who are on the same host as a message asking them to join IRC.

Syntax: Trace a path across the IRC network to a specific server or client, in a similar method to traceroute.

Syntax: 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.

This command is not formally defined by an RFC, but is in use by some IRC daemons.

Syntax: Adds or removes a user to a client's server-side friends list.

More than one nickname may be specified in a space-separated list, each item prefixed with a "+" or "-" to designate whether it is being added or removed.

Sending the command with no parameters returns the entries in the client's friends list.

Support is indicated in a RPL_ISUPPORT reply (numeric 005) with the WATCH keyword and the maximum number of entries a client may have in its friends list.