ChanServ – Part 1


ChanServ is what holds the information for your channel if you register it. It stores all of the access levels, the auto-op list, and such. This guide will show you how to register a channel, as well as explain the different options for configuring your channel.

Registering Your Channel

First and foremost, you must have a registered nick to register a channel. If you don’t, please see the NickServ tutorial for that. Registering a channel is about as simple as registering your nickname, but there is a little more involved with channel options compared to a nickname. Let’s start off with the command for register.

/cs register #channel password description
It is often recommended to use a strong password for the channel, to prevent a channel take-over. IRC Ops will not help you in channel affairs. For the description, this is basically a summary of what your channel is about, so that can be anything you wish.

When you register a channel, you will automatically be identified with the channel as the channel founder. If, for some reason, you are not, you can always identify yourself to the channel with this:

/cs identify #channel password
Be sure to use the password you used to register the channel.

If, for whatever reason you wish to drop your channel’s registration, then use this command to do so:

/cs drop #channel
This will delete your channels information from the ChanServ database.

Configuring Your Channel

The daunting task of configuring.

At first, there may be a lot of options for configuring a channel, but it will be worth it if your up to the task. We’ll start with the more simple options, then work our way to the more advanced options.

/cs set #channel founder name
By default, your name is recorded as the founder, but if for some reason you wish to change it, then here you go. Founders have power to change every option for the channel.

/cs set #channel successor name
This sets the co-founder, or successor, for the channel. If, for some reason the founder’s nickname were to be dropped from NickServ, then the Successor will be moved to the founder position. It is recommended to set this option just in case to prevent the channel from being dropped.

/cs set #channel password newpassword
This will change the password used to identify as the channel founder.

/cs set #channel desc newdescription
This changes the description for your channel.

/cs set #channel url website
This will associate a URL for your channel, that will show in the channel info.

/cs set #channel email email
This will set an email for your channel. This is more of a way of contact for the channel founder, or for IRC Ops when they need to contact people.

/cs set #channel entrymsg message
This will send a /notice to the users when they enter the channel. The message can be anything you wish.

/cs set #channel bantype {number}
This sets the bantype for the auto-ban system. There are 4 different types, and here is what each one means:
0 -> *!user@host – This bans anyone that matches the ident of the user and the hostname for it. The user also has an ident response to the IRCD.
1 -> *!*user@host – This is similar to 0, however this will ban anyone with an ident response or not.
2 -> *!*@host – The most common ban type, where if the host matches, the user will be banned.
3 -> *!*user@*.domain – This will ban anyone with a matching ident and domain.

/cs set #channel mlock parameters
The MLOCK, or Mode Lock, sets the lock on channel modes so they can’t be changed by other channel operators. There are different ways to set the MLOCK, and we’ll explain them here.
MLOCK +npst -> This sets the MLOCK to modes n, p, s, and t on, and they can’t be turned off. All the other modes are free to be on or off.
MLOCK +np-iklps -> The modes n and p are locked on, while i, k, l, p, and s are locked off. The mode m is left to be either on or off.
MLOCK +knsp-iklm my-key -> Modes k, n, s, and p are locked on, which also locks my-key as the channel key to enter the channel. Modes i, k, l, and m are locked off.

/cs set #channel keeptopic {ON|OFF}
This turns on, or off, the keeptopic option. When this is on, ChanServ will store the channel topic so that when no one is in the channel, it will automatically set it back when a user joins the channel.

/cs set #channel opnotice {ON|OFF}
The op-notice feature will send a /notice to operators of the channel whenever an operator uses the OP or DEOP command through ChanServ.

/cs set #channel peace {ON|OFF}
When this is set to on, this prevents users from kicking others that has a level equal, or superior to that of their own.

/cs set #channel private {ON|OFF}
This option prevents the channel from being shown in a channel list.

/cs set #channel restricted {ON|OFF}
When restricted is set, this will kick, and ban, users who would not normally be allowed with Channel Operator status. This is set with negative access on the access list for users using that instead of the xOP list.

/cs set #channel secure {ON|OFF}
Secure is a way to secure the channel so that only users who have identified their nicknames will be allowed the level of status determined by the access list.

/cs set #channel secureops {ON|OFF}
When this option is enabled, this will not allow anyone to have channel operator status unless they are on the user access list. Similar to the SECURE option, only that it will prevent users from gaining Operator status.

/cs set #channel securefounder {ON|OFF}
If SECUREFOUNDER is on, this will limit some commands only to the true founder of the channel, not those who may be identified to the channel. Meaning, only the true founder can drop the channel, change the founder and successor, and change the password.

/cs set #channel signkick {ON|OFF}
SIGNKICK basically shows who kicked the user if they use the KICK command through ChanServ. There is no real purpose as to whether or not this is on, as it only shows who kicked the user.

/cs set #channel topiclock {ON|OFF}
When this is on, this will lock the topic to the channel and it can’t be changed by anyone, not even the founder. You would have to turn this option off to change the topic.

/cs set #channel xop {ON|OFF}
The xOP system gives users privileges through the SOP/AOP/HOP/VOP system to give users access. However, it is not recommended to use this system, but rather the ACCESS system to give better control over your users. If you have previously used the ACCESS system, then switching to the xOP system may cause problems for users. If you modified the ACCESS system, they will be switched back to default values if you switch to xOP. However, if you switch to ACCESS from xOP, then there should be no problems.

More to come later one. ^_~