[IRC]/NickServ /ChanServ /OperServ /MemoServ /HostSer /Bot..

PT-NGS- · June 25, 2006, 10:42:55 AM

PT-NGS- · June 25, 2006, 10:43:16 AM

HELP

NickServ allows you to \\"register\\" a nickname and
prevent others from using it. The following
commands allow for registration and maintenance of
nicknames; to use them, type /msg NickServ command.
For more information on a specific command, type
/msg NickServ HELP command.

REGISTER Register a nickname
GROUP Join a group
IDENTIFY Identify yourself with your password
ACCESS Modify the list of authorized addresses
SET Set options, including kill protection
DROP Cancel the registration of a nickname
RECOVER Kill another user who has taken your nick
RELEASE Regain custody of your nick after RECOVER
SENDPASS Forgot your password? Try this

Other commands: GHOST, ALIST, GLIST, INFO, LIST, LOGOUT,
STATUS

NOTICE: This service is intended to provide a way for
IRC users to ensure their identity is not compromised.
It is NOT intended to facilitate \\"stealing\\" of
nicknames or other malicious actions. Abuse of NickServ
will result in, at minimum, loss of the abused
nickname(s).

REGISTER

Syntax: /msg NickServ REGISTER password [email]

Registers your nickname in the NickServ database. Once
your nick is registered, you can use the SET and ACCESS
commands to configure your nick\\'s settings as you like
them. Make sure you remember the password you use when
registering - you\\'ll need it to make changes to your nick
later. (Note that case matters! EPONA, Epona, and
epona are all different passwords!)

Guidelines on choosing passwords:

Passwords should not be easily guessable. For example,
using your real name as a password is a bad idea. Using
your nickname as a password is a much worse idea and,
in fact, NickServ will not allow it. Also, short
passwords are vulnerable to trial-and-error searches, so
you should choose a password at least 5 characters long.
Finally, the space character cannot be used in passwords.

The parameter email is optional and will set the email
for your nick immediately. However, it may be required
on certain networks.
Your privacy is respected; this e-mail won\\'t be given to
any third-party person.

This command also creates a new group for your nickname,
that will allow you to register other nicks later sharing
the same configuration, the same set of memos and the
same channel privileges. For more information on this
feature, type /msg NickServ HELP GROUP.

GROUP

Syntax: /msg NickServ GROUP target password

This command makes your nickname join the target nickname\\'s
group. password is the password of the target nickname.

Joining a group will allow you to share your configuration,
memos, and channel priviledges with all the nicknames in the
group, and much more!

A group exists as long as it is useful. This means that even
if a nick of the group is dropped, you won\\'t lose the
shared things described above, as long as there is at
least one nick remaining in the group.

You can use this command even if you have not registered
your nick yet. If your nick is already registered, you\\'ll
need to identify yourself before using this command. Type
/msg NickServ HELP IDENTIFY for more information. This
last may be not possible on your IRC network.

It is recommended to use this command with a non-registered
nick because it will be registered automatically when
using this command. You may use it with a registered nick (to
change your group) only if your network administrators allowed
it.

You can only be in one group at a time. Group merging is
not possible.

Note: all the nicknames of a group have the same password.

IDENTIFY

Syntax: /msg NickServ IDENTIFY password

Tells NickServ that you are really the owner of this
nick. Many commands require you to authenticate yourself
with this command before you use them. The password
should be the same one you sent with the REGISTER
command.

LOGOUT

Syntax: /msg NickServ LOGOUT

This 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.

DROP

Syntax: /msg NickServ DROP [nickname]

Drops your nickname from the NickServ database. A nick
that has been dropped is free for anyone to re-register.

You may drop a nick within your group by passing it
as the nick parameter.

In order to use this command, you must first identify
with your password ( /msg NickServ HELP IDENTIFY for more
information).

ACCESS

Syntax: /msg NickServ ACCESS ADD mask
ACCESS DEL mask
ACCESS LIST

Modifies or displays the access list for your nick. This
is the list of addresses which will be automatically
recognized by NickServ as allowed to use the nick. If
you want to use the nick from a different address, you
need to send an IDENTIFY command to make NickServ
recognize you.

Examples:

ACCESS ADD anyone@*.bepeg.com
Allows access to user anyone from any machine in
the bepeg.com domain.

ACCESS DEL anyone@*.bepeg.com
Reverses the previous command.

ACCESS LIST
Displays the current access list.

SET

Syntax: /msg NickServ SET option parameters

Sets various nickname options. option can be one of:

DISPLAY Set the display of your group in Services
PASSWORD Set your nickname password
LANGUAGE Set the language Services will use when
sending messages to you
URL Associate a URL with your nickname
EMAIL Associate an E-mail address with your nickname
ICQ Associate an ICQ number with your nickname
GREET Associate a greet message with your nickname
KILL Turn protection on or off
SECURE Turn nickname security on or off
PRIVATE Prevent your nickname from appearing in a
/msg NickServ LIST
HIDE Hide certain pieces of nickname information
MSG Change the communication method of Services

In order to use this command, you must first identify
with your password ( /msg NickServ HELP IDENTIFY for more
information).

Type /msg NickServ HELP SET option for more information
on a specific option.

SET DISPLAY

Syntax: /msg NickServ SET DISPLAY new-display

Changes the display used to refer to your nickname group in
Services. The new display MUST be a nick of your group.

SET PASSWORD

Syntax: /msg NickServ SET PASSWORD new-password

Changes the password used to identify you as the nick\\'s
owner.

SET LANGUAGE

Syntax: /msg NickServ SET LANGUAGE number

Changes the language Services uses when sending messages to
you (for example, when responding to a command you send).
number should be chosen from the following list of
supported languages:

SET URL

Syntax: /msg NickServ SET URL url

Associates the given URL with your nickname. This URL
will be displayed whenever someone requests information
on your nick with the INFO command.

SET EMAIL

Syntax: /msg NickServ SET EMAIL address

Associates the given E-mail address with your nickname.
This address will be displayed whenever someone requests
information on the channel with the INFO command.

SET ICQ

Syntax: /msg NickServ SET ICQ number

Associates the given ICQ number with your nickname. This
number will be displayed whenever someone requests
information on your nick with the INFO command.

