2 ngIRCd - Next Generation IRC Server
3 http://ngircd.barton.de/
5 (c)2001-2013 Alexander Barton and Contributors.
6 ngIRCd is free software and published under the
7 terms of the GNU General Public License.
12 This file lists all commands available on ngIRCd. It is written in a format
13 that is human readable as well as machine parseable and therefore can be used
14 as "help text file" of the daemon.
16 In short, the daemon reads this file on startup and parses it as following
17 when an user issues a "HELP <cmd>" command:
19 1. Search the file for a line "- <cmd>",
20 2. Output all subsequent lines that start with a TAB (ASCII 9) character
21 to the client using NOTICE commands, treat lines containing a single "."
22 after the TAB as empty lines.
23 3. Break at the first line not starting with a TAB character.
25 This format allows to have information to each command stored in this file
26 which will not be sent to an IRC user requesting help which enables us to
27 have additional annotations stored here which further describe the origin,
28 implementation details, or limits of the specific command which are not
29 relevant to an end-user but administrators and developers.
31 A special "Intro" block is returned to the user when the HELP command is
32 used without a command name:
36 This is ngIRCd, a server software for Internet Relay Chat (IRC)
37 networks. You can find more information about ngIRCd on its homepage:
38 <http://ngircd.barton.de>
40 Use "HELP COMMANDS" to get a list of all available commands and
41 "HELP <command-name>" to get help for a specific IRC command, for
42 example "HELP quit" or "HELP privmsg".
45 Connection Handling Commands
46 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
51 CAP REQ <capabilities>
52 CAP ACK <capabilities>
53 CAP NAK <capabilities>
57 List, request, and clear "IRC Capabilities".
59 Using this command, an IRC client can request additional "IRC
60 capabilities" during login or later on, which influences the
61 communication between server and client. Normally, these commands
62 aren't directly used by humans, but automatically by their client
63 software. And please note that issuing such commands manually can
64 irritate the client software used, because of the "non-standard"
65 behavior of the server!
67 - CAP LS: list all available capabilities.
68 - CAP LIST: list active capabilities of this connection.
69 - CAP REQ: Request particular capabilities.
70 - CAP ACK: Acknowledge a set of capabilities to be enabled/disabled.
71 - CAP NAK: Reject a set of capabilities.
72 - CAP CLEAR: Clear all set capabilities.
73 - CAP END: Indicate end of capability negotiation during login,
74 ignored in an fully registered session.
76 Please note that the <capabilities> must be given in a single
77 parameter but whitespace separated, therefore a command could look
78 like this: "CAP REQ :capability1 capability2 capability3" for example.
81 - <http://ircv3.atheme.org/specification/capability-negotiation-3.1>
82 - <http://ngircd.barton.de/doc/Capabilities.txt>
83 - doc/Capabilities.txt
91 Change your nickname to <nick>.
94 PASS <password> <version> <flags> [<options>]
96 Set a connection <password>. This command must be sent before the
97 NICK/USER registration combination.
99 See doc/Protocol.txt for more info.
102 PING <server1> [<server2>]
104 Tests the presence of a connection. A PING message results in a PONG
105 reply. If <server2> is specified, the message gets passed on to it.
108 PONG <server1> [<server2>]
110 This command is a reply to the PING command and works in much the
114 QUIT [<quit-message>]
116 End IRC session and disconnect from the server.
118 If a <quit-message> has been given, it is displayed to all the
119 channels that you are a member of when leaving.
122 USER <user> <modes> <realname>
124 This command is used at the beginning of a connection to specify the
125 <user>name, hostname, <realname> and initial user <modes> of the
128 <realname> may contain spaces, and thus must be prefixed with a colon.
140 Provides the server with a message to automatically send in reply to a
141 PRIVMSG directed at the user, but not to a channel they are on.
143 If <message> is omitted, the away status is removed.
148 Show help information for a specific IRC <command>. The <command> name
151 Use the command "HELP Commands" to get a list of all available commands.
153 The HELP command isn't specified by any RFC but implemented by most
154 daemons. If no help text could be read in, ngIRCd outputs a list of all
155 implemented commands when receiving a plain "HELP" command as well as
158 ngIRCd replies using "NOTICE" commands like ircd 2.10/2.11; other
159 implementations are using numerics 704, 705, and 706.
163 MODE <nickname> <flags> (user)
164 MODE <channel> <flags> [<args>]
166 The MODE command is dual-purpose. It can be used to set both (user) and
169 See doc/Modes.txt for more information.
172 NOTICE <target> <notice>
174 Send <notice> to <target> (nick or channel).
176 This command works similarly to PRIVMSG, except automatic replies must
177 never be sent in reply to NOTICE messages.
180 PRIVMSG <target> <message>
182 Send <message> to <target> (nick or channel).
184 Common IRC clients use MSG as PRIVMSG alias.
185 (Some clients use "QUERY <nick> [<message>]" to open a private chat.)
188 Status and Informational Commands
189 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
194 Show administrative information about an IRC server in the network.
195 If no server name has been given, the local server will respond.
200 Show the version, birth & online time of the current IRC server.
201 If <server> has been given, it shows the INFO of the specific <server>.
206 Queries the server to see if the clients in the space-separated list
207 <nicknames> are currently on the network.
209 The server returns only the <nicknames> that are on the network in a
210 space-separated list. If none of the clients are on the network the
211 server returns an empty list.
214 LINKS [<remote server> [<server mask>]]
216 Lists all server links matching <server mask>, if given,
217 on <remote server>, or the current server if omitted.
220 LUSERS [<mask> [<server>]]
222 Return statistics about the size of the network. If called with no
223 arguments, the statistics will reflect the entire network.
225 If <mask> is given, it will return only statistics reflecting the
226 masked subset of the network.
227 If <server> is given, the command will be forwarded to <server>
233 Show "Message Of The Day" of the current server or specified <server>.
236 NAMES [<channels> [<server>]]
238 Returns a list of who is on the comma-separated list of <channels>,
241 If <channels> is omitted, all users are shown, grouped by channel name
242 with all users who are not on a channel being shown as part of channel
244 If <server> is specified, the command is sent to <server> for
248 STATS <flag> [<server>]
250 Returns statistics about the current server, or of a specified <server>.
254 g = G-Lines (Network-wide bans)
255 k = K-Lines (Server-local bans)
256 l = Link status (Parent server and own link)
257 m = IRC command status (usage count)
263 Show the local time of the current server, or of a specified <server>.
268 Trace a path across the IRC network of the current server, or if given
269 of a specific <server>, in a similar method to traceroute.
274 Show the user-host of <nicknames> (seperated by space).
275 "-" means <nick> is away,
276 "+" means <nick> is available,
277 "*" indicates your connection.
282 Show the ngIRCd version of the current server, or specified <server>.
287 Returns a list of users who match <target> (nick, hostmask or channel).
289 If the flag "o" is given, the server will only return information about
293 WHOIS [<server>] <nicknames>
295 Returns information about the comma-separated list of <nicknames>.
297 If <server> is given, the command is forwarded to it for processing.
300 WHOWAS <nickname> [<count> [<server>]]
302 Used to return information about <nicknames> that are no longer in use
303 (due to client disconnection, or nickname changes).
305 If given, the server will return information from the last <count> times
306 the nickname has been used.
307 If <server> is given, the command is forwarded to it for processing.
314 INVITE <nick> <channel>
316 Invites <nick> to <channel>.
317 <channel> does not have to exist, but if it does, only members of the
318 channel are allowed to invite other clients.
320 If the <channel> mode "+i" is set, only <channel> operators may invite
324 JOIN <channels> [<channel-keys>]
326 Makes the client join the <channels> (comma-separated list), specifying
327 the passwords, if needed, in the comma-separated <channel-keys> list.
328 A <channel-key> is only needed, if the <channel> mode "+k" is set.
330 If the channel(s) do not exist, then they will be created.
333 KICK <channel> <nick> [<kick-message>]
335 Remove <nick> from <channel>, optional with a <kick-message>.
337 Only <channel> operators are able to KICK.
340 LIST [<channels> [<server>]]
342 List all visible <channels> (comma-seperated list) on the current
344 If <server> is given, the command will be forwarded to <server> for
348 PART <channels> [<part-message>]
350 Leave <channels> (comma-separated list), optional with a
354 TOPIC <channel> <topic>
356 Set a <topic> for <channel>.
358 Only <channel> operators are able to set a <topic>.
361 Administrative Commands
362 ~~~~~~~~~~~~~~~~~~~~~~~
365 CONNECT <target server> [<port> [<remote server> [<mypwd> <peerpwd>]]]
367 Instructs the current server, or <remote server> if specified,
368 to connect to <target server>.
370 To connect <remote server> you need to have remote oper status.
371 If <port> is omitted, it uses the server port of the configuration.
372 If <mypwd> and <peerpwd> is given, it uses those passwords instead
373 of the ones in the configuration.
378 Instructs the server to shut down.
381 DISCONNECT [<remote server>]
383 Disconnects the current server, or <remote server> if specified.
384 To disconnect a <remote server> you need to have remote oper status.
387 GLINE <nick!user@hostmask> <seconds> :<reason>
389 This command provides timed G-Lines (Network-wide bans).
390 If a client matches a G-Line, it cannot connect to any server on
391 the IRC network. If you put 0 as <seconds>, it makes the G-Line
394 To remove a G-Line, type "GLINE <nick!user@hostmask>".
395 To list the G-Lines, type "STATS g".
400 Forcibly removes <nick> from the IRC network with a <reason>.
403 KLINE <nick!user@hostmask> <seconds> :<reason>
405 This command provides timed K-Lines (Server-local bans).
406 If a client matches a K-Line, it cannot connect to the issued server.
407 If you put 0 as <seconds>, it makes the K-Line permanent.
409 To remove a K-Line, type "KLINE <nick!user@hostmask>".
410 To list the K-Lines, type "STATS k".
413 OPER <user> <password>
415 Authenticates <user> as an IRC operator on the current server/network.
420 Causes the server to re-read and re-process its configuration file(s).
430 Sends <message> to all users with user mode "+w".
445 Server Protocol Commands
446 ~~~~~~~~~~~~~~~~~~~~~~~~
449 CHANINFO <channel> +<modes> [[<key> <limit>] <topic>]
451 CHANINFO is used by servers to inform each other about a channel:
452 its modes, channel key, user limits and its topic.
454 See doc/Protocol.txt for more information.
457 ERROR [<message> [<> [...]]]
459 Return an error message to the server. The first parameter, if given,
460 will be logged by the server, all further parameters are silently
463 This command is silently ignored on non-server and non-service links.
466 METADATA <target> <key> <value>
468 The METADATA command is used on server-links to update "metadata"
469 information of clients, like the hostname, the info text ("real name"),
472 See doc/Protocol.txt for more information.
481 Disconnects an IRC Server from the network.