Services admins can drop any nickname without needing to identify for the nick, and may view
the access list for any nickname (/NickServ ACCESS LIST nick).
Syntax: /msg NickServ LOGOUT [nickname [REVALIDATE]] Without a parameter, reverses the effect of the IDENTIFY command, i.e. make you not recognized as the real owner of the nick anymore. Note, however, that you won't be asked to reidentify yourself. With a parameter, does the same for the given nick. If you specify REVALIDATE as well, Services will ask the given nick to re-identify. This use limited to Services admins.
Syntax: /msg NickServ DROP [nickname] Without a parameter, drops your nickname from the NickServ database. With a parameter, drops the named nick from the database. You may drop any nick within your group without any special privileges. Dropping any nick islimited to Services admins.
Syntax: /msg NickServ LIST pattern [FORBIDDEN] [NOEXPIRE] [UNCONFIRMED]
Lists all registered nicknames which match the given pattern, in nick!user@host format.
Nicks with the PRIVATE option set will only be displayed to Services admins. Nicks
with the NOEXPIRE option set will have a ! appended to the nickname for Services admins.
If the FORBIDDEN, NOEXPIRE or UNCONFIRMED options are given, only nicks which, respectively,
are FORBIDden, UNCONFIRMED or have the NOEXPIRE flag set will be displayed. If all three
options are given, all three types of nicks will be displayed.
These options are limited to Services admins.
Examples:
LIST *!joeuser@foo.com
Lists all registered nicks owned by joeuser@foo.com.
LIST *Bot*!*@*
Lists all registered nicks with Bot in their names (case insensitive).
LIST * NOEXPIRE
Lists all registered nicks which have been set to not expire.
Syntax: /msg NickServ ALIST [nickname] [level] With no parameters, lists channels you have access on. With one parameter, lists channels thatnickname has access on. With two parameters lists channels that nickname has level access or greater on. This use limited to Services admins.
;Syntax: /msg NickServ GLIST [nickname] Without a parameter, lists all nicknames that are in your group. With a parameter, lists all nicknames that are in the group of the given nick. This use limited to Services admins.
Syntax: /msg NickServ GETPASS nickname Returns the password for the given nickname. Note that whenever this command is used, a message including theperson who issued the command and the nickname it was used on will be logged and sent out as a WALLOPS/GLOBOPS. Limited to Services admins.
Syntax: /msg NickServ FORBID nickname [reason] Disallows a nickname from being registered or used by anyone. May be cancelled by dropping the nick. On certain networks, reason is required. Limited to Services admins.
Services admins can also drop any channel without needing to identify via password, and may view the access, AKICK, and level setting lists for any channel.
Syntax: /msg ChanServ LOGOUT channel [nickname] This command will log the selected nickname out meaning they would have to reidentify themselves to regain their access. If you are the founder of the channel, you can log out anybody, else you can only log out yourself. If you are a Services admin, you can log out anybody of any channel without having to be the founder of the channel. Also, you can omit the nickname parameter; this will log out all identified users from the channel.
Syntax: /msg ChanServ DROP channel Unregisters the named channel. Only Services admins can drop a channel for which they have not identified.
Services admins can also set the option NOEXPIRE, with which channels can be prevented from expiring. Additionally, Services admins can set options for any channel without identifying by password for the channel.
Syntax: /msg ChanServ SET channel NOEXPIRE {ON | OFF}
Sets whether the given channel will expire. Setting this to ON prevents the channel
from expiring.
Limited to Services admins.
Services admins can use the ALL parameter with any channel.
Syntax: /msg ChanServ LIST pattern [FORBIDDEN] [SUSPENDED] [NOEXPIRE] Lists all registered channels matching the given pattern. Channels with the PRIVATE option set will only be displayed to Services admins. Channels with the NOEXPIRE option set will have a ! appended to the channel name for Services admins. If the FORBIDDEN, SUSPENDED or NOEXPIRE options are given, only channels which, respectively, are FORBIDden, SUSPENDed or have the NOEXPIRE flag set will be displayed. If both options are given, both types of channels will be displayed. These options are limited to Services admins.
Syntax: /msg ChanServ GETPASS channel Returns the password for the given channel. Note thatwhenever this command is used, a message including the person who issued the command and the channel it was used on will be logged and sent out as a WALLOPS/GLOBOPS. Limited to Services admins.
Syntax: /msg ChanServ FORBID channel [reason] Disallows anyone from registering or using the given channel. May be cancelled by dropping the channel. Reason may be required on certain networks. Limited to Services admins.
Syntax: /msg ChanServ SUSPEND channel [reason] Disallows anyone from registering or using the givenchannel. May be cancelled by using the UNSUSPEND command to preserve all previous channel data/settings. Reason may be required on certain networks. Limited to Services admins.
Syntax: /msg ChanServ UNSUSPEND channel Releases a suspended channel. All data and settings are preserved from before the suspension. Limited to Services admins.
STATUS ERROR error-message
Limited to Services admins.
Syntax: /msg MemoServ SET LIMIT [user | channel] {limit | NONE} [HARD]
Sets the maximum number of memos a user or channel is allowed to have. Setting the limit
to 0 prevents the user from receiving any memos; setting it to NONE allows the user to
receive and keep as many memos as they want. If you do not give a nickname or channel,
your own limit is set.
Adding HARD prevents the user from changing the limit. Not adding HARD has the opposite
effect, allowing the user to change the limit (even if a previous limit was set with
HARD).
This use of the SET LIMIT command is limited to Services admins. Other users may only
enter a limit for themselves or a channel on which they have such privileges, may not
remove their limit, may not set a limit above <num>, and may not set a hard limit.
Syntax: /msg MemoServ INFO [nick | channel]
Without a parameter, displays information on the number of memos you have, how many of them are unread, and how many total memos you can receive.
With a channel parameter, displays the same information for the given channel.
With a nickname parameter, displays the same information for the given nickname.
This use limited to Services admins.
Syntax: /msg BotServ BOT ADD nick user host real
BOT CHANGE oldnick newnick [user [host [real]]]
BOT DEL nick
Allows Services admins to create, modify, and delete bots that users will be able to use on
their own channels.
BOT ADD adds a bot with the given nickname, username, hostname and realname. Since no integrity
checks are done for these settings, be really careful.
BOT CHANGE allows to change nickname, username, hostnameor realname of a bot without
actually delete it (and allthe data associated with it).
BOT DEL removes the given bot from the bot list.
Note: you cannot create a bot that has a nick that is currently registered.
If an unregistered user is currently using the nick, they will be killed.
These options are reserved to Services admins:
NOBOT Prevent a bot from being assigned to a channel.
PRIVATE Prevent a bot from being assigned by non IRC operators.
Syntax: /msg BotServ SET channel NOBOT {ON|OFF}
This option makes a channel be unassignable. If a bot is already assigned to the channel,
it is unassignedautomatically when you enable the option.
Limited to Services admins.
Syntax: /msg BotServ SET bot-nick PRIVATE {ON|OFF}
This option prevents a bot from being assigned to a channel by users that aren't
IRC operators.
Limited to Services admins.