Welcome to the NewNet IRC Network Channel Service Class.
This class will cover the basics of channel operation/management through the use of ChanServ. This is the place to learn basic IRC channel commands to help manage your channel using ChanServ.
--===========================================================================--
** Note ** #Services is the official ChanServ and Nickserv help channel. All comments/suggestions about this script can be sent via e-mail to LadyBear@ladybear.com. Thanks!

This class will cover the Channel Services bot (ChanServ) commands only.

When you see a word(s) separated by a |; it usually means \or\. DOS wildcards are used with many commands; a * is used to replace multiple characters and ? is used to replace a single character. A \-\ means take way and \+\ means to give

--===========================================================================--
Section 1: Introduction to the commands

ChanServ allows you to register and control various aspects of your channels. ChanServ can often prevent malicious users from aking over\ channels by limiting who is allowed channel operator privileges.

All commands are accessed by typing /msg ChanServ [command].

NOTE: Do not type these commands while class is going on. You will only confuse yourself. To stop the temptation, (since I can't unplug your keyboard :)) I have put in where the rest of the syntax should be. We will cover those options later in the class.

HELP The most important command
Syntax : /msg ChanServ HELP

REGISTER Register a channel
Syntax : /msg ChanServ REGISTER [channel] [options]

IDENTIFY Identify yourself with your password
Syntax : /msg ChanServ IDENTIFY [channel] [options]

SET Set channel options and information
Syntax : /msg ChanServ SET [channel] [options]

ACCESS Modify the list of privileged users
Syntax : /msg ChanServ ACCESS [channel] [options]

AKICK Maintain the AutoKick list
Syntax : /msg ChanServ AKICK [channel] [options]

DROP Cancel the registration of a channel
Syntax : /msg ChanServ DROP [channel] [options]

CLEAR Reclaim channel if its taken over
Syntax : /msg ChanServ CLEAR [channel] [options]

UNBAN Remove all bans preventing you from entering your channel.
Syntax : /msg ChanServ UNBAN [channel] [options]

LEVELS Allows founders to re assign access level values.
Syntax : /msg ChanServ LEVELS [channe] [options]

INFO Displays the registration information of a channel
Syntax : /msg ChanServ INFO [channel] [options]

LIST Lists all the channels.
Syntax : /msg ChanServ LIST

INVITE Invites you to your channel
Syntax : /msg ChanServ INVITE [channel]

OP Ops people in your channel
Syntax : /msg ChanServ OP [channel] [options]

DEOP Deop people in your channel
Syntax : /msg ChanServ DEOP [channel] [options]

Each of these commands will be explored in subsequent sections.

** Note ** The above commands are taken directly from /msg ChanServ HELP

** Note ** The PART command has been disabled.

--===========================================================================--
Section 2: Registration

For those wishing to have ChanServ in their channel and don't know how to get him there, you must register the channel. Once you have ChanServ in your channel, you can make use of all the features it has to offer. It is in your best interest to make use of ChanServ.

To register your channel, you must make use of the REGISTER command Syntax /msg ChanServ REGISTER #[channel] [password] [description] ie. /msg ChanServ REGISTER #services-help 1gI4Dw Training Classroom.

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 IDENTIFY command to allow you to make changes to the channel settings at a later time. The last parameter, which must be included, is a general description of the channel's purpose.

** Note ** You must have your nick registered with NickServ. If it is not, type /msg NickServ register [password].

** Special Note ** Passwords ARE case sensitive.

If you do not see the following, you did it wrong: [ChanServ] This channel has just been registered by: [your nick]. If you dispute this you should /JOIN #services now and let us know.

When you register a channel, you are recorded as the ounder\ of the channel. The channel founder is allowed to change all of the channel settings for the channel. ChanServ will also automatically give the founder channel-operator privileges when he/she enters the channel. See the ACCESS command for information on giving other users channel op and co-founder access.

IDENTIFY = tell chanserv you really are the founder
Syntax : /msg ChanServ IDENTIFY #[channel] [password]
ie. /msg ChanServ IDENTIFY #chanop 1gI4Dw
Many commands require you to use this command before using them. The password should be the same one you set with the REGISTER command.

DROP = Drop channel registration
Syntax : /msg ChanServ DROP #[channel]
ie. /msg ChanServ DROP #chanop
In case you make a mistake in registering or you no longer want to be the founder you can drop the channel registration.
(see SET FOUNDER for an alternative)
** Note ** This can only be used by the channel founder who must use the IDENTIFY command first.

INFO = Displays the registered channel information
Syntax : /msg ChanServ INFO #[channel]
You can learn who registered the channel, when they did it, and what the channel is about.

LIST = Lists channels
Syntax : /msg ChanServ LIST [mask] ie. /msg ChanServ LIST help
This gives a list of channel matching the mask you entered. Any channel with the +p set will not show up.

INVITE = Allow a user access to an invite only (+i) channel
Syntax : /msg ChanServ INVITE #[channel]
Tells ChanServ to invite you into the channel. This Only works if you are on the access list at a level greater than zero.

OP = Give Channel Operator status to a user
Syntax : /msg ChanServ OP #[channel] [nick]
Ops a selected user on a channel (puts a '@' next to their nick.) Only available to persons with level five access or higher on that channel. See also: DEOP

DEOP = Remove Channel Operator status from a user
Syntax : /msg ChanServ DEOP #[channel] [nick]
Deops a selected nick on a channel (takes away the '@'.) Only available to persons with level five access or higher on that channel.
See also: OP

SET = Change options for channel
Syntax : /msg ChanServ SET #[channel] [option] [parameters]
This command allows the channel founder to set various channel options and other information. The founder must use the IDENTIFY command before using SET.

--===========================================================================--
Section 2 - Subsection: The SET command

Here are the specifics of the SET command.

Syntax : /msg ChanServ SET #[channe] FOUNDER [nick]
Changes the founder of a channel. The new nickname must be a registered one.

Syntax : /msg ChanServ SET #[channel] PASSWORD [password]
Changes the founder password. You must know the old password before you can set a new one. This is helpful if someone who is not supposed to have your password gets it.

Syntax : /msg ChanServ SET #[channel] URL [description]
Sets the homepage URL for the channel which will show up with the INFO command.

Syntax : /msg ChanServ SET #[channel] DESC [description]

Sets the description for the channel which will show up with the LIST and INFO command. The description can be used as a greeting message to each person who joins the channel.

Syntax : /msg ChanServ SET #[channel] GREET ON|OFF
Enables or disables ChanServ greeting users when they join the channel. See above for setting the greeting message.

Syntax : /msg ChanServ SET #[channel] TOPIC [topic]
Causes ChanServ to set the channel topic to the one specified. This command is most useful in conjunction with SET TOPICLOCK.

Syntax : /msg ChanServ SET #[channel] KEEPTOPIC ON|OFF
Enables or disables the topic retention option for a channel. When topic retention is set, the topic for the channel will be remembered by ChanServ even after the last user leaves the channel, and will be restored the next time someone joins the channel, or if ChanServ returns from a netsplit.

Syntax : /msg ChanServ SET #[channel] TOPICLOCK ON|OFF
Enables or disables the topic lock option for a channel. When topic lock is set, ChanServ will not allow the channel topic to be changed except via the SET TOPIC command.

Syntax : /msg ChanServ SET #[channel] PRIVATE ON|OFF
Enables or disables the private (+p) option for a channel. When private is set, a /MSG ChanServ LIST [mask] will not include the channel.

--===========================================================================--
Section 3: Preventing Takeovers

There comes a time when a channel faces a akeover.\ This is where a user gets ops and then wreaks havoc with the channel. Most often the problem user makes it where your regular users can't get in. Below are the methods to prevent such things from happening. This can make or break your channel's flow.

The first and foremost defense is not to give ops (+o) to anyone who asks for it and you don't know the person. Some times people impersonate others, so verify that the person is who they say they are before giving them ops.

MLOCK = Prevent mode changes
Syntax : /msg ChanServ SET #[channel] MLOCK [modes]
This keeps ops from changing your channel modes except through ChanServ. It makes them either on or off, and if they are changed, ChanServ will reset the mode(s). The modes that can be locked are i, k, l, m, n, p, s, and t; each of these modes can be locked on, locked off, or not locked. The [modes] parameter is exactly the same as a /MODE command; that is, modes followed by a + are locked on, and modes followed by a - are locked off.

Warning: If you set a mode-locked key (+k), anyone entering the channel when it is empty will be able to see the key. The most common mode lock is +nt-iklps (/msg ChanServ SET #channel MLOCK +nt-iklps). This prevents unauthorized ops from keeping users out.

** Note ** To reset the mode locks simply use a +.
(/msg ChanServ SET #channel MLOCK +)

SECUREOPS = Prevents people not on the ChanServ access list from getting ops
Syntax : /msg ChanServ SET # SECUREOPS \{ON or OFF\}
When SECUREOPS is set, users who are not on the userlist AND haven't identified with NickServ will not be allowed chanop status. This prevents \accidentally\ oped people from wreaking havoc with your channel.

RESTRICTED = Prevents non operators from joining the channel
Syntax : /msg ChanServ SET # RESTRICTED \{ON or OFF\}
When RESTRICTED is set, users who would normally be disallowed from having channel operator privileges (users with negative access levels and non channel operators and, if SECUREOPS is set, users not on the access list) will instead be kicked and banned from the channel.

SECURE = Keeps unwanted people out by using the access list
Syntax : /msg ChanServ SET # SECURE \{ON on OFF\}
When SECURE is set, only users who have registered their nicknames with NickServ and IDENTIFY'd with their password will be given access to the channel as controlled by the ACCESS list (see below).
** Note ** The access list may only contain registered nicknames if SECURE is set.

ACCESS = List of nicks or hosts that allows channel privileges
Syntax : /msg ChanServ ACCESS #[channel] ADD [mask] [level]
ACCESS #[channel] DEL \{[mask] or [entry-num]\}
ACCESS #[channel] LIST [mask]

Maintains the ACCESS list for a channel. The access list specifies which users are allowed chanop status or access to ChanServ commands on the channel. Different user levels allow for access to different subsets of privileges.
** NOTE ** Type /msg ChanServ HELP ACCESS LEVELS for more specific information. By default, any nick not on the access list has a user level of 0.

ACCESS ADD Adds the given nickname or usermask to the access list with the given user level; if the nick or mask is already present on the list, its access level is changed to the level specified in the command.
ACCESS DEL Removes the given nick or mask from the access list.
ACCESS LIST Displays the access list; if a mask is given, only those entries matching the mask are displayed.

AKICK = Permanent way of keeping someone out of the channel
Syntax : /msg ChanServ AKICK #[channel] ADD [mask] \[reason\]
AKICK #[channel] DEL [mask]
AKICK #[channel] LIST [mask]
Maintains the AutoKick list for a channel. If a user on the AutoKick list attempts to join the channel, ChanServ will ban that user from the channel, then kick the user.
AKICK ADD Adds the given nick or usermask to the AutoKick list. If a reason 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\.
AKICK DEL 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.

This is useful when your ban list starts to fill up. The maximum number of bans allowed at one time is 30. Also, AKICK no longer allows domains to be put on the list.

LEVELS = Control what access levels mean
Syntax : /msg ChanServ LEVELS #[channel] SET [type] [level]
LEVELS #[channel] \{DIS or DISABLE\} [type]
LEVELS #[channel] LIST
LEVELS #[channel] RESET
The LEVELS 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 ChanServ's functions. (The SET FOUNDER and SET PASSWORD commands, as well as this command, are always restricted to the channel founder.)

LEVELS SET Allows the access level for a function or group of functions to be changed.
LEVELS DISABLE (or DIS for short) disables an automatic feature or disallows access to a function by anyone other than the channel founder.
LEVELS LIST Shows the current levels for each function or group of functions.
LEVELS RESET Resets the levels to the default levels of a newly-created channel (see /msg ChanServ HELP ACCESS LEVELS).
For a list of the features and functions whose levels can be set, type /msg ChanServ HELP LEVELS DESC.

--===========================================================================--
Section 4: Recovering after Takeovers

No matter how careful we are, eventually someone will succeed in a takeover.
What happens then? ChanServ has a few commands to help recover your channel.

CLEAR = Clears the channel of certain settings
Syntax : /msg ChanServ CLEAR #[channel] [what]
Tells ChanServ to clear certain settings on a channel. [what] 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.
OPS Removes channel-operator status (mode +o) from all channel operators.
VOICES Removes "voice" status (mode +v) from anyone with that mode set.
USERS Removes (kicks) all users from the channel.

** Note ** Only founders can use the above command unless you set it differently in LEVELS.

UNBAN = Removes all bans in a channel
Syntax : /msg ChanServ UNBAN #[channel]
Tells ChanServ to remove all bans preventing YOU from entering the given channel. Only works if your access level on that channel is greater than zero.

** Note ** Do not remove a ban unless you placed it or have spoken with the person who did. That ban you remove could allow someone to takeover your channel.

There is still another option. Join any Admin/IRCop channel and ask for help. All the IRCop will do is temporarily change the founder and use one or more of the above commands to regain the channel.
Do tell an IRCop so that the problem person is removed from the network and prevents further abuse (have logs).

--===========================================================================--
Section 5: Masks & Wildcards

A wildcard is used the same way it is in DOS. An asterisks (*) is used for many characters and a question mark (?) is used for a single character.
User@Hosts or user@ip are shown when a person does a /whois on users. Masks are variations of these using wildcard characters. Several of the commands we talked about earlier use u@h masks or host masks.

As an example say we do a /whois DaMan. What may be shown as his user@host address will be shown 1 of 4 different ways:
1.) DaMan@shck-72ppp195.epix.net
2.) ~DaMan@shck-72ppp195.epix.net
3.) DaMan@199.224.72.195
4.) ~DaMan@199.224.72.195

A MASK may be made from anyone of these. You will notice that tilde (~) is in front of two of the addresses. The tilde indicates that the person is not using an ident daemon (identd).

In almost all cases an * should be used before the DaMan@. This eliminates the tilde so that command(s) using a mask won't miss the user should they use identd.

User MASKs are in the form (using the example) :
1.) *!*DaMan@*.epix.net
2.) *!*DaMan@199.224.72.*
3.) *!*DaMan@199.224.* (in some rare cases)
A ? may be used anywhere within the mask to replace a particular character if you choose.

These are the types of MASKs you need to use with commands like ACCESS and AKICK. Again, AKICK will not allow domains to be placed on the list.