SET GREET

Syntax: /msg NickServ SET GREET message

Makes the given message the greet of your nickname, that
will be displayed when joining a channel that has GREET
option enabled, provided that you have the necessary
access on it.

SET KILL

Syntax: /msg NickServ SET KILL {ON | QUICK | IMMED | OFF}

Turns the automatic protection option for your nick
on or off. With protection on, if another user
tries to take your nick, they will be given one minute to
change to another nick, after which NickServ will forcibly change
their nick.

If you select QUICK, the user will be given only 20 seconds
to change nicks instead of the usual 60. If you select
IMMED, user\\'s nick will be changed immediately without being
warned first or given a chance to change their nick; please
do not use this option unless necessary. Also, your
network\\'s administrators may have disabled this option.

SET SECURE

Syntax: /msg NickServ SET SECURE {ON | OFF}

Turns NickServ\\'s security features on or off for your
nick. With SECURE set, you must enter your password
before you will be recognized as the owner of the nick,
regardless of whether your address is on the access
list. However, if you are on the access list, NickServ
will not auto-kill you regardless of the setting of the
KILL option.

SET PRIVATE

Syntax: /msg NickServ SET PRIVATE {ON | OFF}

Turns NickServ\\'s privacy option on or off for your nick.
With PRIVATE set, your nickname will not appear in
nickname lists generated with NickServ\\'s LIST command.
(However, anyone who knows your nickname can still get
information on it using the INFO command.)

SET HIDE

Syntax: /msg NickServ SET HIDE {EMAIL | USERMASK | QUIT} {ON | OFF}

Allows you to prevent certain pieces of information from
being displayed when someone does a NickServ INFO on your
nick. You can hide your E-mail address (EMAIL), last seen
user@host mask (USERMASK), and last quit message (QUIT).
The second parameter specifies whether the information should
be displayed (OFF) or hidden (ON).

SET MSG

Syntax: /msg NickServ SET MSG {ON | OFF}

Allows you to choose the way Services are communicating with
you. With MSG set, Services will use messages, else they\\'ll
use notices.

RECOVER

Syntax: /msg NickServ RECOVER nickname [password]

Allows you to recover your nickname if someone else has
taken it; this does the same thing that NickServ does
automatically if someone tries to use a kill-protected
nick.

When you give this command, NickServ will bring a fake
user online with the same nickname as the user you\\'re
trying to recover your nick from. This causes the IRC
servers to disconnect the other user. This fake user will
will remain online for one minute to ensure that the other
user does not immediately reconnect; after that minute, you
can reclaim your nick. Alternatively, use the RELEASE
command ( /msg NickServ HELP RELEASE) to get the nick
back sooner.

In order to use the RECOVER command for a nick, your
current address as shown in /WHOIS must be on that nick\\'s
access list, you must be identified and in the group of
that nick, or you must supply the correct password for
the nickname.

RELEASE

Syntax: /msg NickServ RELEASE nickname [password]

Instructs NickServ to remove any hold on your nickname
caused by automatic kill protection or use of the RECOVER
command. By default, such holds last for one minute;
this command gets rid of them sooner.

In order to use the RELEASE command for a nick, your
current address as shown in /WHOIS must be on that nick\\'s
access list, you must be identified and in the group of
that nick, or you must supply the correct password for
the nickname.

GHOST

Syntax: /msg NickServ GHOST nickname [password]

Terminates a \\"ghost\\" IRC session using your nick. A
\\"ghost\\" session is one which is not actually connected,
but which the IRC server believes is still online for one
reason or another. Typically, this happens if your
computer crashes or your Internet or modem connection
goes down while you\\'re on IRC.

In order to use the GHOST command for a nick, your
current address as shown in /WHOIS must be on that nick\\'s
access list, you must be identified and in the group of
that nick, or you must supply the correct password for
the nickname.

INFO

Syntax: /msg NickServ INFO nickname [ALL]

Displays information about the given nickname, such as
the nick\\'s owner, last seen address and time, and nick
options. If you are identified for the nick you\\'re
getting information for and ALL is specified, you will
be shown all the information; regardless of whether
it\\'s hidden or not.

LIST

Syntax: /msg NickServ LIST pattern

Lists all registered nicknames which match the given
pattern, in nick!user@host format. Nicks with the
PRIVATE option set will not be displayed.

Examples:

LIST *!joeuser@foo.com
Lists all nicks owned by joeuser@foo.com.

LIST *Bot*!*@*
Lists all registered nicks with Bot in their
names (case insensitive).

LIST *!*@*.bar.org
Lists all nicks owned by users in the bar.org
domain.

ALIST

Syntax: /msg NickServ ALIST [level]

Lists all channels you have access on. Optionally, you can specify
a level in XOP or ACCESS format. The resulting list will only
include channels where you have the given level of access.

Examples:
ALIST Founder
     Lists all channels where you have Founder
       access.

    ALIST AOP
     Lists all channels where you have AOP access
       or greater.

    ALIST 10
     Lists all channels where you have level 10
       access or greater.

Channels that have the NOEXPIRE option set will be prefixed by
an exclamation mark.

GLIST

Syntax: /msg NickServ GLIST

Lists all nicks in your group.

STATUS

Syntax: /msg NickServ STATUS nickname...

Returns whether the user using the given nickname is
recognized as the owner of the nickname. The response has
this format:

nickname status-code

where nickname is the nickname sent with the command, and
status-code is one of the following:

0 - no such user online or nickname not registered
1 - user not recognized as nickname\\'s owner
2 - user recognized as owner via access list only
3 - user recognized as owner via password identification

Up to sixteen nicknames may be sent with each command; the
rest will be ignored. No error message is generated if no
nickname is given.

SENDPASS

Syntax: /msg NickServ SENDPASS nickname

Send the password of the given nickname to the e-mail address
set in the nickname record. This command is really useful
to deal with lost passwords.

May be limited to IRC operators on certain networks.

This command is unavailable when encryption is enabled.

SERVADMIN HELP

The following commands are available to Services admins:

GETPASS Retrieve the password for a nickname
(only if encryption is disabled)
FORBID Prevent a nickname from being used

Services admins can also drop any nickname without needing
to identify for the nick, and may view the access list for
any nickname ( /msg NickServ ACCESS LIST nick).

