Warning: Missing argument 2 for plgSystemSourcererHelper::replaceInArticles(), called in /usr/home/freekie/domains/lunagalaxy.net/public_html/plugins/system/sourcerer/helper.php on line 166 and defined in /usr/home/freekie/domains/lunagalaxy.net/public_html/plugins/system/sourcerer/helper.php on line 109
Warning: Missing argument 2 for plgSystemSourcererHelper::replaceInArticles(), called in /usr/home/freekie/domains/lunagalaxy.net/public_html/plugins/system/sourcerer/helper.php on line 166 and defined in /usr/home/freekie/domains/lunagalaxy.net/public_html/plugins/system/sourcerer/helper.php on line 109 CommandsLunaGalaxy Your stepping stone to a great chathttp://www.lunagalaxy.net/cmds.feed2010-09-09T23:36:44ZJoomla! 1.5 - Open Source Content ManagementAstroServ (NickServ)2010-01-18T23:53:28Z2010-01-18T23:53:28Zhttp://www.lunagalaxy.net/cmds/as.htmlCoreyCorey@lunagalaxy.net<h1>AstroServ Commands</h1>
<h2>To Send most of these commands you can actually leave out the /msg AstroServ and simply type /as command here.</h2>
<h3>At LunaGalaxy we use AstroServ in place of NickServ.  If you are used to typing /ns instead of /as the commands will work the same.</h3>
<ul>
<li>
<pre><b>Help AstroServ</b> 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 <b>/msg AstroServ <u>command</u></b>.
For more information on a specific command, type
<b>/msg AstroServ HELP <u>command</u></b>.
</pre>
</li>
<li>
<h3><b>REGISTER</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>REGISTER <u>password</u> <u>[email]</u></b>
Registers your nickname in the AstroServ database. Once
your nick is registered, you can use the <b>SET</b> and <b>ACCESS</b>
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 <b>case matters!</b> <u>ANOPE</u>, <u>Anope</u>, and
<u>anope</u> 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, AstroServ 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 <u>email</u> 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 <b>/msg AstroServ HELP GROUP</b>.
</pre>
</li>
<li>
<h3><b>GROUP</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>GROUP <u>target</u> <u>password</u></b>
This command makes your nickname join the <u>target</u> nickname's
group. <u>password</u> is the password of the target nickname.
Joining a group will allow you to share your configuration,
memos, and channel privileges 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
<u>/msg AstroServ HELP IDENTIFY</u> 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.
<u>Note</u>: all the nicknames of a group have the same password.
</pre>
</li>
<li>
<h3><b>IDENTIFY</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>IDENTIFY <u>password</u></b>
Tells AstroServ 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 <b>REGISTER</b>
command.
</pre>
</li>
<li>
<h3><b>LOGOUT</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>LOGOUT</b>
This reverses the effect of the <b>IDENTIFY</b> 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.
</pre>
</li>
<li>
<h3><b>DROP</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>DROP [<u>nickname</u>]</b>
Drops your nickname from the AstroServ 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 <b>nick</b> parameter.
In order to use this command, you must first identify
with your password (<b>/msg AstroServ HELP IDENTIFY</b> for more
information).
</pre>
</li>
<li>
<h3><b>ACCESS</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>ACCESS ADD <u>mask</u></b>
<b>ACCESS DEL <u>mask</u></b>
<b>ACCESS LIST</b>
Modifies or displays the access list for your nick. This
is the list of addresses which will be automatically
recognized by AstroServ as allowed to use the nick. If
you want to use the nick from a different address, you
need to send an <b>IDENTIFY</b> command to make AstroServ
recognize you.
Examples:
<b>ACCESS ADD anyone@*.bepeg.com</b>
Allows access to user <b>anyone</b> from any machine in
the <b>bepeg.com</b> domain.
<b>ACCESS DEL anyone@*.bepeg.com</b>
Reverses the previous command.
<b>ACCESS LIST</b>
Displays the current access list.
</pre>
</li>
<li>
<h3><b>SET</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET <u>option</u> <u>parameters</u></b>
Sets various nickname options. <u>option</u> 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
<b>/msg AstroServ LIST</b>
HIDE Hide certain pieces of nickname information
MSG Change the communication method of Services
AUTOOP Should services op you automatically.
In order to use this command, you must first identify
with your password (<b>/msg AstroServ HELP IDENTIFY</b> for more
information).
Type <b>/msg AstroServ HELP SET <u>option</u></b> for more information
on a specific option.
</pre>
</li>
<li>
<h3><b>SET DISPLAY</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET DISPLAY <u>new-display</u></b>
Changes the display used to refer to your nickname group in
Services. The new display MUST be a nick of your group.
</pre>
</li>
<li>
<h3><b>SET PASSWORD</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET PASSWORD <u>new-password</u></b>
Changes the password used to identify you as the nick's
owner.
</pre>
</li>
<li>
<h3><b>SET LANGUAGE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET LANGUAGE <u>number</u></b>
Changes the language Services uses when sending messages to
you (for example, when responding to a command you send).
<u>number</u> should be chosen from the following list of
supported languages:
</pre>
</li>
<li>
<h3><b>SET URL</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET URL <u>url</u></b>
Associates the given URL with your nickname. This URL
will be displayed whenever someone requests information
on your nick with the <b>INFO</b> command.
</pre>
</li>
<li>
<h3><b>SET EMAIL</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET EMAIL <u>address</u></b>
Associates the given E-mail address with your nickname.
This address will be displayed whenever someone requests
information on the nickname with the <b>INFO</b> command.
</pre>
</li>
<li>
<h3><b>SET HIDE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET HIDE {EMAIL | STATUS | USERMASK | QUIT} {ON | OFF}</b>
Allows you to prevent certain pieces of information from
being displayed when someone does a AstroServ <b>INFO</b> on your
nick. You can hide your E-mail address (<b>EMAIL</b>), last seen
user@host mask (<b>USERMASK</b>), your services access status
(<b>STATUS</b>) and last quit message (<b>QUIT</b>).
The second parameter specifies whether the information should
be displayed (<b>OFF</b>) or hidden (<b>ON</b>).
</pre>
</li>
<li>
<h3><b>SET ICQ</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET ICQ <u>number</u></b>
Associates the given ICQ number with your nickname. This
number will be displayed whenever someone requests
information on your nick with the <b>INFO</b> command.
</pre>
</li>
<li>
<h3><b>SET GREET</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET GREET <u>message</u></b>
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.
</pre>
</li>
<li>
<h3><b>SET KILL</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET KILL {ON | QUICK | IMMED | OFF}</b>
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 AstroServ will forcibly change
their nick.
If you select <b>QUICK</b>, the user will be given only 20 seconds
to change nicks instead of the usual 60. If you select
<b>IMMED</b>, user's nick will be changed immediately <u>without</u> 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.
</pre>
</li>
<li>
<h3><b>SET SECURE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET SECURE {ON | OFF}</b>
Turns AstroServ's security features on or off for your
nick. With <b>SECURE</b> 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, AstroServ
will not auto-kill you regardless of the setting of the
<b>KILL</b> option.
</pre>
</li>
<li>
<h3><b>SET PRIVATE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET PRIVATE {ON | OFF}</b>
Turns AstroServ's privacy option on or off for your nick.
With <b>PRIVATE</b> set, your nickname will not appear in
nickname lists generated with AstroServ's <b>LIST</b> command.
(However, anyone who knows your nickname can still get
information on it using the <b>INFO</b> command.)
</pre>
</li>
<li>
<h3><b>UPDATE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ UPDATE
Updates your current status, i.e. it checks for new memos,
sets needed chanmodes (ModeonID) and updates your vhost and
your userflags (lastseentime, etc).
</pre>
</li>
<li>
<h3><b>SET HIDE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET HIDE {EMAIL | STATUS | USERMASK | QUIT} {ON | OFF}</b>
Allows you to prevent certain pieces of information from
being displayed when someone does a AstroServ <b>INFO</b> on your
nick. You can hide your E-mail address (<b>EMAIL</b>), last seen
user@host mask (<b>USERMASK</b>), your services access status
(<b>STATUS</b>) and last quit message (<b>QUIT</b>).
The second parameter specifies whether the information should
be displayed (<b>OFF</b>) or hidden (<b>ON</b>).
</pre>
</li>
<li>
<h3><b>SET MSG</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET MSG {ON | OFF}</b>
Allows you to choose the way Services are communicating with
you. With <b>MSG</b> set, Services will use messages, else they'll
use notices.
</pre>
</li>
<li>
<h3><b>RECOVER</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>RECOVER <u>nickname</u> [<u>password</u>]</b>
Allows you to recover your nickname if someone else has
taken it; this does the same thing that AstroServ does
automatically if someone tries to use a kill-protected
nick.
When you give this command, AstroServ 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
remain online for AstroServ to ensure that the other
user does not immediately reconnect; after that time, you
can reclaim your nick. Alternatively, use the <b>RELEASE</b>
command (<b>/msg AstroServ HELP RELEASE</b>) to get the nick
back sooner.
In order to use the <b>RECOVER</b> 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.
</pre>
</li>
<li>
<h3><b>RELEASE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>RELEASE <u>nickname</u> [<u>password</u>]</b>
Instructs AstroServ to remove any hold on your nickname
caused by automatic kill protection or use of the <b>RECOVER</b>
command. This holds lasts for AstroServ;
this command gets rid of them sooner.
In order to use the <b>RELEASE</b> 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.
</pre>
</li>
<li>
<h3><b>GHOST</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>GHOST <u>nickname</u> [<u>password</u>]</b>
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 <b>GHOST</b> 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.
</pre>
</li>
<li>
<h3><b>INFO</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>INFO <u>nickname</u> [ALL]</b>
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 <b>ALL</b> is specified, you will
be shown all the information; regardless of whether
it's hidden or not.
</pre>
</li>
<li>
<h3><b>LIST</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>LIST <u>pattern</u></b>
Lists all registered nicknames which match the given
pattern, in <u>nick!user@host</u> format. Nicks with the
<b>PRIVATE</b> option set will not be displayed.
Examples:
<b>LIST *!joeuser@foo.com</b>
Lists all nicks owned by joeuser@foo.com.
<b>LIST *Bot*!*@*</b>
Lists all registered nicks with <b>Bot</b> in their
names (case insensitive).
<b>LIST *!*@*.bar.org</b>
Lists all nicks owned by users in the <b>bar.org</b>
domain.
</pre>
</li>
<li>
<h3><b>ALIST</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>ALIST [<u>level</u>]</b>
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:
<b>ALIST Founder</b>
Lists all channels where you have Founder
access.
<b>ALIST AOP</b>
Lists all channels where you have AOP
access or greater.
<b>ALIST 10</b>
Lists all channels where you have level 10
access or greater.
Channels that have the <u>NOEXPIRE</u> option set will be
prefixed by an exclamation mark.
</pre>
</li>
<li>
<h3><b>GLIST</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>GLIST</b>
Lists all nicks in your group.
</pre>
</li>
<li>
<h3><b>STATUS</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>STATUS <u>nickname</u>...</b>
Returns whether the user using the given nickname is
recognized as the owner of the nickname. The response has
this format:
<u>nickname</u> <u>status-code</u>
where <u>nickname</u> is the nickname sent with the command, and
<u>status-code</u> is one of the following:
0 - no such user online <b>or</b> 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. If no nickname is given, your status
will be returned.
</pre>
</li>
<li>
<h3><b>EXPIRES</b></h3>
<pre>
Nicknames that are not used anymore are subject to
the automatic expiration, i.e. they will be deleted
after <num> days if not used.
<br type="_moz" /></pre>
</li>
<li>
<h3><b>SERVADMIN LOGOUT</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>LOGOUT [<u>nickname</u> [REVALIDATE]]</b>
Without a parameter, reverses the effect of the <b>IDENTIFY</b>
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 <b>Services admins</b>.
</pre>
</li>
</ul>
<h3> </h3>
<h3> </h3>
<p> </p><h1>AstroServ Commands</h1>
<h2>To Send most of these commands you can actually leave out the /msg AstroServ and simply type /as command here.</h2>
<h3>At LunaGalaxy we use AstroServ in place of NickServ.  If you are used to typing /ns instead of /as the commands will work the same.</h3>
<ul>
<li>
<pre><b>Help AstroServ</b> 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 <b>/msg AstroServ <u>command</u></b>.
For more information on a specific command, type
<b>/msg AstroServ HELP <u>command</u></b>.
</pre>
</li>
<li>
<h3><b>REGISTER</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>REGISTER <u>password</u> <u>[email]</u></b>
Registers your nickname in the AstroServ database. Once
your nick is registered, you can use the <b>SET</b> and <b>ACCESS</b>
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 <b>case matters!</b> <u>ANOPE</u>, <u>Anope</u>, and
<u>anope</u> 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, AstroServ 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 <u>email</u> 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 <b>/msg AstroServ HELP GROUP</b>.
</pre>
</li>
<li>
<h3><b>GROUP</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>GROUP <u>target</u> <u>password</u></b>
This command makes your nickname join the <u>target</u> nickname's
group. <u>password</u> is the password of the target nickname.
Joining a group will allow you to share your configuration,
memos, and channel privileges 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
<u>/msg AstroServ HELP IDENTIFY</u> 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.
<u>Note</u>: all the nicknames of a group have the same password.
</pre>
</li>
<li>
<h3><b>IDENTIFY</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>IDENTIFY <u>password</u></b>
Tells AstroServ 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 <b>REGISTER</b>
command.
</pre>
</li>
<li>
<h3><b>LOGOUT</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>LOGOUT</b>
This reverses the effect of the <b>IDENTIFY</b> 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.
</pre>
</li>
<li>
<h3><b>DROP</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>DROP [<u>nickname</u>]</b>
Drops your nickname from the AstroServ 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 <b>nick</b> parameter.
In order to use this command, you must first identify
with your password (<b>/msg AstroServ HELP IDENTIFY</b> for more
information).
</pre>
</li>
<li>
<h3><b>ACCESS</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>ACCESS ADD <u>mask</u></b>
<b>ACCESS DEL <u>mask</u></b>
<b>ACCESS LIST</b>
Modifies or displays the access list for your nick. This
is the list of addresses which will be automatically
recognized by AstroServ as allowed to use the nick. If
you want to use the nick from a different address, you
need to send an <b>IDENTIFY</b> command to make AstroServ
recognize you.
Examples:
<b>ACCESS ADD anyone@*.bepeg.com</b>
Allows access to user <b>anyone</b> from any machine in
the <b>bepeg.com</b> domain.
<b>ACCESS DEL anyone@*.bepeg.com</b>
Reverses the previous command.
<b>ACCESS LIST</b>
Displays the current access list.
</pre>
</li>
<li>
<h3><b>SET</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET <u>option</u> <u>parameters</u></b>
Sets various nickname options. <u>option</u> 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
<b>/msg AstroServ LIST</b>
HIDE Hide certain pieces of nickname information
MSG Change the communication method of Services
AUTOOP Should services op you automatically.
In order to use this command, you must first identify
with your password (<b>/msg AstroServ HELP IDENTIFY</b> for more
information).
Type <b>/msg AstroServ HELP SET <u>option</u></b> for more information
on a specific option.
</pre>
</li>
<li>
<h3><b>SET DISPLAY</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET DISPLAY <u>new-display</u></b>
Changes the display used to refer to your nickname group in
Services. The new display MUST be a nick of your group.
</pre>
</li>
<li>
<h3><b>SET PASSWORD</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET PASSWORD <u>new-password</u></b>
Changes the password used to identify you as the nick's
owner.
</pre>
</li>
<li>
<h3><b>SET LANGUAGE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET LANGUAGE <u>number</u></b>
Changes the language Services uses when sending messages to
you (for example, when responding to a command you send).
<u>number</u> should be chosen from the following list of
supported languages:
</pre>
</li>
<li>
<h3><b>SET URL</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET URL <u>url</u></b>
Associates the given URL with your nickname. This URL
will be displayed whenever someone requests information
on your nick with the <b>INFO</b> command.
</pre>
</li>
<li>
<h3><b>SET EMAIL</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET EMAIL <u>address</u></b>
Associates the given E-mail address with your nickname.
This address will be displayed whenever someone requests
information on the nickname with the <b>INFO</b> command.
</pre>
</li>
<li>
<h3><b>SET HIDE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET HIDE {EMAIL | STATUS | USERMASK | QUIT} {ON | OFF}</b>
Allows you to prevent certain pieces of information from
being displayed when someone does a AstroServ <b>INFO</b> on your
nick. You can hide your E-mail address (<b>EMAIL</b>), last seen
user@host mask (<b>USERMASK</b>), your services access status
(<b>STATUS</b>) and last quit message (<b>QUIT</b>).
The second parameter specifies whether the information should
be displayed (<b>OFF</b>) or hidden (<b>ON</b>).
</pre>
</li>
<li>
<h3><b>SET ICQ</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET ICQ <u>number</u></b>
Associates the given ICQ number with your nickname. This
number will be displayed whenever someone requests
information on your nick with the <b>INFO</b> command.
</pre>
</li>
<li>
<h3><b>SET GREET</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET GREET <u>message</u></b>
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.
</pre>
</li>
<li>
<h3><b>SET KILL</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET KILL {ON | QUICK | IMMED | OFF}</b>
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 AstroServ will forcibly change
their nick.
If you select <b>QUICK</b>, the user will be given only 20 seconds
to change nicks instead of the usual 60. If you select
<b>IMMED</b>, user's nick will be changed immediately <u>without</u> 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.
</pre>
</li>
<li>
<h3><b>SET SECURE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET SECURE {ON | OFF}</b>
Turns AstroServ's security features on or off for your
nick. With <b>SECURE</b> 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, AstroServ
will not auto-kill you regardless of the setting of the
<b>KILL</b> option.
</pre>
</li>
<li>
<h3><b>SET PRIVATE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET PRIVATE {ON | OFF}</b>
Turns AstroServ's privacy option on or off for your nick.
With <b>PRIVATE</b> set, your nickname will not appear in
nickname lists generated with AstroServ's <b>LIST</b> command.
(However, anyone who knows your nickname can still get
information on it using the <b>INFO</b> command.)
</pre>
</li>
<li>
<h3><b>UPDATE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ UPDATE
Updates your current status, i.e. it checks for new memos,
sets needed chanmodes (ModeonID) and updates your vhost and
your userflags (lastseentime, etc).
</pre>
</li>
<li>
<h3><b>SET HIDE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET HIDE {EMAIL | STATUS | USERMASK | QUIT} {ON | OFF}</b>
Allows you to prevent certain pieces of information from
being displayed when someone does a AstroServ <b>INFO</b> on your
nick. You can hide your E-mail address (<b>EMAIL</b>), last seen
user@host mask (<b>USERMASK</b>), your services access status
(<b>STATUS</b>) and last quit message (<b>QUIT</b>).
The second parameter specifies whether the information should
be displayed (<b>OFF</b>) or hidden (<b>ON</b>).
</pre>
</li>
<li>
<h3><b>SET MSG</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>SET MSG {ON | OFF}</b>
Allows you to choose the way Services are communicating with
you. With <b>MSG</b> set, Services will use messages, else they'll
use notices.
</pre>
</li>
<li>
<h3><b>RECOVER</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>RECOVER <u>nickname</u> [<u>password</u>]</b>
Allows you to recover your nickname if someone else has
taken it; this does the same thing that AstroServ does
automatically if someone tries to use a kill-protected
nick.
When you give this command, AstroServ 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
remain online for AstroServ to ensure that the other
user does not immediately reconnect; after that time, you
can reclaim your nick. Alternatively, use the <b>RELEASE</b>
command (<b>/msg AstroServ HELP RELEASE</b>) to get the nick
back sooner.
In order to use the <b>RECOVER</b> 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.
</pre>
</li>
<li>
<h3><b>RELEASE</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>RELEASE <u>nickname</u> [<u>password</u>]</b>
Instructs AstroServ to remove any hold on your nickname
caused by automatic kill protection or use of the <b>RECOVER</b>
command. This holds lasts for AstroServ;
this command gets rid of them sooner.
In order to use the <b>RELEASE</b> 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.
</pre>
</li>
<li>
<h3><b>GHOST</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>GHOST <u>nickname</u> [<u>password</u>]</b>
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 <b>GHOST</b> 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.
</pre>
</li>
<li>
<h3><b>INFO</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>INFO <u>nickname</u> [ALL]</b>
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 <b>ALL</b> is specified, you will
be shown all the information; regardless of whether
it's hidden or not.
</pre>
</li>
<li>
<h3><b>LIST</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>LIST <u>pattern</u></b>
Lists all registered nicknames which match the given
pattern, in <u>nick!user@host</u> format. Nicks with the
<b>PRIVATE</b> option set will not be displayed.
Examples:
<b>LIST *!joeuser@foo.com</b>
Lists all nicks owned by joeuser@foo.com.
<b>LIST *Bot*!*@*</b>
Lists all registered nicks with <b>Bot</b> in their
names (case insensitive).
<b>LIST *!*@*.bar.org</b>
Lists all nicks owned by users in the <b>bar.org</b>
domain.
</pre>
</li>
<li>
<h3><b>ALIST</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>ALIST [<u>level</u>]</b>
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:
<b>ALIST Founder</b>
Lists all channels where you have Founder
access.
<b>ALIST AOP</b>
Lists all channels where you have AOP
access or greater.
<b>ALIST 10</b>
Lists all channels where you have level 10
access or greater.
Channels that have the <u>NOEXPIRE</u> option set will be
prefixed by an exclamation mark.
</pre>
</li>
<li>
<h3><b>GLIST</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>GLIST</b>
Lists all nicks in your group.
</pre>
</li>
<li>
<h3><b>STATUS</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>STATUS <u>nickname</u>...</b>
Returns whether the user using the given nickname is
recognized as the owner of the nickname. The response has
this format:
<u>nickname</u> <u>status-code</u>
where <u>nickname</u> is the nickname sent with the command, and
<u>status-code</u> is one of the following:
0 - no such user online <b>or</b> 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. If no nickname is given, your status
will be returned.
</pre>
</li>
<li>
<h3><b>EXPIRES</b></h3>
<pre>
Nicknames that are not used anymore are subject to
the automatic expiration, i.e. they will be deleted
after <num> days if not used.
<br type="_moz" /></pre>
</li>
<li>
<h3><b>SERVADMIN LOGOUT</b></h3>
<pre><i>Syntax:</i> /msg AstroServ <b>LOGOUT [<u>nickname</u> [REVALIDATE]]</b>
Without a parameter, reverses the effect of the <b>IDENTIFY</b>
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 <b>Services admins</b>.
</pre>
</li>
</ul>
<h3> </h3>
<h3> </h3>
<p> </p>GalaxyServ (ChanServ)2010-01-19T00:09:45Z2010-01-19T00:09:45Zhttp://www.lunagalaxy.net/cmds/gs.htmlCoreyCorey@lunagalaxy.net<h1>GalaxyServ Commands</h1>
<h2>For most clients you can shorten /msg GalaxyServ for /gs command.</h2>
<h2>We do use GalaxyServ in place of ChanServ, if you are used to using /cs the commands will work the same way if you type /cs command.</h2>
<div> </div>
<ul>
<li>
<h3><b>HELP</b></h3>
<pre><b>GalaxyServ</b> allows you to register and control various
aspects of channels. GalaxyServ can often prevent
malicious users from "taking over" channels by limiting
who is allowed channel operator privileges. Available
commands are listed below; to use them, type
<b>/msg GalaxyServ <u>command</u></b>. For more information on a
specific command, type <b>/msg GalaxyServ HELP <u>command</u></b>.
</pre>
</li>
<li>
<h3><b>EXPIRES</b></h3>
<pre>
Note that any channel which is not used for <num> days
(i.e. which no user on the channel's access list enters
for that period of time) will be automatically dropped.
</pre>
</li>
<li>
<h3><b>REGISTER</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>REGISTER <u>channel</u> <u>password</u> <u>description</u></b>
Registers a channel in the GalaxyServ database. In order
to use this command, you must first be a channel operator
on the channel you're trying to register. The password
is used with the <b>IDENTIFY</b> command to allow others to
make changes to the channel settings at a later time.
The last parameter, which <b>must</b> be included, is a
general description of the channel's purpose.
When you register a channel, you are recorded as the
"founder" of the channel. The channel founder is allowed
to change all of the channel settings for the channel;
GalaxyServ will also automatically give the founder
channel-operator privileges when s/he enters the channel.
See the <b>ACCESS</b> command (<b>/msg GalaxyServ HELP ACCESS</b>) for
information on giving a subset of these privileges to
other channel users.
NOTICE: In order to register a channel, you must have
first registered your nickname. If you haven't,
<b>/msg GalaxyServ HELP</b> for information on how to do so.
</pre>
</li>
<li>
<h3><b>IDENTIFY</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>IDENTIFY <u>channel</u> <u>password</u></b>
Authenticates you to GalaxyServ as the founder of the given
channel. Many commands require you to use this command
before using them. The password should be the same one
you sent with the <b>REGISTER</b> command.
</pre>
</li>
<li>
<h3><b>LOGOUT</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>LOGOUT <u>channel</u> <u>nickname</u></b>
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.
</pre>
</li>
<li>
<h3><b>DROP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DROP <u>channel</u></b>
Unregisters the named channel. Can only be used by
<b>channel founder</b>, who must use the <b>IDENTIFY</b> command first.
</pre>
</li>
<li>
<h3><b>SET</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> <u>option</u> <u>parameters</u></b>
Allows the channel founder to set various channel options
and other information.
Available options:
FOUNDER Set the founder of a channel
SUCCESSOR Set the successor for a channel
PASSWORD Set the founder password
DESC Set the channel description
URL Associate a URL with the channel
EMAIL Associate an E-mail address with the channel
ENTRYMSG Set a message to be sent to users when they
enter the channel
BANTYPE Set how Services make bans on the channel
MLOCK Lock channel modes on or off
KEEPTOPIC Retain topic when channel is not in use
OPNOTICE Send a notice when OP/DEOP commands are used
PEACE Regulate the use of critical commands
PRIVATE Hide channel from LIST command
RESTRICTED Restrict access to the channel
SECURE Activate GalaxyServ security features
SECUREOPS Stricter control of chanop status
SECUREFOUNDER Stricter control of channel founder status
SIGNKICK Sign kicks that are done with KICK command
TOPICLOCK Topic can only be changed with TOPIC
XOP Toggle the user privilege system
Type <b>/msg GalaxyServ HELP SET <u>option</u></b> for more information on a
particular option.
</pre>
</li>
<li>
<h3><b>SET FOUNDER</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> FOUNDER <u>nick</u></b>
Changes the founder of a channel. The new nickname must
be a registered one.
</pre>
</li>
<li>
<h3><b>SET SUCCESSOR</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> SUCCESSOR <u>nick</u></b>
Changes the successor of a channel. If the founder's
nickname expires or is dropped while the channel is still
registered, the successor will become the new founder of the
channel. However, if the successor already has too many
channels registered (<num>), the channel will be dropped
instead, just as if no successor had been set. The new
nickname must be a registered one.
</pre>
</li>
<li>
<h3><b>SET PASSWORD</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> PASSWORD <u>password</u></b>
Sets the password used to identify as the founder of the
channel.
</pre>
</li>
<li>
<h3><b>SET DESC</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> DESC <u>description</u></b>
Sets the description for the channel, which shows up with
the <b>LIST</b> and <b>INFO</b> commands.
</pre>
</li>
<li>
<h3><b>SET URL</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> URL [<u>url</u>]</b>
Associates the given URL with the channel. This URL will
be displayed whenever someone requests information on the
channel with the <b>INFO</b> command. If no parameter is given,
deletes any current URL for the channel.
</pre>
</li>
<li>
<h3><b>SET EMAIL</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> EMAIL [<u>address</u>]</b>
Associates the given E-mail address with the channel.
This address will be displayed whenever someone requests
information on the channel with the <b>INFO</b> command. If no
parameter is given, deletes any current E-mail address for
the channel.
</pre>
</li>
<li>
<h3><b>SET ENTRYMSG</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> ENTRYMSG [<u>message</u>]</b>
Sets the message which will be sent via /notice to users
when they enter the channel. If no parameter is given,
causes no message to be sent upon entering the channel.
</pre>
</li>
<li>
<h3><b>SET BANTYPE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> BANTYPE <u>bantype</u></b>
Sets the ban type that will be used by services whenever
they need to ban someone from your channel.
bantype is a number between 0 and 3 that means:
0: ban in the form *!user@host
1: ban in the form *!*user@host
2: ban in the form *!*@host
3: ban in the form *!*user@*.domain
</pre>
</li>
<li>
<h3><b>SET KEEPTOPIC</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> KEEPTOPIC {ON | OFF}</b>
Enables or disables the <b>topic retention</b> option for a
channel. When <b>topic retention</b> is set, the topic for the
channel will be remembered by GalaxyServ even after the
last user leaves the channel, and will be restored the
next time the channel is created.
</pre>
</li>
<li>
<h3><b>SET TOPICLOCK</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> TOPICLOCK {ON | OFF}</b>
Enables or disables the <b>topic lock</b> option for a channel.
When <b>topic lock</b> is set, GalaxyServ will not allow the
channel topic to be changed except via the <b>TOPIC</b>
command.
</pre>
</li>
<li>
<h3><b>SET MLOCK</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> MLOCK <u>modes</u></b>
Sets the mode-lock parameter for the channel. GalaxyServ
allows you to define certain channel modes to be always
on, off or free to be either on or off.
The <u>modes</u> parameter is constructed exactly the same way
as a <b>/MODE</b> command; that is, modes followed by a + are
locked on, and modes followed by a - are locked off. Note,
however, that unlike the <b>/MODE</b> command, each use of
<b>SET MLOCK</b> will remove all modes previously locked before
setting the new!
<b>Warning:</b> If you set a mode-locked key, as in the second
example below, you should also set the <b>RESTRICTED</b> option for
the channel (see <b>HELP SET RESTRICTED</b>), or anyone entering
the channel when it is empty will be able to see the key!
Examples:
<b>SET #channel MLOCK +nt-iklps</b>
Forces modes n and t on, and modes i, k, l, p, and
s off. Mode m is left free to be either on or off.
<b>SET #channel MLOCK +knst-ilmp my-key</b>
Forces modes k, n, s, and t on, and modes i, l, m,
and p off. Also forces the channel key to be
"my-key".
<b>SET #channel MLOCK +</b>
Removes the mode lock; all channel modes are free
to be either on or off.
</pre>
</li>
<li>
<h3><b>SET PEACE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> PEACE {ON | OFF}</b>
Enables or disables the <b>peace</b> option for a channel.
When <b>peace</b> is set, an user won't be able to kick,
ban or remove a channel status of an user that has
a level superior or equal to his via GalaxyServ commands.
</pre>
</li>
<li>
<h3><b>SET PRIVATE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> PRIVATE {ON | OFF}</b>
Enables or disables the <b>private</b> option for a channel.
When <b>private</b> is set, a <b>/msg GalaxyServ LIST</b> will not
include the channel in any lists.
</pre>
</li>
<li>
<h3><b>SET RESTRICTED</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> RESTRICTED {ON | OFF}</b>
Enables or disables the <b>restricted access</b> option for a
channel. When <b>restricted access</b> is set, users not on
the access list will instead be kicked and banned from the channel.
</pre>
</li>
<li>
<h3><b>SET SECURE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> SECURE {ON | OFF}</b>
Enables or disables GalaxyServ's security features for a
channel. When <b>SECURE</b> is set, only users who have
registered their nicknames with GalaxyServ and IDENTIFY'd
with their password will be given access to the channel
as controlled by the access list.
</pre>
</li>
<li>
<h3><b>SET SECUREOPS</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> SECUREOPS {ON | OFF}</b>
Enables or disables the <b>secure ops</b> option for a channel.
When <b>secure ops</b> is set, users who are not on the userlist
will not be allowed chanop status.
</pre>
</li>
<li>
<h3><b>SET SECUREFOUNDER</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> SECUREFOUNDER {ON | OFF}</b>
Enables or disables the <b>secure founder</b> option for a channel.
When <b>secure founder</b> is set, only the real founder will be
able to drop the channel, change its password, its founder and its
successor, and not those who are IDENTIFY'd with GalaxyServ.
</pre>
</li>
<li>
<h3><b>SET SIGNKICK</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> SIGNKICK {ON | LEVEL | OFF}</b>
Enables or disables signed kicks for a
channel. When <b>SIGNKICK</b> is set, kicks issued with
GalaxyServ KICK command will have the nick that used the
command in their reason.
If you use <b>LEVEL</b>, those who have a level that is superior
or equal to the SIGNKICK level on the channel won't have their
kicks signed. See <b>/msg GalaxyServ HELP LEVELS</b> for more information.
</pre>
</li>
<li>
<h3><b>SET XOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> XOP {ON | OFF}</b>
Enables or disables the xOP lists system for a channel.
When <b>XOP</b> is set, you have to use the <b>AOP</b>/<b>SOP</b>/<b>VOP</b>
commands in order to give channel privileges to
users, else you have to use the <b>ACCESS</b> command.
<b>Technical Note</b>: when you switch from access list to xOP
lists system, your level definitions and user levels will be
changed, so you won't find the same values if you
switch back to access system!
You should also check that your users are in the good xOP
list after the switch from access to xOP lists, because the
guess is not always perfect... in fact, it is not recommended
to use the xOP lists if you changed level definitions with
the <b>LEVELS</b> command.
Switching from xOP lists system to access list system
causes no problem though.
</pre>
</li>
<li>
<h3><b>SET OPNOTICE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> OPNOTICE {ON | OFF}</b>
Enables or disables the <b>op-notice</b> option for a channel.
When <b>op-notice</b> is set, GalaxyServ will send a notice to the
channel whenever the <b>OP</b> or <b>DEOP</b> commands are used for a user
in the channel.
</pre>
</li>
<li>
<h3><b>AOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>AOP <u>channel</u> ADD <u>nick</u></b>
<b>AOP <u>channel</u> DEL {<u>nick</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>AOP <u>channel</u> LIST [<u>mask</u> | <u>list</u>]</b>
<b>AOP <u>channel</u> CLEAR</b>
Maintains the <b>AOP</b> (AutoOP) <b>list</b> for a channel. The AOP
list gives users the right to be auto-opped on your channel,
to unban or invite themselves if needed, to have their
greet message showed on join, and so on.
The <b>AOP ADD</b> command adds the given nickname to the
AOP list.
The <b>AOP DEL</b> command removes the given nick from the
AOP list. If a list of entry numbers is given, those
entries are deleted. (See the example for LIST below.)
The <b>AOP LIST</b> command displays the AOP 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:
<b>AOP #channel LIST 2-5,7-9</b>
Lists AOP entries numbered 2 through 5 and
7 through 9.
The <b>AOP CLEAR</b> command clears all entries of the
AOP list.
The <b>AOP ADD</b> and <b>AOP DEL</b> commands are limited to
SOPs or above, while the <b>AOP CLEAR</b> command can only
be used by the channel founder. However, any user on the
AOP list may use the <b>AOP LIST</b> command.
This command may have been disabled for your channel, and
in that case you need to use the access list. See
<b>/msg GalaxyServ HELP ACCESS</b> for information about the access list,
and <b>/msg GalaxyServ HELP SET XOP</b> to know how to toggle between
the access list and xOP list systems.
</pre>
</li>
<li>
<h3><b>HOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>HOP <u>channel</u> ADD <u>nick</u></b>
<b>HOP <u>channel</u> DEL {<u>nick</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>HOP <u>channel</u> LIST [<u>mask</u> | <u>list</u>]</b>
<b>HOP <u>channel</u> CLEAR</b>
Maintains the <b>HOP</b> (HalfOP) <b>list</b> for a channel. The HOP
list gives users the right to be auto-halfopped on your
channel.
The <b>HOP ADD</b> command adds the given nickname to the
HOP list.
The <b>HOP DEL</b> command removes the given nick from the
HOP list. If a list of entry numbers is given, those
entries are deleted. (See the example for LIST below.)
The <b>HOP LIST</b> command displays the HOP 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:
<b>HOP #channel LIST 2-5,7-9</b>
Lists HOP entries numbered 2 through 5 and
7 through 9.
The <b>HOP CLEAR</b> command clears all entries of the
HOP list.
The <b>HOP ADD</b>, <b>HOP DEL</b> and <b>HOP LIST</b> commands are
limited to AOPs or above, while the <b>HOP CLEAR</b> command
can only be used by the channel founder.
This command may have been disabled for your channel, and
in that case you need to use the access list. See
<b>/msg GalaxyServ HELP ACCESS</b> for information about the access list,
and <b>/msg GalaxyServ HELP SET XOP</b> to know how to toggle between
the access list and xOP list systems.
</pre>
</li>
<li>
<h3><b>SOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SOP <u>channel</u> ADD <u>nick</u></b>
<b>SOP <u>channel</u> DEL {<u>nick</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>SOP <u>channel</u> LIST [<u>mask</u> | <u>list</u>]</b>
<b>SOP <u>channel</u> CLEAR</b>
Maintains the <b>SOP</b> (SuperOP) <b>list</b> for a channel. The SOP
list gives users all rights given by the AOP list, and adds
those needed to use the AutoKick and the BadWords lists,
to send and read channel memos, and so on.
The <b>SOP ADD</b> command adds the given nickname to the
SOP list.
The <b>SOP DEL</b> command removes the given nick from the
SOP list. If a list of entry numbers is given, those
entries are deleted. (See the example for LIST below.)
The <b>SOP LIST</b> command displays the SOP 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:
<b>SOP #channel LIST 2-5,7-9</b>
Lists AOP entries numbered 2 through 5 and
7 through 9.
The <b>SOP CLEAR</b> command clears all entries of the
SOP list.
The <b>SOP ADD</b>, <b>SOP DEL</b> and <b>SOP CLEAR</b> commands are
limited to the channel founder. However, any user on the
AOP list may use the <b>SOP LIST</b> command.
This command may have been disabled for your channel, and
in that case you need to use the access list. See
<b>/msg GalaxyServ HELP ACCESS</b> for information about the access list,
and <b>/msg GalaxyServ HELP SET XOP</b> to know how to toggle between
the access list and xOP list systems.
</pre>
</li>
<li>
<h3><b>VOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>VOP <u>channel</u> ADD <u>nick</u></b>
<b>VOP <u>channel</u> DEL {<u>nick</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>VOP <u>channel</u> LIST [<u>mask</u> | <u>list</u>]</b>
<b>VOP <u>channel</u> CLEAR</b>
Maintains the <b>VOP</b> (VOicePeople) <b>list</b> for a channel.
The VOP list allows users to be auto-voiced and to voice
themselves if they aren't.
The <b>VOP ADD</b> command adds the given nickname to the
VOP list.
The <b>VOP DEL</b> command removes the given nick from the
VOP list. If a list of entry numbers is given, those
entries are deleted. (See the example for LIST below.)
The <b>VOP LIST</b> command displays the VOP 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:
<b>VOP #channel LIST 2-5,7-9</b>
Lists VOP entries numbered 2 through 5 and
7 through 9.
The <b>VOP CLEAR</b> command clears all entries of the
VOP list.
The <b>VOP ADD</b>, <b>VOP DEL</b> and <b>VOP LIST</b> commands are
limited to AOPs or above, while the <b>VOP CLEAR</b> command
can only be used by the channel founder.
This command may have been disabled for your channel, and
in that case you need to use the access list. See
<b>/msg GalaxyServ HELP ACCESS</b> for information about the access list,
and <b>/msg GalaxyServ HELP SET XOP</b> to know how to toggle between
the access list and xOP list systems.
</pre>
</li>
<li>
<h3><b>ACCESS</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>ACCESS <u>channel</u> ADD <u>nick</u> <u>level</u></b>
<b>ACCESS <u>channel</u> DEL {<u>nick</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>ACCESS <u>channel</u> LIST [<u>mask</u> | <u>list</u>]</b>
<b>ACCESS <u>channel</u> CLEAR</b>
Maintains the <b>access list</b> for a channel. The access
list specifies which users are allowed chanop status or
access to GalaxyServ commands on the channel. Different
user levels allow for access to different subsets of
privileges; <b>/msg GalaxyServ HELP ACCESS LEVELS</b> for more
specific information. Any nick not on the access list has
a user level of 0.
The <b>ACCESS ADD</b> command adds the given nickname to the
access list with the given user level; if the nick is
already present on the list, its access level is changed to
the level specified in the command. The <u>level</u> specified
must be less than that of the user giving the command, and
if the <u>nick</u> is already on the access list, the current
access level of that nick must be less than the access level
of the user giving the command.
The <b>ACCESS DEL</b> command removes the given nick from the
access list. If a list of entry numbers is given, those
entries are deleted. (See the example for LIST below.)
The <b>ACCESS LIST</b> command displays the access 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:
<b>ACCESS #channel LIST 2-5,7-9</b>
Lists access entries numbered 2 through 5 and
7 through 9.
The <b>ACCESS CLEAR</b> command clears all entries of the
access list.
</pre>
</li>
<li>
<h3><b>ACCESS LEVELS</b></h3>
<pre><b>User access levels</b>
By default, the following access levels are defined:
<b>Founder</b> Full access to GalaxyServ functions; automatic
opping upon entering channel. Note
that only one person may have founder
status (it cannot be given using the
<b>ACCESS</b> command).
<b> 10</b> Access to AKICK command; automatic opping.
<b> 5</b> Automatic opping.
<b> 3</b> Automatic voicing.
<b> 0</b> No special privileges; can be opped by other
ops (unless <b>secure-ops</b> is set).
<b> <0</b> May not be opped.
These levels may be changed, or new ones added, using the
<b>LEVELS</b> command; type <b>/msg GalaxyServ HELP LEVELS</b> for
information.
</pre>
</li>
<li>
<h3><b>AKICK</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>AKICK <u>channel</u> ADD {<u>nick</u> | <u>mask</u>} [<u>reason</u>]</b>
<b>AKICK <u>channel</u> STICK <u>mask</u></b>
<b>AKICK <u>channel</u> UNSTICK <u>mask</u></b>
<b>AKICK <u>channel</u> DEL {<u>nick</u> | <u>mask</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>AKICK <u>channel</u> LIST [<u>mask</u> | <u>entry-num</u> | <u>list</u>]</b>
<b>AKICK <u>channel</u> VIEW [<u>mask</u> | <u>entry-num</u> | <u>list</u>]</b>
<b>AKICK <u>channel</u> ENFORCE</b>
<b>AKICK <u>channel</u> CLEAR</b>
Maintains the <b>AutoKick list</b> for a channel. If a user
on the AutoKick list attempts to join the channel,
GalaxyServ will ban that user from the channel, then kick
the user.
The <b>AKICK ADD</b> command adds the given nick or usermask
to the AutoKick list. If a <u>reason</u> is given with
the command, that reason will be used when the user is
kicked; if not, the default reason is "You have been
banned from the channel".
When akicking a <u>registered nick</u> the nickserv account
will be added to the akick list instead of the mask.
All users within that nickgroup will then be akicked.
The <b>AKICK STICK</b> command permanently bans the given mask
on the channel. If someone tries to remove the ban, GalaxyServ
will automatically set it again. You can't use it for
registered nicks.
The <b>AKICK UNSTICK</b> command cancels the effect of the
<b>AKICK STICK</b> command, so you'll be able to unset the
ban again on the channel.
The <b>AKICK DEL</b> command removes the given nick or mask
from the AutoKick list. It does not, however, remove any
bans placed by an AutoKick; those must be removed
manually.
The <b>AKICK LIST</b> command displays the AutoKick list, or
optionally only those AutoKick entries which match the
given mask.
The <b>AKICK VIEW</b> command is a more verbose version of
<b>AKICK LIST</b> command.
The <b>AKICK ENFORCE</b> command causes GalaxyServ to enforce the
current AKICK list by removing those users who match an
AKICK mask.
The <b>AKICK CLEAR</b> command clears all entries of the
akick list.
</pre>
</li>
<li>
<h3><b>LEVELS</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>LEVELS <u>channel</u> SET <u>type</u> <u>level</u></b>
<b>LEVELS <u>channel</u> {DIS | DISABLE} <u>type</u></b>
<b>LEVELS <u>channel</u> LIST</b>
<b>LEVELS <u>channel</u> RESET</b>
The <b>LEVELS</b> command allows fine control over the meaning of
the numeric access levels used for channels. With this
command, you can define the access level required for most
of GalaxyServ's functions. (The <b>SET FOUNDER</b> and <b>SET PASSWORD</b>
commands, as well as this command, are always restricted to
the channel founder.)
<b>LEVELS SET</b> allows the access level for a function or group of
functions to be changed. <b>LEVELS DISABLE</b> (or <b>DIS</b> for short)
disables an automatic feature or disallows access to a
function by anyone other than the channel founder.
<b>LEVELS LIST</b> shows the current levels for each function or
group of functions. <b>LEVELS RESET</b> resets the levels to the
default levels of a newly-created channel (see
<b>HELP ACCESS LEVELS</b>).
For a list of the features and functions whose levels can be
set, see <b>HELP LEVELS DESC</b>.
</pre>
</li>
<li>
<h3><b>INFO</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>INFO <u>channel</u> [ALL]</b>
Lists information about the named registered channel,
including its founder, time of registration, last time
used, description, and mode lock, if any. If <b>ALL</b> is
specified, the entry message and successor will also
be displayed.
By default, the <b>ALL</b> option is limited to those with
founder access on the channel.
</pre>
</li>
<li>
<h3><b>LIST</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>LIST <u>pattern</u></b>
Lists all registered channels matching the given pattern.
(Channels with the <b>PRIVATE</b> option set are not listed.)
Note that a preceding '#' specifies a range, channel names
are to be written without '#'.
</pre>
</li>
<li>
<h3><b>OP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>OP [<u>#channel</u> [<u>nick</u>]]</b>
Ops a selected nick on a channel. If nick is not given,
it will op you. If channel and nick are not given,
it will op you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel.
</pre>
</li>
<li>
<h3><b>DEOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DEOP [<u>#channel</u> [<u>nick</u>]]</b>
Deops a selected nick on a channel. If nick is not given,
it will deop you. If channel and nick are not given,
it will deop you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel.
</pre>
</li>
<li>
<h3><b>VOICE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>VOICE [<u>#channel</u> [<u>nick</u>]]</b>
Voices a selected nick on a channel. If nick is not given,
it will voice you. If channel and nick are not given,
it will voice you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel, or to VOPs or those with level 3
and above for self voicing.
</pre>
</li>
<li>
<h3><b>DEVOICE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DEVOICE [<u>#channel</u> [<u>nick</u>]]</b>
Devoices a selected nick on a channel. If nick is not given,
it will devoice you. If channel and nick are not given,
it will devoice you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel, or to VOPs or those with level 3
and above for self devoicing.
</pre>
</li>
<li>
<h3><b>HALFOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>HALFOP [<u>#channel</u> [<u>nick</u>]]</b>
Halfops a selected nick on a channel. If nick is not given,
it will halfop you. If channel and nick are not given,
it will halfop you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs and those with level 5 access
and above on the channel, or to HOPs or those with level 4
and above for self halfopping.
</pre>
</li>
<li>
<h3><b>DEHALFOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DEHALFOP [<u>#channel</u> [<u>nick</u>]]</b>
Dehalfops a selected nick on a channel. If nick is not given,
it will dehalfop you. If channel and nick are not given,
it will dehalfop you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs and those with level 5 access
and above on the channel, or to HOPs or those with level 4
and above for self dehalfopping.
</pre>
</li>
<li>
<h3><b>PROTECT</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>PROTECT [<u>#channel</u> [<u>nick</u>]]</b>
Protects a selected nick on a channel. If nick is not given,
it will protect you. If channel and nick are not given,
it will protect you on all channels you're on, provided you
have the rights to.
By default, limited to the founder, or to SOPs or those with
level 10 and above on the channel for self protecting.
</pre>
</li>
<li>
<h3><b>DEPROTECT</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DEPROTECT [<u>#channel</u> [<u>nick</u>]]</b>
Deprotects a selected nick on a channel. If nick is not given,
it will deprotect you. If channel and nick are not given,
it will deprotect you on all channels you're on, provided you
have the rights to.
By default, limited to the founder, or to SOPs or those with
level 10 and above on the channel for self deprotecting.
</pre>
</li>
<li>
<h3><b>OWNER</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>OWNER [<u>#channel</u>]</b>
Gives you owner status on <b>channel</b>. If channel is not
given, it will give you owner status on all channels you're
on, provided you have the rights to.
Limited to those with founder access on the channel.
</pre>
</li>
<li>
<h3><b>DEOWNER</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DEOWNER [<u>#channel</u>]</b>
Removes your owner status on <b>channel</b>. If channel is
not given, it will remove your owner status on all channels
you're on, provided you have the rights to.
Limited to those with founder access on the channel.
</pre>
</li>
<li>
<h3><b>INVITE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>INVITE <u>channel</u></b>
Tells GalaxyServ to invite you into the given channel.
By default, limited to AOPs or those with level 5 and above
on the channel.
</pre>
</li>
<li>
<h3><b>UNBAN</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>UNBAN <u>channel</u></b>
Tells GalaxyServ to remove all bans preventing you from
entering the given channel.
By default, limited to AOPs or those with level 5 and above
on the channel.
</pre>
</li>
<li>
<h3><b>KICK</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>KICK [<u>#channel</u> [<u>nick</u> [<u>reason</u>]]]</b>
Kicks a selected nick on a channel. If nick is not given,
it will kick you. If channel and nick are not given,
it will kick you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel.
</pre>
</li>
<li>
<h3><b>BAN</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>BAN [<u>#channel</u> [<u>nick</u> [<u>reason</u>]]]</b>
Bans a selected nick on a channel. If nick is not given,
it will ban you. If channel and nick are not given,
it will ban you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel.
</pre>
</li>
<li>
<h3><b>TOPIC</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>TOPIC <u>channel</u> [<u>topic</u>]</b>
Causes GalaxyServ to set the channel topic to the one
specified. If <b>topic</b> is not given, then an empty topic
is set. This command is most useful in conjunction
with <b>SET TOPICLOCK</b>. See <b>/msg GalaxyServ HELP SET TOPICLOCK</b>
for more information.
By default, limited to those with founder access on the
channel.
</pre>
</li>
<li>
<h3><b>CLEAR</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>CLEAR <u>channel</u> <u>what</u></b>
Tells GalaxyServ to clear certain settings on a channel. <u>what</u>
can be any of the following:
MODES Resets all modes on the channel (i.e. clears
modes i,k,l,m,n,p,s,t).
BANS Clears all bans on the channel.
EXCEPTS Clears all excepts on the channel.
INVITES Clears all invites on the channel.
OPS Removes channel-operator status (mode +o) from
all channel operators.
HOPS Removes channel-halfoperator status (mode +h) from
all channel halfoperators, if supported.
VOICES Removes "voice" status (mode +v) from anyone
with that mode set.
USERS Removes (kicks) all users from the channel.
By default, limited to those with founder access on the
channel.
</pre>
</li>
<li>
<h3><b>GETKEY</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>GETKEY <u>channel</u></b>
Returns the key of the given channel. This is a command
mainly intended to be used by bots and/or scripts, so
the output is in the following way:
KEY <channel> <key>
key is "NO KEY" if no key is set.
</pre>
</li>
</ul>
<h3> </h3><h1>GalaxyServ Commands</h1>
<h2>For most clients you can shorten /msg GalaxyServ for /gs command.</h2>
<h2>We do use GalaxyServ in place of ChanServ, if you are used to using /cs the commands will work the same way if you type /cs command.</h2>
<div> </div>
<ul>
<li>
<h3><b>HELP</b></h3>
<pre><b>GalaxyServ</b> allows you to register and control various
aspects of channels. GalaxyServ can often prevent
malicious users from "taking over" channels by limiting
who is allowed channel operator privileges. Available
commands are listed below; to use them, type
<b>/msg GalaxyServ <u>command</u></b>. For more information on a
specific command, type <b>/msg GalaxyServ HELP <u>command</u></b>.
</pre>
</li>
<li>
<h3><b>EXPIRES</b></h3>
<pre>
Note that any channel which is not used for <num> days
(i.e. which no user on the channel's access list enters
for that period of time) will be automatically dropped.
</pre>
</li>
<li>
<h3><b>REGISTER</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>REGISTER <u>channel</u> <u>password</u> <u>description</u></b>
Registers a channel in the GalaxyServ database. In order
to use this command, you must first be a channel operator
on the channel you're trying to register. The password
is used with the <b>IDENTIFY</b> command to allow others to
make changes to the channel settings at a later time.
The last parameter, which <b>must</b> be included, is a
general description of the channel's purpose.
When you register a channel, you are recorded as the
"founder" of the channel. The channel founder is allowed
to change all of the channel settings for the channel;
GalaxyServ will also automatically give the founder
channel-operator privileges when s/he enters the channel.
See the <b>ACCESS</b> command (<b>/msg GalaxyServ HELP ACCESS</b>) for
information on giving a subset of these privileges to
other channel users.
NOTICE: In order to register a channel, you must have
first registered your nickname. If you haven't,
<b>/msg GalaxyServ HELP</b> for information on how to do so.
</pre>
</li>
<li>
<h3><b>IDENTIFY</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>IDENTIFY <u>channel</u> <u>password</u></b>
Authenticates you to GalaxyServ as the founder of the given
channel. Many commands require you to use this command
before using them. The password should be the same one
you sent with the <b>REGISTER</b> command.
</pre>
</li>
<li>
<h3><b>LOGOUT</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>LOGOUT <u>channel</u> <u>nickname</u></b>
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.
</pre>
</li>
<li>
<h3><b>DROP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DROP <u>channel</u></b>
Unregisters the named channel. Can only be used by
<b>channel founder</b>, who must use the <b>IDENTIFY</b> command first.
</pre>
</li>
<li>
<h3><b>SET</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> <u>option</u> <u>parameters</u></b>
Allows the channel founder to set various channel options
and other information.
Available options:
FOUNDER Set the founder of a channel
SUCCESSOR Set the successor for a channel
PASSWORD Set the founder password
DESC Set the channel description
URL Associate a URL with the channel
EMAIL Associate an E-mail address with the channel
ENTRYMSG Set a message to be sent to users when they
enter the channel
BANTYPE Set how Services make bans on the channel
MLOCK Lock channel modes on or off
KEEPTOPIC Retain topic when channel is not in use
OPNOTICE Send a notice when OP/DEOP commands are used
PEACE Regulate the use of critical commands
PRIVATE Hide channel from LIST command
RESTRICTED Restrict access to the channel
SECURE Activate GalaxyServ security features
SECUREOPS Stricter control of chanop status
SECUREFOUNDER Stricter control of channel founder status
SIGNKICK Sign kicks that are done with KICK command
TOPICLOCK Topic can only be changed with TOPIC
XOP Toggle the user privilege system
Type <b>/msg GalaxyServ HELP SET <u>option</u></b> for more information on a
particular option.
</pre>
</li>
<li>
<h3><b>SET FOUNDER</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> FOUNDER <u>nick</u></b>
Changes the founder of a channel. The new nickname must
be a registered one.
</pre>
</li>
<li>
<h3><b>SET SUCCESSOR</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> SUCCESSOR <u>nick</u></b>
Changes the successor of a channel. If the founder's
nickname expires or is dropped while the channel is still
registered, the successor will become the new founder of the
channel. However, if the successor already has too many
channels registered (<num>), the channel will be dropped
instead, just as if no successor had been set. The new
nickname must be a registered one.
</pre>
</li>
<li>
<h3><b>SET PASSWORD</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> PASSWORD <u>password</u></b>
Sets the password used to identify as the founder of the
channel.
</pre>
</li>
<li>
<h3><b>SET DESC</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> DESC <u>description</u></b>
Sets the description for the channel, which shows up with
the <b>LIST</b> and <b>INFO</b> commands.
</pre>
</li>
<li>
<h3><b>SET URL</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> URL [<u>url</u>]</b>
Associates the given URL with the channel. This URL will
be displayed whenever someone requests information on the
channel with the <b>INFO</b> command. If no parameter is given,
deletes any current URL for the channel.
</pre>
</li>
<li>
<h3><b>SET EMAIL</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> EMAIL [<u>address</u>]</b>
Associates the given E-mail address with the channel.
This address will be displayed whenever someone requests
information on the channel with the <b>INFO</b> command. If no
parameter is given, deletes any current E-mail address for
the channel.
</pre>
</li>
<li>
<h3><b>SET ENTRYMSG</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> ENTRYMSG [<u>message</u>]</b>
Sets the message which will be sent via /notice to users
when they enter the channel. If no parameter is given,
causes no message to be sent upon entering the channel.
</pre>
</li>
<li>
<h3><b>SET BANTYPE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> BANTYPE <u>bantype</u></b>
Sets the ban type that will be used by services whenever
they need to ban someone from your channel.
bantype is a number between 0 and 3 that means:
0: ban in the form *!user@host
1: ban in the form *!*user@host
2: ban in the form *!*@host
3: ban in the form *!*user@*.domain
</pre>
</li>
<li>
<h3><b>SET KEEPTOPIC</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> KEEPTOPIC {ON | OFF}</b>
Enables or disables the <b>topic retention</b> option for a
channel. When <b>topic retention</b> is set, the topic for the
channel will be remembered by GalaxyServ even after the
last user leaves the channel, and will be restored the
next time the channel is created.
</pre>
</li>
<li>
<h3><b>SET TOPICLOCK</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> TOPICLOCK {ON | OFF}</b>
Enables or disables the <b>topic lock</b> option for a channel.
When <b>topic lock</b> is set, GalaxyServ will not allow the
channel topic to be changed except via the <b>TOPIC</b>
command.
</pre>
</li>
<li>
<h3><b>SET MLOCK</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> MLOCK <u>modes</u></b>
Sets the mode-lock parameter for the channel. GalaxyServ
allows you to define certain channel modes to be always
on, off or free to be either on or off.
The <u>modes</u> parameter is constructed exactly the same way
as a <b>/MODE</b> command; that is, modes followed by a + are
locked on, and modes followed by a - are locked off. Note,
however, that unlike the <b>/MODE</b> command, each use of
<b>SET MLOCK</b> will remove all modes previously locked before
setting the new!
<b>Warning:</b> If you set a mode-locked key, as in the second
example below, you should also set the <b>RESTRICTED</b> option for
the channel (see <b>HELP SET RESTRICTED</b>), or anyone entering
the channel when it is empty will be able to see the key!
Examples:
<b>SET #channel MLOCK +nt-iklps</b>
Forces modes n and t on, and modes i, k, l, p, and
s off. Mode m is left free to be either on or off.
<b>SET #channel MLOCK +knst-ilmp my-key</b>
Forces modes k, n, s, and t on, and modes i, l, m,
and p off. Also forces the channel key to be
"my-key".
<b>SET #channel MLOCK +</b>
Removes the mode lock; all channel modes are free
to be either on or off.
</pre>
</li>
<li>
<h3><b>SET PEACE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> PEACE {ON | OFF}</b>
Enables or disables the <b>peace</b> option for a channel.
When <b>peace</b> is set, an user won't be able to kick,
ban or remove a channel status of an user that has
a level superior or equal to his via GalaxyServ commands.
</pre>
</li>
<li>
<h3><b>SET PRIVATE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> PRIVATE {ON | OFF}</b>
Enables or disables the <b>private</b> option for a channel.
When <b>private</b> is set, a <b>/msg GalaxyServ LIST</b> will not
include the channel in any lists.
</pre>
</li>
<li>
<h3><b>SET RESTRICTED</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> RESTRICTED {ON | OFF}</b>
Enables or disables the <b>restricted access</b> option for a
channel. When <b>restricted access</b> is set, users not on
the access list will instead be kicked and banned from the channel.
</pre>
</li>
<li>
<h3><b>SET SECURE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> SECURE {ON | OFF}</b>
Enables or disables GalaxyServ's security features for a
channel. When <b>SECURE</b> is set, only users who have
registered their nicknames with GalaxyServ and IDENTIFY'd
with their password will be given access to the channel
as controlled by the access list.
</pre>
</li>
<li>
<h3><b>SET SECUREOPS</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> SECUREOPS {ON | OFF}</b>
Enables or disables the <b>secure ops</b> option for a channel.
When <b>secure ops</b> is set, users who are not on the userlist
will not be allowed chanop status.
</pre>
</li>
<li>
<h3><b>SET SECUREFOUNDER</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> SECUREFOUNDER {ON | OFF}</b>
Enables or disables the <b>secure founder</b> option for a channel.
When <b>secure founder</b> is set, only the real founder will be
able to drop the channel, change its password, its founder and its
successor, and not those who are IDENTIFY'd with GalaxyServ.
</pre>
</li>
<li>
<h3><b>SET SIGNKICK</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> SIGNKICK {ON | LEVEL | OFF}</b>
Enables or disables signed kicks for a
channel. When <b>SIGNKICK</b> is set, kicks issued with
GalaxyServ KICK command will have the nick that used the
command in their reason.
If you use <b>LEVEL</b>, those who have a level that is superior
or equal to the SIGNKICK level on the channel won't have their
kicks signed. See <b>/msg GalaxyServ HELP LEVELS</b> for more information.
</pre>
</li>
<li>
<h3><b>SET XOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> XOP {ON | OFF}</b>
Enables or disables the xOP lists system for a channel.
When <b>XOP</b> is set, you have to use the <b>AOP</b>/<b>SOP</b>/<b>VOP</b>
commands in order to give channel privileges to
users, else you have to use the <b>ACCESS</b> command.
<b>Technical Note</b>: when you switch from access list to xOP
lists system, your level definitions and user levels will be
changed, so you won't find the same values if you
switch back to access system!
You should also check that your users are in the good xOP
list after the switch from access to xOP lists, because the
guess is not always perfect... in fact, it is not recommended
to use the xOP lists if you changed level definitions with
the <b>LEVELS</b> command.
Switching from xOP lists system to access list system
causes no problem though.
</pre>
</li>
<li>
<h3><b>SET OPNOTICE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SET <u>channel</u> OPNOTICE {ON | OFF}</b>
Enables or disables the <b>op-notice</b> option for a channel.
When <b>op-notice</b> is set, GalaxyServ will send a notice to the
channel whenever the <b>OP</b> or <b>DEOP</b> commands are used for a user
in the channel.
</pre>
</li>
<li>
<h3><b>AOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>AOP <u>channel</u> ADD <u>nick</u></b>
<b>AOP <u>channel</u> DEL {<u>nick</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>AOP <u>channel</u> LIST [<u>mask</u> | <u>list</u>]</b>
<b>AOP <u>channel</u> CLEAR</b>
Maintains the <b>AOP</b> (AutoOP) <b>list</b> for a channel. The AOP
list gives users the right to be auto-opped on your channel,
to unban or invite themselves if needed, to have their
greet message showed on join, and so on.
The <b>AOP ADD</b> command adds the given nickname to the
AOP list.
The <b>AOP DEL</b> command removes the given nick from the
AOP list. If a list of entry numbers is given, those
entries are deleted. (See the example for LIST below.)
The <b>AOP LIST</b> command displays the AOP 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:
<b>AOP #channel LIST 2-5,7-9</b>
Lists AOP entries numbered 2 through 5 and
7 through 9.
The <b>AOP CLEAR</b> command clears all entries of the
AOP list.
The <b>AOP ADD</b> and <b>AOP DEL</b> commands are limited to
SOPs or above, while the <b>AOP CLEAR</b> command can only
be used by the channel founder. However, any user on the
AOP list may use the <b>AOP LIST</b> command.
This command may have been disabled for your channel, and
in that case you need to use the access list. See
<b>/msg GalaxyServ HELP ACCESS</b> for information about the access list,
and <b>/msg GalaxyServ HELP SET XOP</b> to know how to toggle between
the access list and xOP list systems.
</pre>
</li>
<li>
<h3><b>HOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>HOP <u>channel</u> ADD <u>nick</u></b>
<b>HOP <u>channel</u> DEL {<u>nick</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>HOP <u>channel</u> LIST [<u>mask</u> | <u>list</u>]</b>
<b>HOP <u>channel</u> CLEAR</b>
Maintains the <b>HOP</b> (HalfOP) <b>list</b> for a channel. The HOP
list gives users the right to be auto-halfopped on your
channel.
The <b>HOP ADD</b> command adds the given nickname to the
HOP list.
The <b>HOP DEL</b> command removes the given nick from the
HOP list. If a list of entry numbers is given, those
entries are deleted. (See the example for LIST below.)
The <b>HOP LIST</b> command displays the HOP 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:
<b>HOP #channel LIST 2-5,7-9</b>
Lists HOP entries numbered 2 through 5 and
7 through 9.
The <b>HOP CLEAR</b> command clears all entries of the
HOP list.
The <b>HOP ADD</b>, <b>HOP DEL</b> and <b>HOP LIST</b> commands are
limited to AOPs or above, while the <b>HOP CLEAR</b> command
can only be used by the channel founder.
This command may have been disabled for your channel, and
in that case you need to use the access list. See
<b>/msg GalaxyServ HELP ACCESS</b> for information about the access list,
and <b>/msg GalaxyServ HELP SET XOP</b> to know how to toggle between
the access list and xOP list systems.
</pre>
</li>
<li>
<h3><b>SOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>SOP <u>channel</u> ADD <u>nick</u></b>
<b>SOP <u>channel</u> DEL {<u>nick</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>SOP <u>channel</u> LIST [<u>mask</u> | <u>list</u>]</b>
<b>SOP <u>channel</u> CLEAR</b>
Maintains the <b>SOP</b> (SuperOP) <b>list</b> for a channel. The SOP
list gives users all rights given by the AOP list, and adds
those needed to use the AutoKick and the BadWords lists,
to send and read channel memos, and so on.
The <b>SOP ADD</b> command adds the given nickname to the
SOP list.
The <b>SOP DEL</b> command removes the given nick from the
SOP list. If a list of entry numbers is given, those
entries are deleted. (See the example for LIST below.)
The <b>SOP LIST</b> command displays the SOP 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:
<b>SOP #channel LIST 2-5,7-9</b>
Lists AOP entries numbered 2 through 5 and
7 through 9.
The <b>SOP CLEAR</b> command clears all entries of the
SOP list.
The <b>SOP ADD</b>, <b>SOP DEL</b> and <b>SOP CLEAR</b> commands are
limited to the channel founder. However, any user on the
AOP list may use the <b>SOP LIST</b> command.
This command may have been disabled for your channel, and
in that case you need to use the access list. See
<b>/msg GalaxyServ HELP ACCESS</b> for information about the access list,
and <b>/msg GalaxyServ HELP SET XOP</b> to know how to toggle between
the access list and xOP list systems.
</pre>
</li>
<li>
<h3><b>VOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>VOP <u>channel</u> ADD <u>nick</u></b>
<b>VOP <u>channel</u> DEL {<u>nick</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>VOP <u>channel</u> LIST [<u>mask</u> | <u>list</u>]</b>
<b>VOP <u>channel</u> CLEAR</b>
Maintains the <b>VOP</b> (VOicePeople) <b>list</b> for a channel.
The VOP list allows users to be auto-voiced and to voice
themselves if they aren't.
The <b>VOP ADD</b> command adds the given nickname to the
VOP list.
The <b>VOP DEL</b> command removes the given nick from the
VOP list. If a list of entry numbers is given, those
entries are deleted. (See the example for LIST below.)
The <b>VOP LIST</b> command displays the VOP 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:
<b>VOP #channel LIST 2-5,7-9</b>
Lists VOP entries numbered 2 through 5 and
7 through 9.
The <b>VOP CLEAR</b> command clears all entries of the
VOP list.
The <b>VOP ADD</b>, <b>VOP DEL</b> and <b>VOP LIST</b> commands are
limited to AOPs or above, while the <b>VOP CLEAR</b> command
can only be used by the channel founder.
This command may have been disabled for your channel, and
in that case you need to use the access list. See
<b>/msg GalaxyServ HELP ACCESS</b> for information about the access list,
and <b>/msg GalaxyServ HELP SET XOP</b> to know how to toggle between
the access list and xOP list systems.
</pre>
</li>
<li>
<h3><b>ACCESS</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>ACCESS <u>channel</u> ADD <u>nick</u> <u>level</u></b>
<b>ACCESS <u>channel</u> DEL {<u>nick</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>ACCESS <u>channel</u> LIST [<u>mask</u> | <u>list</u>]</b>
<b>ACCESS <u>channel</u> CLEAR</b>
Maintains the <b>access list</b> for a channel. The access
list specifies which users are allowed chanop status or
access to GalaxyServ commands on the channel. Different
user levels allow for access to different subsets of
privileges; <b>/msg GalaxyServ HELP ACCESS LEVELS</b> for more
specific information. Any nick not on the access list has
a user level of 0.
The <b>ACCESS ADD</b> command adds the given nickname to the
access list with the given user level; if the nick is
already present on the list, its access level is changed to
the level specified in the command. The <u>level</u> specified
must be less than that of the user giving the command, and
if the <u>nick</u> is already on the access list, the current
access level of that nick must be less than the access level
of the user giving the command.
The <b>ACCESS DEL</b> command removes the given nick from the
access list. If a list of entry numbers is given, those
entries are deleted. (See the example for LIST below.)
The <b>ACCESS LIST</b> command displays the access 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:
<b>ACCESS #channel LIST 2-5,7-9</b>
Lists access entries numbered 2 through 5 and
7 through 9.
The <b>ACCESS CLEAR</b> command clears all entries of the
access list.
</pre>
</li>
<li>
<h3><b>ACCESS LEVELS</b></h3>
<pre><b>User access levels</b>
By default, the following access levels are defined:
<b>Founder</b> Full access to GalaxyServ functions; automatic
opping upon entering channel. Note
that only one person may have founder
status (it cannot be given using the
<b>ACCESS</b> command).
<b> 10</b> Access to AKICK command; automatic opping.
<b> 5</b> Automatic opping.
<b> 3</b> Automatic voicing.
<b> 0</b> No special privileges; can be opped by other
ops (unless <b>secure-ops</b> is set).
<b> <0</b> May not be opped.
These levels may be changed, or new ones added, using the
<b>LEVELS</b> command; type <b>/msg GalaxyServ HELP LEVELS</b> for
information.
</pre>
</li>
<li>
<h3><b>AKICK</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>AKICK <u>channel</u> ADD {<u>nick</u> | <u>mask</u>} [<u>reason</u>]</b>
<b>AKICK <u>channel</u> STICK <u>mask</u></b>
<b>AKICK <u>channel</u> UNSTICK <u>mask</u></b>
<b>AKICK <u>channel</u> DEL {<u>nick</u> | <u>mask</u> | <u>entry-num</u> | <u>list</u>}</b>
<b>AKICK <u>channel</u> LIST [<u>mask</u> | <u>entry-num</u> | <u>list</u>]</b>
<b>AKICK <u>channel</u> VIEW [<u>mask</u> | <u>entry-num</u> | <u>list</u>]</b>
<b>AKICK <u>channel</u> ENFORCE</b>
<b>AKICK <u>channel</u> CLEAR</b>
Maintains the <b>AutoKick list</b> for a channel. If a user
on the AutoKick list attempts to join the channel,
GalaxyServ will ban that user from the channel, then kick
the user.
The <b>AKICK ADD</b> command adds the given nick or usermask
to the AutoKick list. If a <u>reason</u> is given with
the command, that reason will be used when the user is
kicked; if not, the default reason is "You have been
banned from the channel".
When akicking a <u>registered nick</u> the nickserv account
will be added to the akick list instead of the mask.
All users within that nickgroup will then be akicked.
The <b>AKICK STICK</b> command permanently bans the given mask
on the channel. If someone tries to remove the ban, GalaxyServ
will automatically set it again. You can't use it for
registered nicks.
The <b>AKICK UNSTICK</b> command cancels the effect of the
<b>AKICK STICK</b> command, so you'll be able to unset the
ban again on the channel.
The <b>AKICK DEL</b> command removes the given nick or mask
from the AutoKick list. It does not, however, remove any
bans placed by an AutoKick; those must be removed
manually.
The <b>AKICK LIST</b> command displays the AutoKick list, or
optionally only those AutoKick entries which match the
given mask.
The <b>AKICK VIEW</b> command is a more verbose version of
<b>AKICK LIST</b> command.
The <b>AKICK ENFORCE</b> command causes GalaxyServ to enforce the
current AKICK list by removing those users who match an
AKICK mask.
The <b>AKICK CLEAR</b> command clears all entries of the
akick list.
</pre>
</li>
<li>
<h3><b>LEVELS</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>LEVELS <u>channel</u> SET <u>type</u> <u>level</u></b>
<b>LEVELS <u>channel</u> {DIS | DISABLE} <u>type</u></b>
<b>LEVELS <u>channel</u> LIST</b>
<b>LEVELS <u>channel</u> RESET</b>
The <b>LEVELS</b> command allows fine control over the meaning of
the numeric access levels used for channels. With this
command, you can define the access level required for most
of GalaxyServ's functions. (The <b>SET FOUNDER</b> and <b>SET PASSWORD</b>
commands, as well as this command, are always restricted to
the channel founder.)
<b>LEVELS SET</b> allows the access level for a function or group of
functions to be changed. <b>LEVELS DISABLE</b> (or <b>DIS</b> for short)
disables an automatic feature or disallows access to a
function by anyone other than the channel founder.
<b>LEVELS LIST</b> shows the current levels for each function or
group of functions. <b>LEVELS RESET</b> resets the levels to the
default levels of a newly-created channel (see
<b>HELP ACCESS LEVELS</b>).
For a list of the features and functions whose levels can be
set, see <b>HELP LEVELS DESC</b>.
</pre>
</li>
<li>
<h3><b>INFO</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>INFO <u>channel</u> [ALL]</b>
Lists information about the named registered channel,
including its founder, time of registration, last time
used, description, and mode lock, if any. If <b>ALL</b> is
specified, the entry message and successor will also
be displayed.
By default, the <b>ALL</b> option is limited to those with
founder access on the channel.
</pre>
</li>
<li>
<h3><b>LIST</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>LIST <u>pattern</u></b>
Lists all registered channels matching the given pattern.
(Channels with the <b>PRIVATE</b> option set are not listed.)
Note that a preceding '#' specifies a range, channel names
are to be written without '#'.
</pre>
</li>
<li>
<h3><b>OP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>OP [<u>#channel</u> [<u>nick</u>]]</b>
Ops a selected nick on a channel. If nick is not given,
it will op you. If channel and nick are not given,
it will op you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel.
</pre>
</li>
<li>
<h3><b>DEOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DEOP [<u>#channel</u> [<u>nick</u>]]</b>
Deops a selected nick on a channel. If nick is not given,
it will deop you. If channel and nick are not given,
it will deop you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel.
</pre>
</li>
<li>
<h3><b>VOICE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>VOICE [<u>#channel</u> [<u>nick</u>]]</b>
Voices a selected nick on a channel. If nick is not given,
it will voice you. If channel and nick are not given,
it will voice you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel, or to VOPs or those with level 3
and above for self voicing.
</pre>
</li>
<li>
<h3><b>DEVOICE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DEVOICE [<u>#channel</u> [<u>nick</u>]]</b>
Devoices a selected nick on a channel. If nick is not given,
it will devoice you. If channel and nick are not given,
it will devoice you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel, or to VOPs or those with level 3
and above for self devoicing.
</pre>
</li>
<li>
<h3><b>HALFOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>HALFOP [<u>#channel</u> [<u>nick</u>]]</b>
Halfops a selected nick on a channel. If nick is not given,
it will halfop you. If channel and nick are not given,
it will halfop you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs and those with level 5 access
and above on the channel, or to HOPs or those with level 4
and above for self halfopping.
</pre>
</li>
<li>
<h3><b>DEHALFOP</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DEHALFOP [<u>#channel</u> [<u>nick</u>]]</b>
Dehalfops a selected nick on a channel. If nick is not given,
it will dehalfop you. If channel and nick are not given,
it will dehalfop you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs and those with level 5 access
and above on the channel, or to HOPs or those with level 4
and above for self dehalfopping.
</pre>
</li>
<li>
<h3><b>PROTECT</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>PROTECT [<u>#channel</u> [<u>nick</u>]]</b>
Protects a selected nick on a channel. If nick is not given,
it will protect you. If channel and nick are not given,
it will protect you on all channels you're on, provided you
have the rights to.
By default, limited to the founder, or to SOPs or those with
level 10 and above on the channel for self protecting.
</pre>
</li>
<li>
<h3><b>DEPROTECT</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DEPROTECT [<u>#channel</u> [<u>nick</u>]]</b>
Deprotects a selected nick on a channel. If nick is not given,
it will deprotect you. If channel and nick are not given,
it will deprotect you on all channels you're on, provided you
have the rights to.
By default, limited to the founder, or to SOPs or those with
level 10 and above on the channel for self deprotecting.
</pre>
</li>
<li>
<h3><b>OWNER</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>OWNER [<u>#channel</u>]</b>
Gives you owner status on <b>channel</b>. If channel is not
given, it will give you owner status on all channels you're
on, provided you have the rights to.
Limited to those with founder access on the channel.
</pre>
</li>
<li>
<h3><b>DEOWNER</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>DEOWNER [<u>#channel</u>]</b>
Removes your owner status on <b>channel</b>. If channel is
not given, it will remove your owner status on all channels
you're on, provided you have the rights to.
Limited to those with founder access on the channel.
</pre>
</li>
<li>
<h3><b>INVITE</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>INVITE <u>channel</u></b>
Tells GalaxyServ to invite you into the given channel.
By default, limited to AOPs or those with level 5 and above
on the channel.
</pre>
</li>
<li>
<h3><b>UNBAN</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>UNBAN <u>channel</u></b>
Tells GalaxyServ to remove all bans preventing you from
entering the given channel.
By default, limited to AOPs or those with level 5 and above
on the channel.
</pre>
</li>
<li>
<h3><b>KICK</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>KICK [<u>#channel</u> [<u>nick</u> [<u>reason</u>]]]</b>
Kicks a selected nick on a channel. If nick is not given,
it will kick you. If channel and nick are not given,
it will kick you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel.
</pre>
</li>
<li>
<h3><b>BAN</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>BAN [<u>#channel</u> [<u>nick</u> [<u>reason</u>]]]</b>
Bans a selected nick on a channel. If nick is not given,
it will ban you. If channel and nick are not given,
it will ban you on all channels you're on, provided you
have the rights to.
By default, limited to AOPs or those with level 5 access
and above on the channel.
</pre>
</li>
<li>
<h3><b>TOPIC</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>TOPIC <u>channel</u> [<u>topic</u>]</b>
Causes GalaxyServ to set the channel topic to the one
specified. If <b>topic</b> is not given, then an empty topic
is set. This command is most useful in conjunction
with <b>SET TOPICLOCK</b>. See <b>/msg GalaxyServ HELP SET TOPICLOCK</b>
for more information.
By default, limited to those with founder access on the
channel.
</pre>
</li>
<li>
<h3><b>CLEAR</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>CLEAR <u>channel</u> <u>what</u></b>
Tells GalaxyServ to clear certain settings on a channel. <u>what</u>
can be any of the following:
MODES Resets all modes on the channel (i.e. clears
modes i,k,l,m,n,p,s,t).
BANS Clears all bans on the channel.
EXCEPTS Clears all excepts on the channel.
INVITES Clears all invites on the channel.
OPS Removes channel-operator status (mode +o) from
all channel operators.
HOPS Removes channel-halfoperator status (mode +h) from
all channel halfoperators, if supported.
VOICES Removes "voice" status (mode +v) from anyone
with that mode set.
USERS Removes (kicks) all users from the channel.
By default, limited to those with founder access on the
channel.
</pre>
</li>
<li>
<h3><b>GETKEY</b></h3>
<pre><i>Syntax:</i> /msg GalaxyServ <b>GETKEY <u>channel</u></b>
Returns the key of the given channel. This is a command
mainly intended to be used by bots and/or scripts, so
the output is in the following way:
KEY <channel> <key>
key is "NO KEY" if no key is set.
</pre>
</li>
</ul>
<h3> </h3>