How to use ChanServ

We work hard to make things easy for you. We want you to be safe and have fun. So we will come up with some basic guides in how to best use our network so it is fun and safe for you. In this guide we will talk about ChanServ, a manager helping users to manage their channels in a highly customizable way. ChanServ keeps a list of privileged and banned users for each channel and it thus allows for access control. It also overcome all takeover problems thanks to op/unban/invite functions, as well as a function of mass deop and mass kick.

After you've registered your nickname, you can use it to register a channel through ChanServ.

In order to register a channel, you naturally have to be Op(erator) of this channel, and the channel mustn't be already registered or currently used by others.

/join #test

-:- megabug [~megabug@1e79b4c9.27ea28c2.fastres.net] has joined #test
-:- [Users(#test:1)]
[@megabug ]
-:- Channel #test was created at Sat Apr 27 02:21:49 2002

Now you are an operator of the #test channel, and since #test hasn't been registered yet, you can register it with the REGISTER command:

/msg ChanServ REGISTER #test mypassword Channel description

-ChanServ- Channel #test registered under your nickname: megabug
-ChanServ- Your channel password is mypassword - remember it for later use.

Your channel has been registered and the registering user has become channel founder. A founder can change access modality for her channel, can define a list of nicks enjoying particular privileges, etc.

Now let's try to exit and re-enter the channel.

/part #test
/join #test

-:- megabug [~megabug@1e79b4c9.27ea28c2.fastres.net] has joined #test
-:- [Users(#test:1)]
[@megabug ]
-:- mode #test [+nrt] by ChanServ
-:- Topic (#test): changed by ChanServ: (ChanServ)
-:- mode #test [+o megabug] by ChanServ
-:- Channel #test was created at Sat Apr 27 02:34:31 2002

as you can see, Chanserv has automatically opped you. Auto-Op is a very nice feature of ChanServ. A founder is opped by default every time she accesses her channel (also because she has the highest privileges in the channel). Furthermore, a founder can write a list of nicks which are automatically given operator status when they connect to the channel.

Actually a founder can keep three different privileges lists:

  • VOP (VOice People) - This list contains nicks which will automatically receive Voice modality when they access the channel.
  • AOP (Auto OP) - This list contains nicks which will automatically receive Op status when they access the channel.
  • SOP (Super OP) - People included in this list have the same privileges as AOPs, but can also use AutoKick and read or write messages in the channel memo.

These three lists use the same commands for adding/removing nicks, so a command for AOP list such as:

/msg ChanServ AOP #test LIST

has a corresponding line for VOP and SOP lists:

/msg ChanServ VOP #test LIST
/msg ChanServ SOP #test LIST

this applies to all commands described below.

The LIST command we have just seen shows the content of each list. Since the channel has just been created, the list is obviously empty.

-ChanServ- #test AOP list is empty.

If you want to add a nick to the list, use the ADD command:

/msg ChanServ AOP #test ADD baku

-ChanServ- baku added to #test AOP list.

/msg ChanServ AOP #test LIST

-ChanServ- AOP list for #test:
-ChanServ- Num Nick
-ChanServ- 1 baku

User baku has thus been added to the AOP list in the channel.

Similarly, you can delete this nick with the DEL command

/msg ChanServ AOP #test DEL baku

-ChanServ- baku deleted from #test AOP list.

These few commands help manage channel access. Only channel founders can modify these lists. It can also be useful to acquire channel privileges even if you connect to the IRC server with a different nick. To do this, you can use the IDENTIFY command:

/msg ChanServ IDENTIFY #test miapassword

-ChanServ- Password accepted - you now have founder-level access to #test.

In this case, even if you have not materially founded a channel, you can obtain founder privileges just by knowing the channel password; or you can give the channel password to trusted people who can help us manage the channel.

How to manage takeovers

Sometimes there can be difficulties with troublesome users joining your channels. Our network gives the channel owners and channel operators the ability to manage these issues without needing any intervention from the IRC Operators. Of course, if you have any questions or something you do not know how to handle, you can always come to #Help to talk to someone that may be able to do something to assist.

If you have founder privileges for a channel, you shouldn't worry much about takeovers, as you can use a recovery system even for extreme situations. The command you need, and which of course only founders can use, is the CLEAR command. This command has some options you can use depending on the situation:

/msg ChanServ CLEAR #test OPS

This command deops all #test users. It can be useful if someone takes over the channel by deopping everybody without kicking/banning them.

/msg ChanServ CLEAR #test BANS

If someone takes over the channel and then kicks and bans all users, you can remove the ban with this command. It must naturally be used after a CLEAR OPS so that the person taking over the channel cannot ban again soon after.

/msg ChanServ CLEAR #test MODES

This command removes all channel modes (in particular +k +i and +l). If someone sets an invite-only, a password-protected (+k) or a user-limit (+l) mode on your channel, you can reset the configuration with this command. For the reason above, you should of course make a CLEAR OPS before giving this command.

/msg ChanServ CLEAR #test USER

This command removes all users from the channel, in practice with a mass kick. It should be clearly avoided, but in some cases this is the easiest solution.

Once you get your channel under control, you can obtain operator status (if ChanServ hasn't given them automatically) by entering the command:

/msg ChanServ OP

After this, set things back up the way you want and you are back in control!