SERVADMIN LOGOUT

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.

SERVADMIN DROP

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 is limited to
Services admins.

SERVADMIN SET

Services admins can also set the option NOEXPIRE, with
which nicknames can be prevented from expiring.
Additionally, Services admins can set options for any
nickname without entering a password, using the format
SET nickname option parameters.

SERVADMIN SET NOEXPIRE

Syntax: /msg NickServ SET [nickname] NOEXPIRE {ON | OFF}

Sets whether the given nickname will expire. Setting this
to ON prevents the nickname from expiring. If no
nickname is given, sets the no-expire flag for your nick.

Limited to Services admins.

SERVADMIN LIST

Syntax: /msg NickServ LIST pattern [FORBIDDEN] [NOEXPIRE]

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 ! prepended to the
nickname for Services admins.

If the FORBIDDEN or NOEXPIRE options are given, only nicks
which, respectively, are FORBIDden or have the NOEXPIRE flag
set will be displayed. If both options are given, both
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.

SERVADMIN ALIST

Syntax: /msg NickServ ALIST [nickname] [level]

With no parameters, lists channels you have access on. With
one parameter, lists channels that nickname has access
on. With two parameters lists channels that nickname has
level access or greater on.

This use limited to Services admins.

SERVADMIN GLIST

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.

SERVADMIN GETPASS

Syntax: /msg NickServ GETPASS nickname

Returns the password for the given nickname. Note that
whenever this command is used, a message including the
person 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.

This command is unavailable when encryption is enabled.

SERVADMIN FORBID

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.

PT-NGS- · June 25, 2006, 10:46:23 AM

HELP

OperServ commands:
GLOBAL Send a message to all users
STATS Show status of Services and network
OPER LIST List all Services operators
ADMIN LIST List all Services admins

Commands available to Services operators and admins only:
MODE Change a channel\\'s modes
KICK Kick a user from a channel
CLEARMODES Clear modes of a channel
KILLCLONES Kill all users that have a certain host
AKILL Manipulate the AKILL list
SGLINE Manipulate the SGLINE list
SQLINE Manipulate the SQLINE list
SZLINE Manipulate the SZLINE list

Commands available to Services admins only:
OPER Modify the Services operator list
CHANLIST Lists all channel records
USERLIST Lists all user records
LOGONNEWS Define messages to be shown to users at logon
RANDOMNEWS Define messages to be randomly shown to users
at logon
OPERNEWS Define messages to be shown to users who oper
SESSION View the list of host sessions
EXCEPTION Modify the session-limit exception list
CACHE Lists hostname cache used by the proxy detector
NOOP Temporarily remove all O:lines of a server
remotely
JUPE \\"Jupiter\\" a server
IGNORE Modify the Services ignore list
UMODE Change a user\\'s modes
OLINE Give Operflags to a certain user (UnrealIRCd
only)
SET Set various global Services options
RELOAD Reload services\\' configuration file
UPDATE Force the Services databases to be
updated on disk immediately
RESTART Save databases and restart Services
QUIT Terminate the Services program with no save
SHUTDOWN Terminate the Services program with save

Commands available to the Services super-user only:
ADMIN Modify the Services admin list

Notice: All commands sent to OperServ are logged!

GLOBAL

Syntax: /msg OperServ GLOBAL message

Allows IRCops to send messages to all users on the network.
The message will be sent from the nick OperServ.

STATS

Syntax: /msg OperServ STATS [AKILL | ALL | RESET]

Without any option, shows the current number of users and
IRCops online (excluding Services), the highest number of
users online since Services was started, and the length of
time Services has been running.

With the AKILL option, displays the current size of the
AKILL list and the current default expiry time.

The ALL option is available only to Services admins, and
displays information on Services\\' memory usage. Using this
option can freeze Services for a short period of time on
large networks, so don\\'t overuse it!

The RESET option currently resets the maximum user count
to the number of users currently present on the network.

UPTIME may be used as a synonym for STATS.

OPER

Syntax: /msg OperServ OPER ADD nick
OPER DEL {nick | entry-num | list}
OPER LIST [mask | list]
OPER CLEAR

Allows the Services admins to add or remove nicknames
to or from the Services operator list. A user whose nickname
is on the Services operator list and who has identified to
OperServ will be able to access Services operator commands.

The OPER ADD command adds the given nickname to the
Services operator list.

The OPER DEL command removes the given nick from the
Services operator list. If a list of entry numbers is given,
those entries are deleted. (See the example for LIST below.)

The OPER LIST command displays the Services operator list.
If a wildcard mask is given, only those entries matching the
mask are displayed. If a list of entry numbers is given,
only those entries are shown; for example:

OPER LIST 2-5,7-9
Lists Services operator entries numbered 2 through
5 and 7 through 9.

The OPER CLEAR command clears all entries of the
Services operator list.

Any IRC operator may use the OPER LIST form of the command.
All other use limited to Services admins.

ADMIN

Syntax: /msg OperServ ADMIN ADD nick
ADMIN DEL {nick | entry-num | list}
ADMIN LIST [mask | list]
ADMIN CLEAR

Allows the Services root to add or remove nicknames
to or from the Services admin list. A user whose nickname
is on the Services admin list and who has identified to
OperServ will be able to access Services admin commands.

The ADMIN ADD command adds the given nickname to the
Services admin list.

The ADMIN DEL command removes the given nick from the
Services admin list. If a list of entry numbers is given,
those entries are deleted. (See the example for LIST below.)

The ADMIN LIST command displays the Services admin list.
If a wildcard mask is given, only those entries matching the
mask are displayed. If a list of entry numbers is given,
only those entries are shown; for example:

ADMIN LIST 2-5,7-9
Lists Services admin entries numbered 2 through
5 and 7 through 9.

The ADMIN CLEAR command clears all entries of the
Services admin list.

Any IRC operator may use the ADMIN LIST form of the command.
All other use limited to Services root.

IGNORE

Syntax: /msg OperServ IGNORE {ADD|DEL|LIST|CLEAR} [time] [nick]

Allows Services Admins to make Services ignore a nick for a
certain time or until the next restart. The default time
format is seconds. You can specify it by using units. Valid
units are: s for seconds, m for minutes, h for hours and
d for days. Combinations of these units are not permitted. To
make Services permanently ignore the user type 0 as time.

