|
|
ChanServ gives normal users the ability to keep hold of a channel, without the need for a bot. Unlike other IRC networks, channel takeovers are virtually impossible, when they are registered. Registration is a quick and painless process. Once registered, the founder can maintain complete and total control of the channel. ChanServ will stop monitoring a channel if no Op enters the channel for 20 days or the founder's nick expires. For more information on a command /msg ChanServ help [command] Core Commands: REGISTER - Register a channel SET - Change various channel configuration settings SOP - Maintain SuperOp channel operator list AOP - Maintain AutoOp channel operator list AKICK - Maintain the channel AutoKick banned user list DROP - Drop a registered channel Other Commands: IDENTIFY ACCESS SOP DEOP INFO INVITE MKICK MDEOP UNBAN COUNT WHYUsage - REGISTER {channel} {password} {description} When you register a channel with ChanServ, you don't need to worry about takeovers, or bots to keep a list of Ops. ChanServ does all of this and more. The founder is the person who does the registering. Make up a password to register with. The password is used so that only the founder can completely control the channel. The description is only used when a user asks ChanServ for information on a channel, and you make this up also. *** PLEASE NOTE: Also, PLEASE memorize your password, write it down somewhere, but PLEASE remember it! You will need it later on. Also, all passwords are case-sensative! Examples: /msg ChanServ register #Home anyGOODpasswd General Chat! /msg ChanServ register #WD NeXTStep White Dragon Command - SET {channel} [command] [value] Allows you to change your channel settings. These affect a registered channel's status and operation. Only the channel founder can use the SET commands. For more information on a command /msg ChanServ help SET [command] Core SET Commands: FOUNDER - Allows you to change the channel founder PASSWD - Lets you change the channel founder password DESC - Modify the channel's description MLOCK - Locks the channel to certain modes OPGUARD - More militant channel operator protection KEEPTOPIC - Maintain the topic when no one is on the channel URL - Attaches a URL to the channel IDENT - Ops have to identify to NickServ before ChanServ ops them RESTRICT - Allow ops only into a channel Additional Commands: TOPICLOCK LEAVEOPS UNSECURE PRIVATE MEMO Usage - SOP {channel} ADD {nick or mask} SOP {channel} DEL {index number or mask} SOP {channel} LIST [search pattern] SOP {channel} WIPE Maintains the channel SuperOp list. All SOP commands are limited to the channel founder except the LIST command, which is available to all AutoOps or above. ADD adds a user to a channels SuperOp access list. DEL removes a user from a channel's SuperOp access list. LIST lists the SuperOp access list, with an index number. When LIST is used with a search pattern, only those entries to the SOp access list matching your search pattern will be shown to you. LIST will only display the first 100 entries. WIPE will totally clear the SOp list. CLEAN will remove any SOp entries whose nicks have expired (i think this is useless because ChanServ automaticaly clean the expired's nick from AOP or SOP). Examples:
Usage - SET {channel} FOUNDER Allows a channel's founder to be changed to suit different situations should they arise. This command sets the founder of a channel to the current user. You must use the ChanServ IDENTIFY command before using this command. Example: /msg ChanServ SET #Home FOUNDER This would make the person using this command the new founder of #Home. This person would need to use ChanServ's IDENTIFY command before using this command. Usage - SET {channel} PASSWD {password} Will change the password needed for founder access on a channel. You must use the IDENTIFY command to gain access. Example: /msg ChanServ SET #Home PASSWD ANewPassword Usage - SET {channel} DESC {description} Allows the founder to change the description of a channel. Example: /msg ChanServ SET #Home DESC my channel Usage - SET {channel} MLOCK [mode lock mask] Changes mode lock pattern for specified channel. Setting a lock mask of * will turn off all mode locking. Examples: /msg ChanServ SET #Home MLOCK +nt-ispklm /msg ChanServ SET #Home MLOCK +nt-ipklm /msg ChanServ SET #home MLOCK * The first example keeps modes nt ON and ispklm OFF. The second is the same, except mode s can be ON or OFF in the channel. The last example clears ALL previous mode locks on a channel. Usage - SET {channel} OPGUARD [ON|OFF] Turns on/off ops guarding on a channel. When ON, only AutoOps, SuperOps, and the channel founder will be allowed ops on the channel. Example: /msg ChanServ SET #Home OPGUARD ON Usage - SET {channel} KEEPTOPIC [ON|OFF] Turns "Sticky" topics for a channel on or off. If everybody in a certain channel leaves that channel, then the topic is normally lost. But with this option on, ChanServ will save the last topic and when the channel is recreated, it will set the topic to what it previously was, followed by the nick who previously set that topic. Example: /msg ChanServ SET #Home KEEPTOPIC ON Usage - SET {channel} URL {URL} Allows a URL (Uniform Resource Locator) to be shown in the channel's INFO listing. Usually indicates where more information on the channel may be found. Examples: /msg ChanServ SET #Home URL http://www.homeclub.cjb.net/ /msg ChanServ SET #Home URL mailto:Drakkaro@dalnet.com /msg ChanServ SET #Home URL The first example is setting the URL to a Web Site, the second to an email address. The final is used to clear any former URL setting. Usage - SET {channel} IDENT [ON|OFF] This command makes it harder for anyone to use someone elses nick to gain ops in your channel. If this option is on, then all ops have to identify to NickServ before ChanServ ops them. NickServ's Access Lists will have no effect on ops. Any AOp or SOp entries that don't use registered nicknames will also become useless. Example: /msg ChanServ SET #home IDENT ON Usage - SET {channel} RESTRICT [ON|OFF] This option will only allow ops into a channel. If someone who joins is not on the AOp/SOp list, they will be kickbanned when they enter the channel. Example: /msg ChanServ SET #Home RESTRICT ON Usage - SET {channel} TOPICLOCK [FOUNDER|SOP|OFF] Sets the "topic lock" option for a channel. When on, only the founder or SuperOps (depending on the option> are able to change the topic. This setting also performs the function of the KEEPTOPIC command. Example: /msg ChanServ SET #Home TOPICLOCK SOP Usage - SET {channel} LEAVEOPS [ON|OFF] If set ON, this setting will prevent services from de-opping the first user that joins an empty channel. If set OFF (default), the first user to join an empty channel (that is not an AOp/SOp/Founder) will be de-opped. Example: /msg ChanServ SET #Home LEAVEOPS ON Usage - SET {channel} UNSECURE [ON|OFF] Will make a channel a little less secure than normal. When on, you need only be in the founders nick access list to make founder level changes; you won't need to identify. *** NOTE: This setting can cause problems if you do not have a secure NickServ Access List. This setting is strongly discouraged. Example: /msg ChanServ SET #Home UNSECURE ON Usage - SET {channel} PRIVATE [ON|OFF] When this option is ON, only those who know about the channel will have access to it. An MLOCK of +p will be set. Example: /msg ChanServ SET #Home PRIVATE ON Usage - SET {channel} MEMO [NONE|AOP|SOP|FOUNDER] Use this command to limit who can send channel memos. When NONE, no-one can send channel memos. When AOP, only AOps and above can send channel memos (this is the default setting). When SOP, only SOps and the founder can send channel memos. When FOUNDER, only the Channel Founder can send channel memos. Example: /msg ChanServ SET #Home MEMO AOP
|
|
|
|
|
|
|
|
|
|
Back to Dalnet Return Home |
|
|