Irc Commands:
Chanserv - The Basics
Info
USAGE: /ChanServ INFO channelThis command is used to find out lots of information about a channel. It includes the founder's nick, the current channel mode lock, the last topic set (and who set it), the channel description, possibly a list of options (all of them except "Sticky" Topics are shown below), perhaps what Memo Level is set for the channel (if any), when the channel was registered and when the last opping (by ChanServ) occurred. INFO can be used by anyone on the network.
The only option not discussed in the Advanced ChanServ section is "Held." This means that the channel will not expire because it is a network channel; this option is not available to normal channels where users generally go. It is intended for channels the network uses to run itself.
Of the options, only three don't use the command of the exact same name to set those options on: SecuredOps is set using OPGUARD; "Sticky" Topics is set using KEEPTOPIC; and, Restricted is set using RESTRICT.
All of this information can be changed in one way or another. The date and times listed are managed by ChanServ and are not directly modifiable. The topic is set in the channel itself; the rest of the options are all changed using ChanServ SET commands.
EXAMPLE: /ChanServ Info #MyChannel
-ChanServ- Info for #MyChannel:
-ChanServ- Founder : Nick1 (userid@some.place.com)
-ChanServ- Mode Lock : +p-ikntm
-ChanServ- Last Topic : Some cool place to chat (Nick1)
-ChanServ- Description: General Chat Channel
-ChanServ- URL : http://www.myisp.net/nick1/main.html
-ChanServ- Options : Private, SecuredOps, LeaveOps, UnSecure, Restricted, Ident, Held, Topic Lock(S)
-ChanServ- Memo Level : AOP
-ChanServ- Registered : Wed 08/02/1998 10:04:51 GMT
-ChanServ- Last opping: Mon 08/02/1999 18:51:03 GMT
-ChanServ- *** End of Info ***
If you have a registered nick and you are an op in a channel that is not registered with ChanServ, you can found that channel. If you want to be a channel founder, you can (assuming your nick is registered already) check to see if the channel you want is already taken by someone else by using the ChanServ Info command described above. ChanServ will tell you if the channel is not registered. Then, you can join that channel. If you are the first one there, you will automatically remain an op in that channel (because you created it), and therefore you can register it with ChanServ before someone else does.
If you have met all of these requirements, you need to think up a secret password for your channel and some sort of a description. The password can be anything you want, is case-sensitive and shouldn't be anything anyone could equate with you in any way. The description is what your channel is about, basically. It can contain pretty much as many words as you can fit on the single command line with all the rest of the required words and still make it to the server (which is about 500 characters for the whole message - that's LOTS of words!).
EXAMPLE: /ChanServ REGISTER #MyChannel q59H39tF2bb Nick1's Wonderful New DALnet Channel - Come and see!
-ChanServ- The channel #MyChannel has been registered to you. Your
-ChanServ- password is q59H39tF2bb: You are responsible for remembering
-ChanServ- your password. To maintain your registration: 1) Do not share your
-ChanServ- password. 2) Do not let the founder's nick expire. 3) An operator
-ChanServ- must use the channel at least once every 20 days.
-ChanServ- For help with ChanServ: /ChanServ help or join #DALnetHelp
This command is used when you want to identify to ChanServ for the channel. This is necessary if you are not using your normal nick or possibly your normal machine and don't want to identify for the founder's nick. Using this command gives you full access to all the ChanServ commands for the channel.
EXAMPLE: /ChanServ IDENTIFY #MyChannel q59H39tF2bb
-ChanServ- Password accepted for #MyChannel.
This command is used to check what level of access a person has on a channel (use is limited to AOPs and above). There are 7 levels. (Level 1 is unused; it was going to be VOp - Auto Voiced, but was removed.)
Level Meaning
5 Founder - Identified to ChanServ for the channel. 4 Founder - Identified to NickServ for the founder's nick. 3 Founder - Matches a mask in the founder's nick. 2 SOP - Super Operator. 1 AOP - Auto Operator. 0 Normal user. -1 AKicked user. EXAMPLE: /ChanServ ACCESS #MyChannel Nick1
-ChanServ- Nick1 ACC #MyChannel 5 (Founder)
This command tells an AOP (or higher) why someone else in that channel was opped, assuming ChanServ did it. This is handy when someone joins your channel and is opped by ChanServ but you have no idea why.
EXAMPLE: /ChanServ WHY #MyChannel Nick1
-ChanServ- Nick1 has FOUNDER access to #MyChannel. Reason: Identification to the founder's nickname.
This command is Founder or SOp only. It unbans the entire ban list for the specified channel.
EXAMPLE: /ChanServ CLEARBANS #MyChannel
-ChanServ- All bans on #MyChannel have been cleared.
If you are an AOP or higher on a channel, you can unban yourself on that channel through ChanServ using this command. You can also unban a particular ban using the banmask. If you are an SOP or higher on a channel, you can unban all bans at once using the * parameter instead no parameter.
This is the command you need to memorize for when people kick you out of your channel and ban you.
EXAMPLE: /ChanServ UNBAN #MyChannel
-ChanServ- Any bans against you on #MyChannel have been cleared.EXAMPLE: /ChanServ UNBAN #MyChannel Nick1
-ChanServ- Any bans against Nick1 on #MyChannel have been cleared.EXAMPLE: /ChanServ UNBAN #MyChannel Nick1!*userid@host.domain
-ChanServ- Any bans matching Nick1!*userid@host.domain on #MyChannel have been cleared.EXAMPLE: (Founder/SOp only) /ChanServ UNBAN #MyChannel *
-ChanServ- All bans on #MyChannel have been cleared.
If the channel you are an AOP (or higher) is set Invite Only (channel mode +i), you can gain admission to the channel through this command. There are no parameters, so you may not invite someone else using ChanServ, only yourself.
NOTE: You cannot invite yourself through ChanServ to a channel with the channel option PRIVATE set ON.
EXAMPLE: /ChanServ INVITE #MyChannel
*** ChanServ (service@dal.net)
invites you to join #Hammer
This is the first (lowest) real level of access to a channel. It grants you access to view the other ops on the channel (using AOP or SOP List). It grants you the ability to use ChanServ to op you if you are not currently opped. Therefore, you can always kick and ban people from your channel if they displease you.
If TopicLock is not set, an AOP can change the topic. If Memo is set to AOP, an AOP can send a channel memo (/memoserv send #channel).
These are your normal ops in your channel.
This command is used to add a new AOP to the channel. If you add them by nick, then you have to keep watch on the list for any nicks that go unregistered (their address out to the right side of their nick disappears). If you add them by mask, then anyone who matches that mask is an AOP. (If you have IDENT set ON for this channel, then no one who is added by mask will get opped by ChanServ - you cannot identify for an address mask.)
EXAMPLE: /ChanServ AOP #MyChannel ADD Nick2
-ChanServ- Nick2 has been
successfully added to #MyChannel's AOp list.
EXAMPLE: /ChanServ AOP #MyChannel ADD *!*userid@*.myisp.net
-ChanServ- *!*userid@*.myisp.net has been successfully added to #MyChannel's AOp list.
This command removes an AOP from the AOP list. This usually happens when they become an SOP, if their nick becomes unregistered or if they have warranted having their AOPs removed.
EXAMPLE: /ChanServ AOP #MyChannel DEL *!*userid@*.myisp.net
-ChanServ-
*!*userid@*.myisp.net has been successfully removed from
#MyChannel's AOp list.
EXAMPLE: /ChanServ AOP #MyChannel DEL 1
-ChanServ- Nick2 has been successfully removed from #MyChannel's AOp list.
Use this command to see who is on the AOP list.
EXAMPLE: /ChanServ AOP #MyChannel LIST
-ChanServ- AOp list for
#MyChannel
-ChanServ- 1 - *!*userid@*.myisp.net
-ChanServ- 2 -
Nick2 (~userid@ppp-465.myisp.net)
-ChanServ- End of
list
Use this command if your AOP list has gotten unmanagable, or if you just want to start it from scratch. This frequently happens in larger channels where the AOP list gets very large and many of the AOPs no longer come to the channel. Instead of weeding through the list one nick at a time, it's frequently easier to just start from scratch, re-adding those who do show up and forgetting about those you won't miss.
NOTE: You can wipe your AOP list even if there are no entries without an error.
EXAMPLE: /ChanServ AOP #MyChannel WIPE
-ChanServ- The AOp list for
#MyChannel has been wiped.
The next step up the chain of command from AOP is SOP. These are your especially trusted operators. They have a lot more "power" on the channel.
They can add or delete more AOPs to your channel in your place. They can add AKicks to permanently remove problem users (until they delete the AKick). If the channel is set TopicLock SOP, they can change the topic but AOPs cannot. If the Memo Level of the channel is set to SOP, they can send two kinds of channel memos: /memoserv send #channel message and /memoserv sendsop #channel message (the second only sends memos to the SOPs and the Founder).
This is the command used to add a Super Operator to your channel. However, while this might be a promotion from AOP, it doesn't remove their AOPs from the AOP list automatically. You have to do this yourself.
EXAMPLE: /ChanServ SOP #MyChannel ADD Nick2
-ChanServ- Nick2 has been
successfully added to #MyChannel's SOp list.
EXAMPLE: /ChanServ SOP #MyChannel ADD *!*userid@*.myisp.net
-ChanServ- *!*userid@*.myisp.net has been successfully added to #MyChannel's SOp list.
This command removes an AOP from the AOP list. This usually happens if their nick becomes unregistered or if they have warranted having their SOPs removed.
EXAMPLE: /ChanServ AOP #MyChannel DEL *!*userid@*.myisp.net
-ChanServ-
*!*userid@*.myisp.net has been successfully removed from
#MyChannel's AOp list.
EXAMPLE: /ChanServ AOP #MyChannel DEL 1
-ChanServ- Nick2 has been successfully removed from #MyChannel's SOp list.
Use this command to see who is on the SOP list.
EXAMPLE: /ChanServ SOP #MyChannel LIST
-ChanServ- SOp list for
#MyChannel
-ChanServ- 1 - *!*userid@*.myisp.net
-ChanServ- 2 -
Nick2 (~userid@ppp-465.myisp.net)
-ChanServ- End of list
Use this command if your SOP list has gotten unmanagable, or if you just want to start it from scratch. This frequently happens in larger channels where the SOP list gets very large and many of the SOPs no longer come to the channel. Instead of weeding through the list one nick at a time, it's frequently easier to just start from scratch, re-adding those who do show up and forgetting about those you won't miss.
NOTE: You can wipe your SOP list even if there are no entries without an error.
EXAMPLE: /ChanServ SOP #MyChannel WIPE
-ChanServ- The SOp list for
#MyChannel has been wiped.
AKicks are bans that you set in ChanServ's memory. When it sees someone matching an AKickaddress mask join your channel, it bans them and then kicks them from the channel. If you are looking through a channel's banlist, you can tell which ones are AKicks: ChanServ set the ban.
Only the SOPs of that channel and the channel founder may modify the channel's AKick list.
NOTE: AKick evasion can be grounds for being removed from the network.
Use this command to add a problem user to the AKick list to have ChanServ ban him and kick him from the channel.
Although it is possible to add an AKick by nick, doing so is very questionable; it's very easy to avoid such an akick. Also, if the nick has set NoOp on (currently), they can't be added to an AKick list. (This problem will disappear with the bug.)
EXAMPLE: /ChanServ AKICK #MyChannel ADD *!*userid@*.myisp.net
-ChanServ- *!*userid@*.myisp.net has been successfully added to #MyChannel's AKick list.
When you can no longer remember why the mask was placed in the AKick list, or if the problem has been resolved, you can remove the AKick using this command.
EXAMPLE: /ChanServ AKICK #MyChannel DEL *!*userid@*.myisp.net
-ChanServ-
*!*userid@*.myisp.net has been successfully removed from
#MyChannel's AKick list.
EXAMPLE: /ChanServ AKICK #MyChannel DEL 1
-ChanServ- Nick2 has been successfully removed from #MyChannel's AKick list.
This command is used to view the current AKick list.
EXAMPLE: /ChanServ AKICK #MyChannel LIST
-ChanServ- AKick list for
#MyChannel
-ChanServ- 1 - *!*userid@*.myisp.net
-ChanServ- End
of list
If your entire AKick list is out of date, or if one of your SOPs has gone suddenly schizophrenic and added lots of AKicks, it's frequently easier to use this command to just wipe the AKick list and start again. Occasionally, it's a good idea to do this anyway, since many of your problem users have long since given up trying to come to a channel they can't get in.
NOTE: You can wipe your AKICK list even if there are no entries without an error.
EXAMPLE: /ChanServ AKICK #MyChannel WIPE
-ChanServ- The AKick list for #MyChannel has been wiped.