MODE

Syntax: /msg OperServ MODE channel modes

Allows Services operators to set channel modes for any
channel. Parameters are the same as for the standard /MODE
command.

Limited to Services operators.

UMODE

Syntax: /msg OperServ UMODE user modes

Allows Services admins to set user modes for any user.
Parameters are the same as for the standard /MODE
command.

Limited to Services admins.

OLINE

Syntax: /msg OperServ OLINE user flags

Allows Services admins to give Operflags to any user.
Flags have to be prefixed with a \\"+\\" or a \\"-\\". To
remove all flags simply type a \\"-\\" instead of any flags.

Limited to Services admins.

CLEARMODES

Syntax: /msg OperServ CLEARMODES channel [ALL]

Clears all binary modes (i,k,l,m,n,p,s,t) and bans from a
channel. If ALL is given, also clears all ops and
voices ( +o and +v modes) from the channel.

Limited to Services operators.

KICK

Syntax: /msg OperServ KICK channel user reason

Allows IRCops to kick a user from any channel.
Parameters are the same as for the standard /KICK
command. The kick message will have the nickname of the
IRCop sending the KICK command prepended; for example:

*** SpamMan has been kicked off channel #my_channel by OperServ (Alcan (Flood))

Limited to Services operators.

AKILL

Syntax: /msg OperServ AKILL ADD [+expiry] mask reason
AKILL DEL {mask | entry-num | list}
AKILL LIST [mask | list]
AKILL VIEW [mask | list]
AKILL CLEAR

Allows Services operators to manipulate the AKILL list. If
a user matching an AKILL mask attempts to connect, Services
will issue a KILL for that user and, on supported server
types, will instruct all servers to add a ban (K-line) for
the mask which the user matched.

AKILL ADD adds the given user@host/ip mask to the AKILL
list for the given reason (which must be given).
expiry is specified as an integer followed by one of d
(days), h (hours), or m (minutes). Combinations (such as
1h30m) are not permitted. If a unit specifier is not
included, the default is days (so +30 by itself means 30
days). To add an AKILL which does not expire, use +0. If the
usermask to be added starts with a +, an expiry time must
be given, even if it is the same as the default. The
current AKILL default expiry time can be found with the
STATS AKILL command.

The AKILL DEL command removes the given mask from the
AKILL list if it is present. If a list of entry numbers is
given, those entries are deleted. (See the example for LIST
below.)

The AKILL LIST command displays the AKILL list.
If a wildcard mask is given, only those entries matching the
mask are displayed. If a list of entry numbers is given,
only those entries are shown; for example:

AKILL LIST 2-5,7-9
Lists AKILL entries numbered 2 through 5 and 7
through 9.

AKILL VIEW is a more verbose version of AKILL LIST, and
will show who added an AKILL, the date it was added, and when
it expires, as well as the user@host/ip mask and reason.

AKILL CLEAR clears all entries of the AKILL list.

Limited to Services operators.

SGLINE

Syntax: /msg OperServ SGLINE ADD [+expiry] mask:reason
    SGLINE DEL {mask | entry-num | list}
SGLINE LIST [mask | list]
SGLINE VIEW [mask | list]
SGLINE CLEAR

Allows Services operators to manipulate the SGLINE list. If
a user with a realname matching an SGLINE mask attempts to
connect, Services will not allow it to pursue his IRC
session.

SGLINE ADD adds the given realname mask to the SGLINE
list for the given reason (which must be given).
expiry is specified as an integer followed by one of d
(days), h (hours), or m (minutes). Combinations (such as
1h30m) are not permitted. If a unit specifier is not
included, the default is days (so +30 by itself means 30
days). To add an SGLINE which does not expire, use +0. If the
realname mask to be added starts with a +, an expiry time must
be given, even if it is the same as the default. The
current SGLINE default expiry time can be found with the
STATS AKILL command.
Note: because the realname mask may contain spaces, the
separator between it and the reason is a colon.

The SGLINE DEL command removes the given mask from the
SGLINE list if it is present. If a list of entry numbers is
given, those entries are deleted. (See the example for LIST
below.)

The SGLINE LIST command displays the SGLINE list.
If a wildcard mask is given, only those entries matching the
mask are displayed. If a list of entry numbers is given,
only those entries are shown; for example:

SGLINE LIST 2-5,7-9
Lists SGLINE entries numbered 2 through 5 and 7
through 9.

SGLINE VIEW is a more verbose version of SGLINE LIST, and
will show who added an SGLINE, the date it was added, and when
it expires, as well as the realname mask and reason.

SGLINE CLEAR clears all entries of the SGLINE list.

Limited to Services operators.

SQLINE

Syntax: /msg OperServ SQLINE ADD [+expiry] mask:reason
    SQLINE DEL {mask | entry-num | list}
SQLINE LIST [mask | list]
SQLINE VIEW [mask | list]
SQLINE CLEAR

Allows Services operators to manipulate the SQLINE list. If
a user with a nick matching an SQLINE mask attempts to
connect, Services will not allow it to pursue his IRC
session.

If the first character of the mask is #, services will
prevent the use of matching channels (on IRCds that
support it).

SQLINE ADD adds the given mask to the SQLINE
list for the given reason (which must be given).
expiry is specified as an integer followed by one of d
(days), h (hours), or m (minutes). Combinations (such as
1h30m) are not permitted. If a unit specifier is not
included, the default is days (so +30 by itself means 30
days). To add an SQLINE which does not expire, use +0.
If the mask to be added starts with a +, an expiry time
must be given, even if it is the same as the default. The
current SQLINE default expiry time can be found with the
STATS AKILL command.

The SQLINE DEL command removes the given mask from the
SQLINE list if it is present. If a list of entry numbers is
given, those entries are deleted. (See the example for LIST
below.)

The SQLINE LIST command displays the SQLINE list.
If a wildcard mask is given, only those entries matching the
mask are displayed. If a list of entry numbers is given,
only those entries are shown; for example:

SQLINE LIST 2-5,7-9
Lists SQLINE entries numbered 2 through 5 and 7
through 9.

SQLINE VIEW is a more verbose version of SQLINE LIST, and
will show who added an SQLINE, the date it was added, and when
it expires, as well as the mask and reason.

SQLINE CLEAR clears all entries of the SQLINE list.

Limited to Services operators.

SZLINE

Syntax: /msg OperServ SZLINE ADD [+expiry] mask reason
SZLINE DEL {mask | entry-num | list}
SZLINE LIST [mask | list]
SZLINE VIEW [mask | list]
SZLINE CLEAR

Allows Services operators to manipulate the SZLINE list. If
a user with an IP matching an SZLINE mask attempts to
connect, Services will not allow it to pursue his IRC
session (and this, whether the IP has a PTR RR or not).

SZLINE ADD adds the given IP mask to the SZLINE
list for the given reason (which must be given).
expiry is specified as an integer followed by one of d
(days), h (hours), or m (minutes). Combinations (such as
1h30m) are not permitted. If a unit specifier is not
included, the default is days (so +30 by itself means 30
days). To add an SZLINE which does not expire, use +0. If the
realname mask to be added starts with a +, an expiry time must
be given, even if it is the same as the default. The
current SZLINE default expiry time can be found with the
STATS AKILL command.

The SZLINE DEL command removes the given mask from the
SZLINE list if it is present. If a list of entry numbers is
given, those entries are deleted. (See the example for LIST
below.)

The SZLINE LIST command displays the SZLINE list.
If a wildcard mask is given, only those entries matching the
mask are displayed. If a list of entry numbers is given,
only those entries are shown; for example:

SZLINE LIST 2-5,7-9
Lists SZLINE entries numbered 2 through 5 and 7
through 9.

SZLINE VIEW is a more verbose version of SZLINE LIST, and
will show who added an SZLINE, the date it was added, and when
it expires, as well as the IP mask and reason.

SZLINE CLEAR clears all entries of the SZLINE list.

Limited to Services operators.

SET

Syntax: /msg OperServ SET option setting

Sets various global Services options. Option names
currently defined are:
READONLY Set read-only or read-write mode
LOGCHAN Report log messages to a channel
DEBUG Activate or deactivate debug mode
NOEXPIRE Activate or deactivate no expire mode
SUPERADMIN Activate or deactivate super-admin mode

Limited to Services admins.

SET READONLY

Syntax: /msg OperServ SET READONLY {ON | OFF}

Sets read-only mode on or off. In read-only mode, normal
users will not be allowed to modify any Services data,
including channel and nickname access lists, etc. IRCops
with sufficient Services privileges will be able to modify
Services\\' AKILL list and drop or forbid nicknames and
channels, but any such changes will not be saved unless
read-only mode is deactivated before Services is terminated
or restarted.

This option is equivalent to the command-line option
-readonly.

SET LOGCHAN

Syntax: /msg OperServ SET LOGCHAN {ON | OFF}

With this setting on, Services will send its logs to a specified
channel as well as the log file. LogChannel must also be defined
in the Services configuration file for this setting to be of any
use.

Note: This can have strong security implications if your log
channel is not properly secured.

SET DEBUG

Syntax: /msg OperServ SET DEBUG {ON | OFF | num}

Sets debug mode on or off. In debug mode, all data sent to
and from Services as well as a number of other debugging
messages are written to the log file. If num is
given, debug mode is activated, with the debugging level set
to num.

This option is equivalent to the command-line option
-debug.

SET NOEXPIRE

Syntax: /msg OperServ SET NOEXPIRE {ON | OFF}

Sets no expire mode on or off. In no expire mode, nicks,
channels, akills and exceptions won\\'t expire until the
option is unset.

This option is equivalent to the command-line option
-noexpire.

SET SUPERADMIN

Syntax: /msg OperServ SET SUPERADMIN {ON | OFF}

Setting this will grant you extra privlages such as the
ability to be \\"founder\\" on all channel\\'s etc...

This opion is not persistant, and should only be used when
needed, and set back to OFF when no longer needed.

NOOP

Syntax: /msg OperServ NOOP SET server
NOOP REVOKE server

NOOP SET remove all O:lines of the given
server and kill all IRCops currently on it to
prevent them from rehashing the server (because this
would just cancel the effect).

NOOP REVOKE makes all removed O:lines available again
on the given server.

Note: The server is not checked at all by the
Services.

Limited to Services admins.

JUPE

Syntax: /msg OperServ JUPE server [reason]

Tells Services to jupiter a server -- that is, to create
a fake \\"server\\" connected to Services which prevents
the real server of that name from connecting. The jupe
may be removed using a standard SQUIT. If a reason is
given, it is placed in the server information field;
otherwise, the server information field will contain the
text \\"Juped by <nick>\\", showing the nickname of the
person who jupitered the server.

Limited to Services admins.

RAW

Syntax: /msg OperServ RAW text

Sends a string of text directly to the server to which
Services is connected. This command has a very limited
range of uses, and can wreak havoc on a network if used
improperly. DO NOT USE THIS COMMAND unless you are
absolutely certain you know what you are doing!

Limited to Services admins.

UPDATE

Syntax: /msg OperServ UPDATE

Causes Services to update all database files as soon as you
send the command.

Limited to Services admins.

RELOAD

Syntax: /msg OperServ RELOAD

Causes Services to reload the configuration file. Note that
some directives still need the restart of the Services to
take effect (such as Services\\' nicknames, activation of the
session limitation, etc.)

Limited to Services admins.

QUIT

Syntax: /msg OperServ QUIT

Causes Services to do an immediate shutdown; databases are
not saved. This command should not be used unless
damage to the in-memory copies of the databases is feared
and they should not be saved. For normal shutdowns, use the
SHUTDOWN command.

Limited to Services admins.

SHUTDOWN

Syntax: /msg OperServ SHUTDOWN

Causes Services to save all databases and then shut down.

Limited to Services admins.

RESTART

Syntax: /msg OperServ RESTART

Causes Services to save all databases and then restart
(i.e. exit and immediately re-run the executable).

Limited to Services admins.

KILLCLONES

Syntax: /msg OperServ KILLCLONES nick

Kills all users who have the same hostname as nick. A
temporary AKILL, in the form *@host, is added to
prevent the offending clients from immediately
reconnecting. A wallops is also sent indicating who
used the command, which host was affected and how many
users were killed. It\\'s usefull for removing numerous
clones from the network.

Limited to Services operators.

CHANLIST

Syntax: /msg OperServ CHANLIST [{pattern | nick} [SECRET]]

Lists all channels currently in use on the IRC network, whether they
are registered or not.

If pattern is given, lists only channels that match it. If a nickname
is given, lists only the channels the user using it is on. If SECRET is
specified, lists only channels matching pattern that have the +s or
+p mode.

Limited to Services admins.

USERLIST

Syntax: /msg OperServ USERLIST [{pattern | channel} [INVISIBLE]]

Lists all users currently online on the IRC network, whether their
nick is registered or not.

If pattern is given, lists only users that match it (it must be in
the format nick!user@host). If channel is given, lists only users
that are on the given channel. If INVISIBLE is specified, only users
with the +i flag will be listed.

Limited to Services admins.

CACHE

Syntax: /msg OperServ CACHE DEL hostname
CACHE LIST pattern [QUEUED | ALL]

The CACHE DEL command deletes the specified hostname from
the cache. This is meant for debug purpose only.

The CACHE LIST command lists all found proxies that match the
given pattern. If the QUEUED option is given, it will list
the queued or in progress scans instead, and if the ALL option
is given, it will list all cached hostnames.

Limited to Services admins.

EXCEPTION

Syntax: /msg OperServ EXCEPTION ADD [+expiry] mask limit reason
EXCEPTION DEL {mask | list}
EXCEPTION MOVE num position
EXCEPTION LIST [mask | list]
EXCEPTION VIEW [mask | list]

Allows Services admins to manipulate the list of hosts that
have specific session limits - allowing certain machines,
such as shell servers, to carry more than the default number
of clients at a time. Once a host reaches it\\'s session limit,
all clients attempting to connect from that host will be
killed. Before the user is killed, they are notified, via a
/NOTICE from OperServ, of a source of help regarding session
limiting. The content of this notice is a config setting.

EXCEPTION ADD adds the given host mask to the exception list.
Note that nick!user@host and user@host masks are invalid!
Only real host masks, such as box.host.dom and *.host.dom,
are allowed because sessions limiting does not take nick or
user names into account. limit must be a number greater than
or equal to zero. This determines how many sessions this host
may carry at a time. A value of zero means the host has an
unlimited session limit. See the AKILL help for details about
the format of the optional expiry parameter.
EXCEPTION DEL removes the given mask from the exception list.
EXCEPTION MOVE moves exception num to position. The
exceptions inbetween will be shifted up or down to fill the gap.
EXCEPTION LIST and EXCEPTION VIEW show all current
exceptions; if the optional mask is given, the list is limited
to those exceptions matching the mask. The difference is that
EXCEPTION VIEW is more verbose, displaying the name of the
person who added the exception, it\\'s session limit, reason,
host mask and the expiry date and time.

Note that a connecting client will \\"use\\" the first exception
their host matches. Large exception lists and widely matching
exception masks are likely to degrade services\\' performance.

Limited to Services admins.

SESSION

Syntax: /msg OperServ SESSION LIST threshold
SESSION VIEW host

Allows Services admins to view the session list.

SESSION LIST lists hosts with atleast threshold sessions.
The threshold must be a number greater than 1. This is to
prevent accidental listing of the large number of single
session hosts.
SESSION VIEW displays detailed information about a specific
host - including the current session count and session limit.
The host value may not include wildcards.

See the EXCEPTION help for more information about session
limiting and how to set session limits specific to certain
hosts and groups thereof.

Limited to Services admins.

PT-NGS- · June 25, 2006, 10:47:15 AM

HELP

MemoServ is a utility allowing IRC users to send short
messages to other IRC users, whether they are online at
the time or not, or to channels(*). Both the sender\\'s
nickname and the target nickname or channel must be
registered in order to send a memo.

MemoServ\\'s commands include:

SEND Send a memo to a nick or channel
CANCEL Cancel last memo you sent
LIST List your memos
READ Read a memo or memos
DEL Delete a memo or memos
SET Set options related to memos

Type /msg MemoServ HELP command for help on any of the
above commands.

(*) By default, any user with at least level 10 access on a
channel can read that channel\\'s memos. This can be
changed with the MemoServ LEVELS command.

SEND

Syntax: /msg MemoServ SEND {nick | channel} memo-text

Sends the named nick or channel a memo containing
memo-text. When sending to a nickname, the recipient will
receive a notice that he/she has a new memo. The target
nickname/channel must be registered.

CANCEL

Syntax: /msg MemoServ CANCEL {nick | channel}

Cancels the last memo you sent to the given nick or channel,
provided it has not been read at the time you use the command.

LIST

Syntax: /msg MemoServ LIST [channel]

*\\"
to the left of the memo number. You can also specify a list
of numbers, as in the example below:

LIST 2-5,7-9
Lists memos numbered 2 through 5 and 7 through 9.

READ

Syntax: /msg MemoServ READ [channel] {num | list | LAST | NEW}

Sends you the text of the memos specified. If LAST is
given, sends you the memo you most recently received. If
NEW is given, sends you all of your new memos. Otherwise,
sends you memo number num. You can also give a list of
numbers, as in this example:

READ 2-5,7-9
Displays memos numbered 2 through 5 and 7 through 9.

DEL

Syntax: /msg MemoServ DEL [channel] {num | list | LAST | ALL}

Deletes the specified memo or memos. You can supply
multiple memo numbers or ranges of numbers instead of a
single number, as in the second example below.

If LAST is given, the last memo will be deleted.
If ALL is given, deletes all of your memos.

Examples:

DEL 1
Deletes your first memo.

DEL 2-5,7-9
Deletes memos numbered 2 through 5 and 7 through 9.

SET

Syntax: /msg MemoServ SET option parameters

Sets various memo options. option can be one of:

NOTIFY Changes when you will be notified about
new memos (only for nicknames)
LIMIT Sets the maximum number of memos you can
receive

Type /msg MemoServ HELP SET option for more information
on a specific option.

SET NOTIFY

Syntax: /msg MemoServ SET NOTIFY {ON | LOGON | NEW | OFF}

Changes when you will be notified about new memos:

ON You will be notified of memos when you log on,
when you unset /AWAY, and when they are sent
to you.
LOGON You will only be notified of memos when you log
on or when you unset /AWAY.
NEW You will only be notified of memos when they
are sent to you.
OFF You will not receive any notification of memos.

ON is essentially LOGON and NEW combined.

SET LIMIT

Syntax: /msg MemoServ SET LIMIT [channel] limit

Sets the maximum number of memos you (or the given channel)
are allowed to have. If you set this to 0, no one will be
able to send any memos to you. However, you cannot set
this any higher than <num>.

INFO

Syntax: /msg MemoServ INFO [channel]

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 parameter, displays the same information
for the given channel.

SERVADMIN SET LIMIT

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.

SERVADMIN INFO

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.

PT-NGS- · June 25, 2006, 10:47:46 AM

HELP

HostServ commands:
ON Activates your assigned vhost
OFF Deactivates your assigned vhost
GROUP Syncs the Vhost for all nicks in a group

OPER HELP

Commands available to services operators only:
SET Set the vhost of another user
SETALL Set the vhost for all nicks in a group
DEL Delete the vhost of another user

ADMIN HELP

Commands available to services admins only:
LIST Displays one or more vhost entries.

ON

Syntax: /msg HostServ ON

Activates the vhost currently assigned to the nick in use.
When you use this command any user who performs a /whois
on you will see the vhost instead of your real IP address.

SET

Syntax: /msg HostServ SET <nick> <hostmask>.

Sets the vhost for the given nick to that of the given
hostmask. If your IRCD supports vIdents, then using
SET <nick> <ident>@<hostmask> set idents for users as
well as vhosts.

Limited to Services operators.

SETALL

Syntax: /msg HostServ SETALL <nick> <hostmask>.

Sets the vhost for all nicks in the same group as that
of the given nick. If your IRCD supports vIdents, then
using SETALL <nick> <ident>@<hostmask> will set idents
for users as well as vhosts.

* NOTE, this will not update the vhost for any nick\\'s
added to the group after this command was used.

Limited to Services operators.

OFF

Syntax: /msg HostServ OFF

Deactivates the vhost currently assigned to the nick in use.
When you use this command any user who performs a /whois
on you will see your real IP address.

DEL

Syntax: /msg HostServ DEL <nick>

Deletes the vhost assigned to the given nick from the
database.

Limited to Services operators.

LIST

Syntax: /msg HostServ LIST [<nick>|<vhost>]

This command outputs all registered vhosts to the operator,
specifiying a nick or vhost will display the owner / vhost
for exact matchs only. NOTE: there is currently no flood
protection for large DB files.

Limited to Services admins.

GROUP

Syntax: /msg HostServ GROUP

This command allows users to set the vhost of thier
CURRENT nick to be the vhost for all nicks in the same
group.

PT-NGS- · June 25, 2006, 10:48:14 AM

HELP

BotServ allows you to have a bot on your own channel.
It has been created for users that can\\'t host or
configure a bot, or for use on networks that don\\'t
allow users\\' bot. Available commands are listed
below; to use them, type /msg BotServ command. For
more information on a specific command, type /msg
BotServ HELP command.

BOTLIST Lists available bots
ASSIGN Assigns a bot to a channel
SET Configures bot options
KICK Configures kickers
BADWORDS Maintains bad words list

Other commands: ACT INFO SAY UNASSIGN

Bot will join a channel whenever there is at least
<num> user(s) on it.

BOTLIST

Syntax: /msg BotServ BOTLIST

Lists all available bots on this network.

ASSIGN

Syntax: /msg BotServ ASSIGN chan nick

Assigns a bot pointed out by nick to the channel chan. You
can then configure the bot for the channel so it fits
your needs.

UNASSIGN

Syntax: /msg BotServ UNASSIGN chan

Unassigns a bot from a channel. When you use this command,
the bot won\\'t join the channel anymore. However, bot
configuration for the channel is kept, so you will always
be able to reassign a bot later without have to reconfigure
it entirely.

INFO

Syntax: /msg BotServ INFO {chan | nick}

Allows you to see BotServ information about a channel or a bot.
If the parameter is a channel, then you\\'ll get information
such as enabled kickers. If the parameter is a nick,
you\\'ll get information about a bot, such as creation
time or number of channels it is on.

SET

Syntax: /msg BotServ SET channel option parameters

Configures bot options. option can be one of:

DONTKICKOPS To protect ops against bot kicks
DONTKICKVOICES To protect voices against bot kicks
GREET Enable greet messages
FANTASY Enable fantaisist commands
SYMBIOSIS Allow the bot to act as a real bot

Type /msg BotServ HELP SET option for more information
on a specific option.

Note: access to this command is controlled by the
level SET.

SET DONTKICKOPS

Syntax: /msg BotServ SET channel DONTKICKOPS {ON|OFF}

Enables or disables ops protection mode on a channel.
When it is enabled, ops won\\'t be kicked by the bot
even if they don\\'t match the NOKICK level.

SET DONTKICKVOICES

Syntax: /msg BotServ SET channel DONTKICKVOICES {ON|OFF}

Enables or disables voices protection mode on a channel.
When it is enabled, voices won\\'t be kicked by the bot
even if they don\\'t match the NOKICK level.

SET FANTASY

Syntax: /msg BotServ SET channel FANTASY {ON|OFF}

Enables or disables fantasy mode on a channel.
When it is enabled, users will be able to use
commands !op, !deop, !voice, !devoice,
!kick, !kb, !unban, !seen on a channel (find how
to use them; try with or without nick for each,
and with a reason for some?).

Note that users wanting to use fantaisist
commands MUST have enough level for both
the FANTASIA and another level depending
of the command if required (for example, to use
!op, user must have enough access for the OPDEOP
level).

SET GREET

Syntax: /msg BotServ SET channel GREET {ON|OFF}

Enables or disables greet mode on a channel.
When it is enabled, the bot will display greet
messages of users joining the channel, provided
they have enough access to the channel.

SET SYMBIOSIS

Syntax: /msg BotServ SET channel SYMBIOSIS {ON|OFF}

Enables or disables symbiosis mode on a channel.
When it is enabled, the bot will do everything
normally done by BotServ on channels, such as MODEs,
KICKs, and even the entry message.

KICK

Syntax: /msg BotServ KICK channel option parameters

Configures bot kickers. option can be one of:

BOLDS Sets if the bot kicks bolds
BADWORDS Sets if the bot kicks bad words
CAPS Sets if the bot kicks caps
COLORS Sets if the bot kicks colors
FLOOD Sets if the bot kicks flooding users
REPEAT Sets if the bot kicks users who repeat
themselves
REVERSES Sets if the bot kicks reverses
UNDERLINES Sets if the bot kicks underlines

Type /msg BotServ HELP KICK option for more information
on a specific option.

Note: access to this command is controlled by the
level SET.

KICK BOLDS

Syntax: /msg BotServ KICK channel BOLDS {ON|OFF} [ttb]

Sets the bolds kicker on or off. When enabled, this
option tells the bot to kick users who use bolds.

ttb is the number of times an user can be kicked
before it get banned. Don\\'t give ttb to disable
the ban system once activated.

KICK COLORS

Syntax: /msg BotServ KICK channel COLORS {ON|OFF} [ttb]

Sets the colors kicker on or off. When enabled, this
option tells the bot to kick users who use colors.

ttb is the number of times an user can be kicked
before it get banned. Don\\'t give ttb to disable
the ban system once activated.

KICK REVERSES

Syntax: /msg BotServ KICK channel REVERSES {ON|OFF} [ttb]

Sets the reverses kicker on or off. When enabled, this
option tells the bot to kick users who use reverses.

ttb is the number of times an user can be kicked
before it get banned. Don\\'t give ttb to disable
the ban system once activated.

KICK UNDERLINES

Syntax: /msg BotServ KICK channel UNDERLINES {ON|OFF} [ttb]

Sets the underlines kicker on or off. When enabled, this
option tells the bot to kick users who use underlines.

ttb is the number of times an user can be kicked
before it get banned. Don\\'t give ttb to disable
the ban system once activated.

KICK CAPS

Syntax: /msg BotServ KICK channel CAPS {ON|OFF} [ttb [min [percent]]]

Sets the caps kicker on or off. When enabled, this
option tells the bot to kick users who are talking in
CAPS.

The bot kicks only if there are at least min caps
and they constitute at least percent%% of the total
text line (if not given, it defaults to 10 characters
and 25%%).

ttb is the number of times an user can be kicked
before it get banned. Don\\'t give ttb to disable
the ban system once activated.

KICK FLOOD

Syntax: /msg BotServ KICK channel FLOOD {ON|OFF} [ttb [ln [secs]]]

Sets the flood kicker on or off. When enabled, this
option tells the bot to kick users who are flooding
the channel using at least ln lines in secs seconds
(if not given, it defaults to 6 lines in 10 seconds).

ttb is the number of times an user can be kicked
before it get banned. Don\\'t give ttb to disable
the ban system once activated.

KICK REPEAT

Syntax: /msg BotServ KICK #channel REPEAT {ON|OFF} [ttb [num]]

Sets the repeat kicker on or off. When enabled, this
option tells the bot to kick users who are repeating
themselves num times (if num is not given, it
defaults to 3).

ttb is the number of times an user can be kicked
before it get banned. Don\\'t give ttb to disable
the ban system once activated.

KICK BADWORDS

Syntax: /msg BotServ KICK #channel BADWORDS {ON|OFF} [ttb]

Sets the bad words kicker on or off. When enabled, this
option tells the bot to kick users who say certain words
on the channels.

You can define bad words for your channel using the
BADWORDS command. Type /msg BotServ HELP BADWORDS for
more information.

ttb is the number of times an user can be kicked
before it get banned. Don\\'t give ttb to disable
the ban system once activated.

BADWORDS

Syntax: /msg BotServ BADWORDS channel ADD word [SINGLE | START | END]
BADWORDS channel DEL {word | entry-num | list}
BADWORDS channel LIST [mask | list]
BADWORDS channel CLEAR

Maintains the bad words list for a channel. The bad
words list determines which words are to be kicked
when the bad words kicker is enabled. For more information,
type /msg BotServ HELP KICK BADWORDS.

The BADWORDS ADD command adds the given word to the
badword list. If SINGLE is specified, a kick will be
done only if an user says the entire word. If START is
specified, a kick will be done if an user says a word
that starts with word. If END is specified, a kick
will be done if an user says a word that ends with
word. If you don\\'t specify anything, a kick will
be issued every time word is said by an user.

The BADWORDS DEL command removes the given word from the
bad words list. If a list of entry numbers is given, those
entries are deleted. (See the example for LIST below.)

The BADWORDS LIST command displays the bad words list. If
a wildcard mask is given, only those entries matching the
mask are displayed. If a list of entry numbers is given,
only those entries are shown; for example:

BADWORDS #channel LIST 2-5,7-9
Lists bad words entries numbered 2 through 5 and
7 through 9.

The BADWORDS CLEAR command clears all entries of the
bad words list.

SAY

Syntax: /msg BotServ SAY channel text

Makes the bot say the given text on the given channel.

ACT

Syntax: /msg BotServ ACT channel text

Makes the bot do the equivalent of a \\" /me \\" command
on the given channel using the given text.

SERVADMIN HELP

The following command is available to Services admins:

BOT Maintains network bot list

SERVADMIN BOT

Syntax: /msg BotServ BOT ADD nick user host real
BOT CHANGE oldnick newnick [user [host [real]]]
BOT DEL nick
BOT LIST

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, hostname
or realname of a bot without actually delete it (and all
the data associated with it).
BOT DEL removes the given bot from the bot list.
BOT LIST is an alias of BOTLIST and just lists all
bots available on the network.

Note: if you create a bot that has a nick that is
registered, it will be dropped. Also, if an user is
currently using the nick, it will be killed.

SERVADMIN SET

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

SERVADMIN SET NOBOT

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 unassigned
automatically when you enable the option.

Limited to Services admins.

SERVADMIN SET PRIVATE

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.

Fórum WebTuga

News:

[IRC]/NickServ /ChanServ /OperServ /MemoServ /HostSer /Bot..

PT-NGS-

PT-NGS-

PT-NGS-

PT-NGS-

PT-NGS-

PT-NGS-