The SorceryNet website would like to use cookies to improve your experience on our website. This notice is in accordance with the EU Cookie Directive, some cookies essential for the operation of this site may have already been set, please configure your browser to block / delete them if you feel it necessary for your privacy.

EU Cookie Directive Module Information
FAQ's SorceryNet IRC Chat Network - irc.sorcery.net http://www.sorcery.net/index.php 2017-12-17T10:10:50Z Joomla! 1.5 - Open Source Content Management Proxy Scanning 2012-09-30T09:52:10Z 2012-09-30T09:52:10Z http://www.sorcery.net/index.php?option=com_content&view=article&id=259:proxy-scanning&catid=105:faqs&Itemid=78 SorceryNet jc@sorcery.net <p><strong>What is a proxy?</strong></p> <p> </p> <p>A proxy is a piece of software that allows a user to access internet through a different computer (taking on the IP adress of this computer). This can allow access to the internet from networks which do not have a direct internet connection.</p> <p> </p> <p><strong>So why aren't they allowed?</strong></p> <p>We do not have a problem with correctly configured proxies, they are sometimes the only way for someone to gain internet access. However when a proxy is misconfigured to allow access to anyone on the internet (often called an open proxy), it can be used by anyone to connect through your system!</p> <p>This type of misconfigured proxy is an annoyance to the internet community as a whole because they allow abusers to hide behind someone else's IP address.</p> <p>This can be abused by spammers to anonymously send unsolicitied email ("spam"), to anonymously connect to (and possibily abuse) a chat network such as IRC or to access websites.</p> <p> </p> <p><strong>How does this affect IRC?</strong></p> <p>If you have been on IRC for any length of time, you have probably seen an attack using open proxies at least once. Hundreds of clients will enter a channel, often with random nick names, and start sending large amounts of coloured channel and CTCP messages. Commonly they will leave and join the channel rapidly in order to cause more disruption.</p> <p>Without completely locking up the channel, there is no effective way to stop the flood. Even if the channel is locked up, the floods of text can be sent to individual users and this will usually be enough to disconnect them.</p> <p>Most of these types of attacks use open proxies because open proxies are relatively easy to come by. Lists of them are readily available over the Internet. So this is why many IRC networks do not allow them. If you have to use a proxy, it should be configured correctly.</p> <p> </p> <p><strong>How can I fix it?</strong></p> <p>There are many different types of proxy software, in all cases you need to make sure that your proxy is configured to only allow the IP addresses within your own network to access it. A proxy that does not allow external access is considered secure.</p> <p>If you are not using any kind of proxy software then it is likely a trojan or virus has infected your system. We recommend you perform a full virus scan with up-to-date virus definitions. If you do not have a virus scanner try AVG Anti-Virus Free.</p> <p>If you are certain you do not have an open proxy or virus it is possible your IP address is on a list of previously comprimised machines (known as a DNS Blacklist). It is also possible your host will have automatically been submitted to one or more of these lists when you connected with an open proxy. If you cannot resolve this problem please contact us via kline@sorcery.net with your ban ID and we'll try and help you.</p> <p> </p> <p><strong>How do we check for them?</strong></p> <p>When you connect to SorceryNet we ask your system to connect to one of our servers which a correctly configured proxy would not allow. If your system responds OK to this request we know it's not configured properly and as a result the proxy will be blocked from connecting to SorceryNet. This is for your own protection too as a bad person could instruct the proxy to do things you wouldn't want to happen.</p> <p>We scan for proxies from the IP subnets below so you can be sure any connections from these IPs are safe and you should not worry if your router detects this as an attack, it's not, honest!</p> <p>1) 31.25.101.127 (open.proxy.monitor.sorcery.net)</p> <p>If you disagree with us checking for these security measures please disconnect from SorceryNet.</p> <p> </p> <p><strong>What is a proxy?</strong></p> <p> </p> <p>A proxy is a piece of software that allows a user to access internet through a different computer (taking on the IP adress of this computer). This can allow access to the internet from networks which do not have a direct internet connection.</p> <p> </p> <p><strong>So why aren't they allowed?</strong></p> <p>We do not have a problem with correctly configured proxies, they are sometimes the only way for someone to gain internet access. However when a proxy is misconfigured to allow access to anyone on the internet (often called an open proxy), it can be used by anyone to connect through your system!</p> <p>This type of misconfigured proxy is an annoyance to the internet community as a whole because they allow abusers to hide behind someone else's IP address.</p> <p>This can be abused by spammers to anonymously send unsolicitied email ("spam"), to anonymously connect to (and possibily abuse) a chat network such as IRC or to access websites.</p> <p> </p> <p><strong>How does this affect IRC?</strong></p> <p>If you have been on IRC for any length of time, you have probably seen an attack using open proxies at least once. Hundreds of clients will enter a channel, often with random nick names, and start sending large amounts of coloured channel and CTCP messages. Commonly they will leave and join the channel rapidly in order to cause more disruption.</p> <p>Without completely locking up the channel, there is no effective way to stop the flood. Even if the channel is locked up, the floods of text can be sent to individual users and this will usually be enough to disconnect them.</p> <p>Most of these types of attacks use open proxies because open proxies are relatively easy to come by. Lists of them are readily available over the Internet. So this is why many IRC networks do not allow them. If you have to use a proxy, it should be configured correctly.</p> <p> </p> <p><strong>How can I fix it?</strong></p> <p>There are many different types of proxy software, in all cases you need to make sure that your proxy is configured to only allow the IP addresses within your own network to access it. A proxy that does not allow external access is considered secure.</p> <p>If you are not using any kind of proxy software then it is likely a trojan or virus has infected your system. We recommend you perform a full virus scan with up-to-date virus definitions. If you do not have a virus scanner try AVG Anti-Virus Free.</p> <p>If you are certain you do not have an open proxy or virus it is possible your IP address is on a list of previously comprimised machines (known as a DNS Blacklist). It is also possible your host will have automatically been submitted to one or more of these lists when you connected with an open proxy. If you cannot resolve this problem please contact us via kline@sorcery.net with your ban ID and we'll try and help you.</p> <p> </p> <p><strong>How do we check for them?</strong></p> <p>When you connect to SorceryNet we ask your system to connect to one of our servers which a correctly configured proxy would not allow. If your system responds OK to this request we know it's not configured properly and as a result the proxy will be blocked from connecting to SorceryNet. This is for your own protection too as a bad person could instruct the proxy to do things you wouldn't want to happen.</p> <p>We scan for proxies from the IP subnets below so you can be sure any connections from these IPs are safe and you should not worry if your router detects this as an attack, it's not, honest!</p> <p>1) 31.25.101.127 (open.proxy.monitor.sorcery.net)</p> <p>If you disagree with us checking for these security measures please disconnect from SorceryNet.</p> <p> </p> BotServ 2010-09-05T10:45:54Z 2010-09-05T10:45:54Z http://www.sorcery.net/index.php?option=com_content&view=article&id=252:botserv&catid=105:faqs&Itemid=78 SorceryNet jc@sorcery.net BotServ Commands<br /><br />BotServ allows you to have a bot in your own channel.  BotServ was created for users that either cannot host, configure or spend the time needed to run their own bots.  On SorceryNet, we do permit friendly bots so this is merely a convenient bonus for those who would like to use this option instead.  The available commands for the bot are listed below.  On SorceryNet, you can always type in /BotServ help. <br /><br />* BOTLIST<br />Explanation:  This command lists all available bots on the network.<br />Syntax: /BotServ BOTLIST<br />Example:  /botserv botlist<br /><br />* ASSIGN<br />Explanation:  This command will assign a bot to a channel.  You can then configure the bot for the channel so that it fits your needs.<br />Syntax:  /BotServ ASSIGN channel botname<br />Example:  /botserv assign #blah Bot<br /><br />* UNASSIGN<br />Explanation:  This command removes a bot from your channel.  When you use this command the bot will not join the channel anymore.  However, the bot configuration for the channel will remain so you will always be able to reassign a bot later without having to reconfigure it entirely.<br />Syntax:  /BotServ UNASSIGN channel botname<br />Example:  /botserv unassign #blah Bot<br /><br />* INFO<br />Explanation:  This permits you to see BotServ information pertaining to a channel or a bot.  If the parameter is a channel, you will get information such as enabled kickers.  If the parameter is a nick, you will gain information about a bot (such as creation time or number of channels the bot is in).  <br />Syntax:  /BotServ INFO {channel | botnick}<br />Examples:  /botserv info #blah <br />/botserv info Bot<br /><br />* SET <br />Explanation:  Here are the BotServ SET commands to configure bot options.  Access is granted to this command by the user's Level SET.<br />Syntax: /msg BotServ SET (channel | bot) option parameters<br />DONTKICKOPS      To protect ops against bot kicks<br />DONTKICKVOICES   To protect voices against bot kicks<br />GREET            Enable the bot to give Greet messages from users who join the channel with high enough Access.<br />FANTASY          Enable fantaisist commands such as !op, !deop, !ban, !kick, !kb, !unban, !voice, !seen, etc.  <br />SYMBIOSIS        Allow the bot to act as a real bot.  The bot will do all acts that normally ChanServ would handle. <br /><br />* SET DONTKICKOPS<br />Explanation:  This will enable or disable OPs protection mode on a channel.  When it is enabled, ops will not be kicked by the bot, even if they do not match the NOKICK level.<br />Syntax:  /BotServ SET channel DONTKICKOPS {ON | OFF}<br />Example:  /botserv set #blah dontkickops on<br /><br />* SET DONTKICKVOICES<br />Explanation:  This command enables or disables Voices protection mode on a channel.  When it is ON, Voices will not be kicked by the bot, even if they do not match the NOKICK level.<br />Syntax:  /BotServ SET channel DONTKICKVOICES {ON | OFF}<br />Example:  /botserv set #blah dontkickvoices off<br /><br />* SET FANTASY<br />Explanation:  This enables or disables the Fantasy mode on a channel.  When it is enabled, users will be able to use the commands !op, !deop, !voice, !devoice, !kick, !kb, !unban and !seen on a channel.  Note that users wanting to use Fantaisist commands MUST have enough level for both the FANTASIA and another level depending on the command if required.  For example, to use !op, the user must have enough access for the OPDEOP Level. Many commands work simply by typing the command and the user's nick.  i.e. !op Snake will give ops to user Snake in the channel.  <br />Syntax /BotServ SET channel FANTASY {ON | OFF}<br />Example:  /botserv set #blah fantasy on<br />    <br />* SET GREET<br />Explanation:  This command enables or disables the GREET mode on a channel.  When enabled, the bot will display greet messages of the users who join the channel, provided they have enough access to the channel.  <br />Syntax:  /BotServ SET channel GREET {ON | OFF}<br />Example:  /botserv set #blah greet off<br /><br />* SET SYMBIOSiS<br />Explanation:  This enables or disables Symbiosis mode on a channel.  When enabled, the bot will do everything normally done by ChanServ in the channel such as MODES, KICKS and even the entry message. Access to this command is determined by Level set. <br />Syntax:  /BotServ SET channel SYMBIOSIS {ON | OFF}<br />Example:  /botserv set #blah symbiosis on<br /><br />* KICK <br />Explanation:  This command sets the Bot to autokick when an event happens or parameters are met. <br />Syntax:  /BotServ KICK channel option parameters<br />Options to use: <br />BOLDS         Sets if the bot kicks bold lettering<br />BADWORDS      Sets if the bot kicks bad words<br />CAPS          Sets if the bot kicks caps<br />COLORS        Sets if the bot kicks colors<br />FLOOD         Sets if the bot kicks flooding users<br />REPEAT        Sets if the bot kicks users who repeat themselves<br />REVERSES      Sets if the bot kicks reverses<br />UNDERLINES    Sets if the bot kicks underlines<br /><br />* KICK BOLDS<br />Explanation:  This activates the bolds kicker.  When enabled, this option tells the bot to kick users who use bold typing. (Control + B) 'ttb' is the number of times a user can be kicked before he/she gets banned.  Do not give ttb to disable the ban system once it has been activated.<br />Syntax:  /BotServ KICK channel BOLDS {ON | OFF} [ttb]<br />Example:  /botserv kick #blah bolds on <br /><br />* KICK COLORS<br />Explanation:  This sets the colors kicker on or off.  When enabled, this option tells the bot to kick users who use colors.  'ttb' is the number of times a user can be kicked before that user is banned.  Do not give ttb to disable the ban system once it has been activated.<br />Syntax:  /BotServ KICK channel COLORS {ON | OFF} [ttb]<br />Example:  /botserv kick #blah colors on 14 = The color kicker is on and after 14 times of kicking a user for colors, a ban will be set. (Control + K) <br /><br />* KICK REVERSES<br />Explanation:  This sets the reverses kicker on or off.  When enabled, this option tells the bot to kick users who use reverses (Control + R) to invert text.<br />Syntax:  /BotServ KICK channel REVERSES {ON | OFF} [ttb]<br />Example: /botserv kick #blah reverses on 5 = The bot reverses kicker has been activated and will ban after 5 kicks.<br /><br />* KICK UNDERLINES<br />Explanation:  This sets the underlines kicker on or off.  When enabled, this option tells the bot to kick users who use underlines. (Control + U)<br />Syntax:  /BotServ KICK channel REVERSES {ON | OFF} [ttb]<br />Example: /botserv kick #blah reverses on 5 = The bot reverses kicker has been activated and will ban after 5 kicks.<br /><br />* KICK CAPS<br />Explanation:  This sets the caps kicker on or off.  When enabled, this option tells the bot to kick users who are talking in CAPS.  The bot kicks only if <br /><br />there are at least the minimum caps number set and/or they constitute at least a certain percentage set of the total text line.  If not set manually by this command, the bot defaults to 10 characters and 25 percent of the message.  'ttb' is the number of times a user can be kicked before he/she will be banned.  Do not give ttb to disable the ban system once activated.<br />Syntax:  /BotServ KICK channel CAPS {ON | OFF} [ttb [min [percent]]]<br />Example:  /botserv kick #blah caps on 12 15 50 = The bot will now kick caps which constitute at least 15 characters and 50% of the entire message.  It will ban after the user has been kicked 12 times for the offense. <br /><br />* KICK FLOOD<br />Explanation:  This sets the flood kicker on or off.  When enabled, this option tells the bot to kick users who are flooding the channel using at least a set number of lines in a given number of seconds.  If the parameters are not given, the default is 6 lines in 10 seconds.  'ttb' is the number of times a user can be kicked before it is banned.  Do not give ttb to disable teh ban system once activated.<br />Syntax:  /BotServ KICK channel FLOOD {ON | OFF} [ttb [lines [seconds]]]<br />Example:  /botserv kick #blah flood on 12 15 15 = The bot will kick a flooder who does 15 lines in 15 seconds.  It will ban a user who has been kicked 12 times.  <br /><br />* KICK REPEAT <br />Explanation:  This command sets the repeat kicker on or off.  When enabled, this option tells the bot to kick users who are repeating themselves a certain number of times.  If no number is given, the default amount is three times.  'ttb' is the number of times a user can be kicked before he or she is banned.  Do not give ttb to disable the ban system once activated.<br />Syntax:  /BotServ KICK channel REPEAT {ON | OFF} [ttb [number]]<br />Example:  /botserv kick #blah on 4 5 = The bot is set to kick someone who repeats the same message 5 times.  If the user is kicked 4 times for the offense, the bot will ban the user on the 4th kick.  <br /><br />* KICK BADWORDS<br />Explanation:  This sets the bad words kicker on or off.  When enabled, this option tells the bot to kick users who say certain words on the channels.  You will be able to set bad words for your channel using the BADWORDS command.  You can read on to the next paragraph here or type /BotServ HELP BADWORDS for more information.  'ttb' is the number of times a user can be kicked before the user is banned.  Do not give ttb to disable the ban system once activated.<br />Syntax:  /BotServ KICK channel BADWORDS {ON | OFF} [ttb]<br />Example:  /bs kick #blah badwords on 5 = the bad words kicker has been activated and users saying 'bad words' that are set will be banned after 5 kicks.<br /><br />* BADWORDS<br />Explanation:  This command maintains the bad words list for the channel.  The bad words list determines which words are to be kicked when the bad words kicker is enabled.  For more information, see the command above this one or type /BotServ HELP KICK BADWORDS.  The BADWORDS ADD command will add the given word to the bad words list.  If SINGLE is specified, a kicker will be done only if a user says the word alone.  If START is specified, a kicker will be done if a user says a word that starts with the word.  I.e. if 'truck' is the word you set with SINGLE, any word with 'trucker' showing up in the first part will be banned.  'truckface' will therefore be kicked.  If you use END, a kick will be done if the user says a word that ends with the particular kickable word.  I.e. 'mothertrucker' would be banned if 'trucker' is put in and END is used.  If you do not specify anything, a kick will be used every time the word is said by a user.  This command can also be used to delete words off of the bad words list and you can view your list at any time.  You may also choose to clear the entire bad words list if you are the founder. <br />Syntax:  /BotServ BADWORDS channel ADD word [SINGLE | START | END]<br />Example:  /botserv #blah add truck single = If used as a stand-alone word, anyone saying 'trucker' will be kicked.<br />Example:  /bs #blah add truck start = saying the word 'truck' at the start of a compound word will enable the person to be kicked. i.e. truckface.<br />Example:  /bs #blah add trucker end = using 'trucker' at the end of a compound word will enact the kicker.  i.e. mothertrucker.<br />Example:  /bs #blah add trucker = saying the word 'trucker' at anytime will activate the kicker.<br />Syntax:  /BotServ BADWORDS channel DEL {word | entry number | list of numbers}<br />Example:  /botserv badwords #blah del trucker = deletes 'trucker'<br />Example:  /botserv badwords #blah del 5 = this deletes the 5th bad word in the bad words list.<br />Syntax:  /BotServ BADWORDS channel LIST [mask | list]<br />Example:  /botserv badwords #blah list 2-5,7-9 = this will list the bad words entries number 2 through 5 and 7 through 9.  <br />Syntax:  /BotServ channel CLEAR<br />Example:  /bs #blah clear<br /><br />* SAY<br />Explanation:  This makes the bot say the given text on the given channel.  The bot must be in the channel to say the text.  <br />Syntax:  /BotServ SAY channel text<br />Example:  /botserv say #blah Hey how's it going? = The bot will say to the channel 'Hey, how's it going?'<br /><br />* ACT<br />Explanation:  This makes the bot do the equivalent of a "/me" command, putting a sentence into 'action', which will be posted to the indicated channel.  The bot must be in the channel that you wish it to speak in.<br />Syntax:  /BotServ ACT channel text<br />Example:  /botserv act #blah ran to the store = The bot, named bot in this case, will then post '* @Bot ran to the store <br /> BotServ Commands<br /><br />BotServ allows you to have a bot in your own channel.  BotServ was created for users that either cannot host, configure or spend the time needed to run their own bots.  On SorceryNet, we do permit friendly bots so this is merely a convenient bonus for those who would like to use this option instead.  The available commands for the bot are listed below.  On SorceryNet, you can always type in /BotServ help. <br /><br />* BOTLIST<br />Explanation:  This command lists all available bots on the network.<br />Syntax: /BotServ BOTLIST<br />Example:  /botserv botlist<br /><br />* ASSIGN<br />Explanation:  This command will assign a bot to a channel.  You can then configure the bot for the channel so that it fits your needs.<br />Syntax:  /BotServ ASSIGN channel botname<br />Example:  /botserv assign #blah Bot<br /><br />* UNASSIGN<br />Explanation:  This command removes a bot from your channel.  When you use this command the bot will not join the channel anymore.  However, the bot configuration for the channel will remain so you will always be able to reassign a bot later without having to reconfigure it entirely.<br />Syntax:  /BotServ UNASSIGN channel botname<br />Example:  /botserv unassign #blah Bot<br /><br />* INFO<br />Explanation:  This permits you to see BotServ information pertaining to a channel or a bot.  If the parameter is a channel, you will get information such as enabled kickers.  If the parameter is a nick, you will gain information about a bot (such as creation time or number of channels the bot is in).  <br />Syntax:  /BotServ INFO {channel | botnick}<br />Examples:  /botserv info #blah <br />/botserv info Bot<br /><br />* SET <br />Explanation:  Here are the BotServ SET commands to configure bot options.  Access is granted to this command by the user's Level SET.<br />Syntax: /msg BotServ SET (channel | bot) option parameters<br />DONTKICKOPS      To protect ops against bot kicks<br />DONTKICKVOICES   To protect voices against bot kicks<br />GREET            Enable the bot to give Greet messages from users who join the channel with high enough Access.<br />FANTASY          Enable fantaisist commands such as !op, !deop, !ban, !kick, !kb, !unban, !voice, !seen, etc.  <br />SYMBIOSIS        Allow the bot to act as a real bot.  The bot will do all acts that normally ChanServ would handle. <br /><br />* SET DONTKICKOPS<br />Explanation:  This will enable or disable OPs protection mode on a channel.  When it is enabled, ops will not be kicked by the bot, even if they do not match the NOKICK level.<br />Syntax:  /BotServ SET channel DONTKICKOPS {ON | OFF}<br />Example:  /botserv set #blah dontkickops on<br /><br />* SET DONTKICKVOICES<br />Explanation:  This command enables or disables Voices protection mode on a channel.  When it is ON, Voices will not be kicked by the bot, even if they do not match the NOKICK level.<br />Syntax:  /BotServ SET channel DONTKICKVOICES {ON | OFF}<br />Example:  /botserv set #blah dontkickvoices off<br /><br />* SET FANTASY<br />Explanation:  This enables or disables the Fantasy mode on a channel.  When it is enabled, users will be able to use the commands !op, !deop, !voice, !devoice, !kick, !kb, !unban and !seen on a channel.  Note that users wanting to use Fantaisist commands MUST have enough level for both the FANTASIA and another level depending on the command if required.  For example, to use !op, the user must have enough access for the OPDEOP Level. Many commands work simply by typing the command and the user's nick.  i.e. !op Snake will give ops to user Snake in the channel.  <br />Syntax /BotServ SET channel FANTASY {ON | OFF}<br />Example:  /botserv set #blah fantasy on<br />    <br />* SET GREET<br />Explanation:  This command enables or disables the GREET mode on a channel.  When enabled, the bot will display greet messages of the users who join the channel, provided they have enough access to the channel.  <br />Syntax:  /BotServ SET channel GREET {ON | OFF}<br />Example:  /botserv set #blah greet off<br /><br />* SET SYMBIOSiS<br />Explanation:  This enables or disables Symbiosis mode on a channel.  When enabled, the bot will do everything normally done by ChanServ in the channel such as MODES, KICKS and even the entry message. Access to this command is determined by Level set. <br />Syntax:  /BotServ SET channel SYMBIOSIS {ON | OFF}<br />Example:  /botserv set #blah symbiosis on<br /><br />* KICK <br />Explanation:  This command sets the Bot to autokick when an event happens or parameters are met. <br />Syntax:  /BotServ KICK channel option parameters<br />Options to use: <br />BOLDS         Sets if the bot kicks bold lettering<br />BADWORDS      Sets if the bot kicks bad words<br />CAPS          Sets if the bot kicks caps<br />COLORS        Sets if the bot kicks colors<br />FLOOD         Sets if the bot kicks flooding users<br />REPEAT        Sets if the bot kicks users who repeat themselves<br />REVERSES      Sets if the bot kicks reverses<br />UNDERLINES    Sets if the bot kicks underlines<br /><br />* KICK BOLDS<br />Explanation:  This activates the bolds kicker.  When enabled, this option tells the bot to kick users who use bold typing. (Control + B) 'ttb' is the number of times a user can be kicked before he/she gets banned.  Do not give ttb to disable the ban system once it has been activated.<br />Syntax:  /BotServ KICK channel BOLDS {ON | OFF} [ttb]<br />Example:  /botserv kick #blah bolds on <br /><br />* KICK COLORS<br />Explanation:  This sets the colors kicker on or off.  When enabled, this option tells the bot to kick users who use colors.  'ttb' is the number of times a user can be kicked before that user is banned.  Do not give ttb to disable the ban system once it has been activated.<br />Syntax:  /BotServ KICK channel COLORS {ON | OFF} [ttb]<br />Example:  /botserv kick #blah colors on 14 = The color kicker is on and after 14 times of kicking a user for colors, a ban will be set. (Control + K) <br /><br />* KICK REVERSES<br />Explanation:  This sets the reverses kicker on or off.  When enabled, this option tells the bot to kick users who use reverses (Control + R) to invert text.<br />Syntax:  /BotServ KICK channel REVERSES {ON | OFF} [ttb]<br />Example: /botserv kick #blah reverses on 5 = The bot reverses kicker has been activated and will ban after 5 kicks.<br /><br />* KICK UNDERLINES<br />Explanation:  This sets the underlines kicker on or off.  When enabled, this option tells the bot to kick users who use underlines. (Control + U)<br />Syntax:  /BotServ KICK channel REVERSES {ON | OFF} [ttb]<br />Example: /botserv kick #blah reverses on 5 = The bot reverses kicker has been activated and will ban after 5 kicks.<br /><br />* KICK CAPS<br />Explanation:  This sets the caps kicker on or off.  When enabled, this option tells the bot to kick users who are talking in CAPS.  The bot kicks only if <br /><br />there are at least the minimum caps number set and/or they constitute at least a certain percentage set of the total text line.  If not set manually by this command, the bot defaults to 10 characters and 25 percent of the message.  'ttb' is the number of times a user can be kicked before he/she will be banned.  Do not give ttb to disable the ban system once activated.<br />Syntax:  /BotServ KICK channel CAPS {ON | OFF} [ttb [min [percent]]]<br />Example:  /botserv kick #blah caps on 12 15 50 = The bot will now kick caps which constitute at least 15 characters and 50% of the entire message.  It will ban after the user has been kicked 12 times for the offense. <br /><br />* KICK FLOOD<br />Explanation:  This sets the flood kicker on or off.  When enabled, this option tells the bot to kick users who are flooding the channel using at least a set number of lines in a given number of seconds.  If the parameters are not given, the default is 6 lines in 10 seconds.  'ttb' is the number of times a user can be kicked before it is banned.  Do not give ttb to disable teh ban system once activated.<br />Syntax:  /BotServ KICK channel FLOOD {ON | OFF} [ttb [lines [seconds]]]<br />Example:  /botserv kick #blah flood on 12 15 15 = The bot will kick a flooder who does 15 lines in 15 seconds.  It will ban a user who has been kicked 12 times.  <br /><br />* KICK REPEAT <br />Explanation:  This command sets the repeat kicker on or off.  When enabled, this option tells the bot to kick users who are repeating themselves a certain number of times.  If no number is given, the default amount is three times.  'ttb' is the number of times a user can be kicked before he or she is banned.  Do not give ttb to disable the ban system once activated.<br />Syntax:  /BotServ KICK channel REPEAT {ON | OFF} [ttb [number]]<br />Example:  /botserv kick #blah on 4 5 = The bot is set to kick someone who repeats the same message 5 times.  If the user is kicked 4 times for the offense, the bot will ban the user on the 4th kick.  <br /><br />* KICK BADWORDS<br />Explanation:  This sets the bad words kicker on or off.  When enabled, this option tells the bot to kick users who say certain words on the channels.  You will be able to set bad words for your channel using the BADWORDS command.  You can read on to the next paragraph here or type /BotServ HELP BADWORDS for more information.  'ttb' is the number of times a user can be kicked before the user is banned.  Do not give ttb to disable the ban system once activated.<br />Syntax:  /BotServ KICK channel BADWORDS {ON | OFF} [ttb]<br />Example:  /bs kick #blah badwords on 5 = the bad words kicker has been activated and users saying 'bad words' that are set will be banned after 5 kicks.<br /><br />* BADWORDS<br />Explanation:  This command maintains the bad words list for the channel.  The bad words list determines which words are to be kicked when the bad words kicker is enabled.  For more information, see the command above this one or type /BotServ HELP KICK BADWORDS.  The BADWORDS ADD command will add the given word to the bad words list.  If SINGLE is specified, a kicker will be done only if a user says the word alone.  If START is specified, a kicker will be done if a user says a word that starts with the word.  I.e. if 'truck' is the word you set with SINGLE, any word with 'trucker' showing up in the first part will be banned.  'truckface' will therefore be kicked.  If you use END, a kick will be done if the user says a word that ends with the particular kickable word.  I.e. 'mothertrucker' would be banned if 'trucker' is put in and END is used.  If you do not specify anything, a kick will be used every time the word is said by a user.  This command can also be used to delete words off of the bad words list and you can view your list at any time.  You may also choose to clear the entire bad words list if you are the founder. <br />Syntax:  /BotServ BADWORDS channel ADD word [SINGLE | START | END]<br />Example:  /botserv #blah add truck single = If used as a stand-alone word, anyone saying 'trucker' will be kicked.<br />Example:  /bs #blah add truck start = saying the word 'truck' at the start of a compound word will enable the person to be kicked. i.e. truckface.<br />Example:  /bs #blah add trucker end = using 'trucker' at the end of a compound word will enact the kicker.  i.e. mothertrucker.<br />Example:  /bs #blah add trucker = saying the word 'trucker' at anytime will activate the kicker.<br />Syntax:  /BotServ BADWORDS channel DEL {word | entry number | list of numbers}<br />Example:  /botserv badwords #blah del trucker = deletes 'trucker'<br />Example:  /botserv badwords #blah del 5 = this deletes the 5th bad word in the bad words list.<br />Syntax:  /BotServ BADWORDS channel LIST [mask | list]<br />Example:  /botserv badwords #blah list 2-5,7-9 = this will list the bad words entries number 2 through 5 and 7 through 9.  <br />Syntax:  /BotServ channel CLEAR<br />Example:  /bs #blah clear<br /><br />* SAY<br />Explanation:  This makes the bot say the given text on the given channel.  The bot must be in the channel to say the text.  <br />Syntax:  /BotServ SAY channel text<br />Example:  /botserv say #blah Hey how's it going? = The bot will say to the channel 'Hey, how's it going?'<br /><br />* ACT<br />Explanation:  This makes the bot do the equivalent of a "/me" command, putting a sentence into 'action', which will be posted to the indicated channel.  The bot must be in the channel that you wish it to speak in.<br />Syntax:  /BotServ ACT channel text<br />Example:  /botserv act #blah ran to the store = The bot, named bot in this case, will then post '* @Bot ran to the store <br /> User Modes 2010-09-05T10:44:34Z 2010-09-05T10:44:34Z http://www.sorcery.net/index.php?option=com_content&view=article&id=251:user-modes&catid=105:faqs&Itemid=78 SorceryNet jc@sorcery.net Modes:  USER MODES<br /><br />+D, deaf - /mode nick +/-D = Users with the +D umode set will not receive messages sent to channels. Joins, parts, topic changes, mode changes, etc are <br /><br />received as normal, as are private messages.<br /><br />+g, Caller ID - /mode nick +/-g = Users with the +g umode set will only receive private messages from users on a session-defined whitelist, defined by the <br /><br />/accept command. If a user who is not on the whitelist attempts to send a private message, the target user will receive a rate-limited notice saying that <br /><br />the user wishes to speak to him/her.<br /><br />+i, invisible - /mode nick +/-i = Invisible users do not show up in WHO and NAMES unless you are in a channel with them.<br /><br />+Q, disable forwarding - /mode nick +/-Q = This umode prevents you from being affected by any of the channel forwarding mechanisms. In any event where you <br /><br />would normally be forwarded, instead you will get the usual error message as if no forwarding was in effect.<br /><br />+R, reject messages from non-registered users - /mode nick +/-R = If a user has the +R umode set, then any users who are not identified will receive an <br /><br />error message if they attempt to send a private message or notice to the +R user.  Opers and accepted users (like in +g) are exempt. Unlike +g, the target <br /><br />user is not notified of failed messages.<br /><br />+w, receive wallops - /mode nick +/-w = Users with the +w umode set will receive WALLOPS messages sent by opers.<br /><br />ACCEPT - /ACCEPT [nick], [-nick], = Adds or removes users from your accept list for umode +g and +R. Users are automatically removed when they quit, split <br /><br />or change nick.<br /><br />/ACCEPT * - Lists all users on your accept list.= Support of this command is indicated by the CALLERID token in RPL_ISUPPORT (005); the optional parameter <br /><br />indicates the letter of the "only allow accept users to send private messages" umode, otherwise +g. In charybdis this is always +g.<br /><br />CNOTICE - /CNOTICE [nick] [channel] [:text] = Providing you are opped (+o) or voiced (+v) in channel, and nick is a member of channel, CNOTICE generates a <br /><br />NOTICE towards nick. CNOTICE bypasses any anti-spam measures in place. If you get "Targets changing too fast, message dropped", you should probably use <br /><br />this command, for example sending a notice to every user joining a certain channel.<br /><br />CPRIVMSG - /CPRIVMSG nick channel :text = Providing you are opped (+o) or voiced (+v) in channel, and nick is a member of channel, CPRIVMSG generates a <br /><br />PRIVMSG towards nick. CPRIVMSG bypasses any anti-spam measures in place. If you get "Targets changing too fast, message dropped", you should probably use <br /><br />this command.<br /><br />HELP - /HELP [topic] = Displays help information. topic can be INDEX, CREDITS, UMODE, CMODE, SNOMASK or a command name.<br /><br />KNOCK - /KNOCK [channel] - Requests an invite to the given channel. The channel must be locked somehow (+ikl), must not be +p and you may not be banned or <br /><br />quieted. Also, this command is rate limited.<br /><br />MONITOR - Server side notify list. This list contains nicks. When a user connects orquits with a listed nick or changes to or from a listed nick, you will <br /><br />get a notification<br /><br />/MONITOR + nick, ... - Adds nicks to your monitor list.<br /><br />/MONITOR - nick, ... - Removes nicks from your monitor list. No output is generated for this command.<br /><br />/MONITOR C - Clears your monitor list. No output is generated for this command.<br /><br />/MONITOR L - Lists all nicks on your monitor list.<br /><br />/MONITOR S - <br /> Modes:  USER MODES<br /><br />+D, deaf - /mode nick +/-D = Users with the +D umode set will not receive messages sent to channels. Joins, parts, topic changes, mode changes, etc are <br /><br />received as normal, as are private messages.<br /><br />+g, Caller ID - /mode nick +/-g = Users with the +g umode set will only receive private messages from users on a session-defined whitelist, defined by the <br /><br />/accept command. If a user who is not on the whitelist attempts to send a private message, the target user will receive a rate-limited notice saying that <br /><br />the user wishes to speak to him/her.<br /><br />+i, invisible - /mode nick +/-i = Invisible users do not show up in WHO and NAMES unless you are in a channel with them.<br /><br />+Q, disable forwarding - /mode nick +/-Q = This umode prevents you from being affected by any of the channel forwarding mechanisms. In any event where you <br /><br />would normally be forwarded, instead you will get the usual error message as if no forwarding was in effect.<br /><br />+R, reject messages from non-registered users - /mode nick +/-R = If a user has the +R umode set, then any users who are not identified will receive an <br /><br />error message if they attempt to send a private message or notice to the +R user.  Opers and accepted users (like in +g) are exempt. Unlike +g, the target <br /><br />user is not notified of failed messages.<br /><br />+w, receive wallops - /mode nick +/-w = Users with the +w umode set will receive WALLOPS messages sent by opers.<br /><br />ACCEPT - /ACCEPT [nick], [-nick], = Adds or removes users from your accept list for umode +g and +R. Users are automatically removed when they quit, split <br /><br />or change nick.<br /><br />/ACCEPT * - Lists all users on your accept list.= Support of this command is indicated by the CALLERID token in RPL_ISUPPORT (005); the optional parameter <br /><br />indicates the letter of the "only allow accept users to send private messages" umode, otherwise +g. In charybdis this is always +g.<br /><br />CNOTICE - /CNOTICE [nick] [channel] [:text] = Providing you are opped (+o) or voiced (+v) in channel, and nick is a member of channel, CNOTICE generates a <br /><br />NOTICE towards nick. CNOTICE bypasses any anti-spam measures in place. If you get "Targets changing too fast, message dropped", you should probably use <br /><br />this command, for example sending a notice to every user joining a certain channel.<br /><br />CPRIVMSG - /CPRIVMSG nick channel :text = Providing you are opped (+o) or voiced (+v) in channel, and nick is a member of channel, CPRIVMSG generates a <br /><br />PRIVMSG towards nick. CPRIVMSG bypasses any anti-spam measures in place. If you get "Targets changing too fast, message dropped", you should probably use <br /><br />this command.<br /><br />HELP - /HELP [topic] = Displays help information. topic can be INDEX, CREDITS, UMODE, CMODE, SNOMASK or a command name.<br /><br />KNOCK - /KNOCK [channel] - Requests an invite to the given channel. The channel must be locked somehow (+ikl), must not be +p and you may not be banned or <br /><br />quieted. Also, this command is rate limited.<br /><br />MONITOR - Server side notify list. This list contains nicks. When a user connects orquits with a listed nick or changes to or from a listed nick, you will <br /><br />get a notification<br /><br />/MONITOR + nick, ... - Adds nicks to your monitor list.<br /><br />/MONITOR - nick, ... - Removes nicks from your monitor list. No output is generated for this command.<br /><br />/MONITOR C - Clears your monitor list. No output is generated for this command.<br /><br />/MONITOR L - Lists all nicks on your monitor list.<br /><br />/MONITOR S - <br /> Channel Modes 2010-08-30T19:53:47Z 2010-08-30T19:53:47Z http://www.sorcery.net/index.php?option=com_content&view=article&id=249:chanmodes&catid=105:faqs&Itemid=78 SorceryNet jc@sorcery.net <pre>Mode Syntax and Description ------------------------------------------------------------------------------------------- b /MODE &lt;channel&gt; [+|-]b &lt;nickname!ident@hostname&gt; Allows (half-)operators to ban specified hostmasks/users from the channel. This will prevent the targetted user/mask from joining the channel. c /MODE &lt;channel&gt; [+|-]c Strips out all control codes (bold, underline, beeps,colour codes and ANSI escapes) out of messages. e /MODE &lt;channel&gt; [+|-]e &lt;nickname!ident@hostname&gt; This will grant an exception for the specified user/hostmask. When set, the user won't be blocked by mode b (ban). f /MODE &lt;channel&gt; [+|-]f &lt;channel&gt; If someone attempts to join but the channel is blocked due e.g. +i +r +l or +j, they will join the alternate channel destination instead. Forwards may only be set to +F channels or to one the founder/setter has ops in. g /mode &lt;channel&gt; [+|-]g allows anyone to use the Invite command on a channel. If unset, only ops are permitted to use it. If this is used with +i all channel members can influence who joins. h /mode &lt;channel&gt; [+|-]h &lt;nickname&gt; This gives level 4(HOP) halfop status temporarily to a user. This user can control users with a lower level and is able set modes and topics. i /mode &lt;channel&gt; [+|-]i When this mode is set, no client can join the channel unless he/she has an invex(+I) or are invited with the INVITE command. j /mode &lt;channel&gt; [+|-]j &lt;amount&gt;:&lt;seconds&gt; Only &lt;amount&gt; users may join in each period of &lt;seconds&gt; seconds. This slows down joins to the channel. k /mode &lt;channel&gt; [+|-]k &lt;key&gt; This mode requires a user to supply the key (a channel password set for each member to join with) in order to join the channel: /JOIN #channel key. l /mode &lt;channel&gt; [+|-]l &lt;limit&gt; Sets a number of members permitted in a channel and those who attempt to join afterward cannot enter. m /mode #channel [+|-]m Only those with +o, +h or +v can chat in the channel when this mode is activated. Users can still knock on the channel or change nicknames. n /mode #channel [+|-]n This mode prevents users from sending to the channel without being in it themselves. This is recommended and a default. o /MODE &lt;channel&gt; [+|-]o &lt;nickname&gt; This gives level 5(AOP) operator status temporarily to a user. This user can control users with a lower or equal level and is able set modes and topics. p /mode &lt;channel&gt; [+|-] The KNOCK command cannot be used on the channel to request an invite, and users will not be shown the channel in WHOIS replies unless they are on it. Unlike in traditional IRC, +p and +s can be set together. q /mode &lt;channel&gt; [+|-]q &lt;nickname!ident@hostname&gt; Like +b (ban), except that the user may still join the channel. The net effect is that they cannot knock on the channel, send to the channel or change their nick while on channel. r /mode &lt;channel&gt; [+|-]r This mode prevents unidentified or unregistered users from joining. It gives a message to others not registered of Cannot join channel (+r) s /mode &lt;channel&gt; [+|-]s This mode prevents the channel from appearing in the output of the LIST, WHO and WHOIS command by users who are not on it. t /mode &lt;channel&gt; [+/-t] This mode prevents users who are not channel operators or half-operator from changing the topic. v /mode &lt;channel&gt; [+|-]v &lt;nickname&gt; This gives level 3(VOP) voice status temporarily to a user. This user will be excempted from mode +m if set. z /mode &lt;channel&gt; [+|-]z If set the effects of +m are relaxed so that the person may send text so that all channel operators may see it. This is used for moderated debates. C /mode &lt;channel&gt; [+|-]C This mode blocks the sending of CTCP commands to whole channels. F /mode &lt;channel&gt; [+|-]F When this mode is set, anybody may set a forward from a channel they have ops in to this channel. Otherwise they have to have ops in this channel. I /mode &lt;channel&gt; [+|-]I &lt;nickname!ident@hostname&gt; If set +i on a channel, users with +I can enter without needing a personal invite. Q /mode &lt;channel&gt; [+|-]Q Channels with this mode set are not valid targets for forwarding. Any attempt to forward to this channel will be ignored, and the user will be handled as if the attempt was never made (by sending them the relevant error message). This does not affect the ability to set +f. S /mode &lt;channel&gt; [+|-]S Only users connected by an SSL connection are able to join this channel when set. The following modes are restricted to IRC Operators A /mode &lt;channel&gt; [+|-]A This mode will mark the channel as "Administrator" channel. L /mode &lt;channel&gt; [+|-]L Channels with this mode will be allowed larger banlists (by default, 500 instead of 50 entries for +b, +q, +e and +I together). O /mode &lt;channel&gt; [+|-]O This mode will mark the channel as "IRC Operator" channel. P /mode &lt;channel&gt; [+|-]P Channels with this mode (which is accessible only to network operators) set will not be destroyed when the last user left. This makes it less likely modes, bans and the topic will be lost and makes it harder to abuse network splits, but also causes more unwanted restoring of old modes, bans and topics after long splits.</pre> <pre>Mode Syntax and Description ------------------------------------------------------------------------------------------- b /MODE &lt;channel&gt; [+|-]b &lt;nickname!ident@hostname&gt; Allows (half-)operators to ban specified hostmasks/users from the channel. This will prevent the targetted user/mask from joining the channel. c /MODE &lt;channel&gt; [+|-]c Strips out all control codes (bold, underline, beeps,colour codes and ANSI escapes) out of messages. e /MODE &lt;channel&gt; [+|-]e &lt;nickname!ident@hostname&gt; This will grant an exception for the specified user/hostmask. When set, the user won't be blocked by mode b (ban). f /MODE &lt;channel&gt; [+|-]f &lt;channel&gt; If someone attempts to join but the channel is blocked due e.g. +i +r +l or +j, they will join the alternate channel destination instead. Forwards may only be set to +F channels or to one the founder/setter has ops in. g /mode &lt;channel&gt; [+|-]g allows anyone to use the Invite command on a channel. If unset, only ops are permitted to use it. If this is used with +i all channel members can influence who joins. h /mode &lt;channel&gt; [+|-]h &lt;nickname&gt; This gives level 4(HOP) halfop status temporarily to a user. This user can control users with a lower level and is able set modes and topics. i /mode &lt;channel&gt; [+|-]i When this mode is set, no client can join the channel unless he/she has an invex(+I) or are invited with the INVITE command. j /mode &lt;channel&gt; [+|-]j &lt;amount&gt;:&lt;seconds&gt; Only &lt;amount&gt; users may join in each period of &lt;seconds&gt; seconds. This slows down joins to the channel. k /mode &lt;channel&gt; [+|-]k &lt;key&gt; This mode requires a user to supply the key (a channel password set for each member to join with) in order to join the channel: /JOIN #channel key. l /mode &lt;channel&gt; [+|-]l &lt;limit&gt; Sets a number of members permitted in a channel and those who attempt to join afterward cannot enter. m /mode #channel [+|-]m Only those with +o, +h or +v can chat in the channel when this mode is activated. Users can still knock on the channel or change nicknames. n /mode #channel [+|-]n This mode prevents users from sending to the channel without being in it themselves. This is recommended and a default. o /MODE &lt;channel&gt; [+|-]o &lt;nickname&gt; This gives level 5(AOP) operator status temporarily to a user. This user can control users with a lower or equal level and is able set modes and topics. p /mode &lt;channel&gt; [+|-] The KNOCK command cannot be used on the channel to request an invite, and users will not be shown the channel in WHOIS replies unless they are on it. Unlike in traditional IRC, +p and +s can be set together. q /mode &lt;channel&gt; [+|-]q &lt;nickname!ident@hostname&gt; Like +b (ban), except that the user may still join the channel. The net effect is that they cannot knock on the channel, send to the channel or change their nick while on channel. r /mode &lt;channel&gt; [+|-]r This mode prevents unidentified or unregistered users from joining. It gives a message to others not registered of Cannot join channel (+r) s /mode &lt;channel&gt; [+|-]s This mode prevents the channel from appearing in the output of the LIST, WHO and WHOIS command by users who are not on it. t /mode &lt;channel&gt; [+/-t] This mode prevents users who are not channel operators or half-operator from changing the topic. v /mode &lt;channel&gt; [+|-]v &lt;nickname&gt; This gives level 3(VOP) voice status temporarily to a user. This user will be excempted from mode +m if set. z /mode &lt;channel&gt; [+|-]z If set the effects of +m are relaxed so that the person may send text so that all channel operators may see it. This is used for moderated debates. C /mode &lt;channel&gt; [+|-]C This mode blocks the sending of CTCP commands to whole channels. F /mode &lt;channel&gt; [+|-]F When this mode is set, anybody may set a forward from a channel they have ops in to this channel. Otherwise they have to have ops in this channel. I /mode &lt;channel&gt; [+|-]I &lt;nickname!ident@hostname&gt; If set +i on a channel, users with +I can enter without needing a personal invite. Q /mode &lt;channel&gt; [+|-]Q Channels with this mode set are not valid targets for forwarding. Any attempt to forward to this channel will be ignored, and the user will be handled as if the attempt was never made (by sending them the relevant error message). This does not affect the ability to set +f. S /mode &lt;channel&gt; [+|-]S Only users connected by an SSL connection are able to join this channel when set. The following modes are restricted to IRC Operators A /mode &lt;channel&gt; [+|-]A This mode will mark the channel as "Administrator" channel. L /mode &lt;channel&gt; [+|-]L Channels with this mode will be allowed larger banlists (by default, 500 instead of 50 entries for +b, +q, +e and +I together). O /mode &lt;channel&gt; [+|-]O This mode will mark the channel as "IRC Operator" channel. P /mode &lt;channel&gt; [+|-]P Channels with this mode (which is accessible only to network operators) set will not be destroyed when the last user left. This makes it less likely modes, bans and the topic will be lost and makes it harder to abuse network splits, but also causes more unwanted restoring of old modes, bans and topics after long splits.</pre> ChanServ 2010-08-30T19:52:19Z 2010-08-30T19:52:19Z http://www.sorcery.net/index.php?option=com_content&view=article&id=248:chanserv&catid=105:faqs&Itemid=78 SorceryNet jc@sorcery.net Chanserv Commands <br />ChanServ allows you to register, control and alter various aspects of channels.  It gives you the ability to customize a channel, ops privileges and more through the commands listed below, as well as providing a solid defense against malicious users who attempt thefts of channels, flooding, etc.  You can access help on IRC by typing in your status window '/chanserv help'.  All of the commands are listed here with more detail and solid examples.  For further aid, you are welcome to bring your inquiries to #sorcery where we will be glad to assist you. <br /><br /><br />* REGISTER<br />Explanation: This command registers a channel into the ChanServ database.  You must have a registered nick, be identified to it and be an op in a channel you would wish to register.  If you need assistance registering your nick, do the command: '/nickserv help register'.  Preferably, use a different password than the one you used to register your nick.  The description can be anything short that tells a bit about what the purpose of the channel is for.  When you register a channel, you become the Founder and as such, can change all of the channel settings and ChanServ automatically grants the Founder channel-operator privileges upon entering the room.  To grant functions to ops who will assist you in running the channel, see /ChanServ ACCESS. <br />Syntax: /ChanServ REGISTER #channel password description <br />Example:  /chanserv register #sorcery ExeCuto1 A room full of unusual people.<br /><br />* IDENTIFY<br />Explanation:  This command gives proof to ChanServ that you are the Founder of the given channel.  Many commands require you to use the Identify command prior to using them.  The password you use here is the same one that you registered the channel with. <br />Syntax:  /ChanServ identify #channel password <br />Example:  /chanserv identify #sorcery ExeCuto1<br />    <br />* LOGOUT<br />Explanation:  This command logs the selected nickname out; meaning that the user would have to re-identify him/herself to regain access.  If you are the Founder of the channel, you have the power to log out anyone from ChanServ.  No one else has this privilege and can only log out themselves.<br />Syntax:  /ChanServ LOGOUT channel nickname<br />Example:  /chanserv logout #orange Bloo<br /><br />* DROP <br />Explanation:  You can use this command to unregister a channel that you are the Founder of.  You must use the IDENTIFY command first.  Once a channel is dropped, it may be registered by the first op to the room, as it has become available.  On SorceryNet, you can do '/chanserv help set option' (replacing 'option' with one of the options below) to get an understanding of what these commands do.  You can also read on in this section for a more in depth look.<br />Syntax:  /ChanServ DROP channel<br />Example:  /chanserv drop #orange<br /><br />* SET<br />Explanation:  This allows the channel Founder to set various channel options.  <br />Syntax:  /ChanServ SET channel option parameters<br />Options:  <br />FOUNDER - Sets the Founder of a channel. <br />SUCCESSOR - Set a successor for a channel.<br />PASSWORD - Set the Founder password for the channel.<br />DESC - Set a channel description.<br />URL - Associate a URL with the channel.<br />EMAIL - Associate an E-mail address with the channel.<br />ENTRYMSG - Set a message to be sent to users when they enter the channel.<br />BANTYPE - Set how Services has bans on the channel<br />MLOCK - Lock channel modes on or off.<br />KEEPTOPIC - Retain a topic when the channel is not in use.<br />OPNOTICE - Send a notice when OP/DEOP commands are used.<br />PEACE - Regulate the use of critical commands.<br />PRIVATE - Hide the channel from the LIST command.<br />RESTRICTED - Restrict access to the channel.<br />SECURE - Activate ChanServ security features.<br />SECUREOPS - Provides stricter control of chanop status.<br />SECUREFOUNDER - Provides stricter control of channel Founder status.<br />SIGNKICK - Sign kicks that are done with the KICK command.<br />TOPICLOCK - The topic can only be changed with the TOPIC command.<br />XOP - Toggles the user privilege system<br /><br />* SET FOUNDER<br />Explanation:  This changes the Founder of a channel.  The new nickname to be set as Founder must be registered.<br />Syntax:  /ChanServ SET channel FOUNDER nick<br />Example:  /chanserv set #blah founder Pita<br /><br />* SET SUCCESSOR<br />Explanation:  This function allows a Founder to choose a successor for the channel.  If the Founder's nick expires or is dropped while the channel is still registered, the Successor will inherit the channel as the new Founder.  If, for some reason, the Successor has too many channels registered to him/her, the channel instead will be dropped.  The Successor must have a registered nick.  <br />Syntax:  /ChanServ set channel SUCCESSOR nick<br />Example:  /chanserv set #blah Luke<br /><br />* SET PASSWORD<br />Explanation:  This allows the Founder to change the password that is used to Identify as the Founder of the channel.  The Founder must Identify to the channel prior to using this command.<br />Syntax:  /ChanServ SET channel PASSWORD password<br />Example:  /chanserv set #zomg password 234lalarawr93<br /><br />* SET DESC<br />Explanation:  This command allows you to set up a description for the channel.  This will show up in LIST and INFO commands.<br />Syntax:  /ChanServ SET channel DESC description<br />Example:  /ChanServ SET #zomg desc a channel totally about whatever zomg. <br /><br />* SET URL <br />Explanation:  Allows you to associate a URL to the channel which will be displayed whenever someone requests information on the channel with the INFO command.  If you give no parameter, instead of providing a new URL, this will delete any current URL listed for the channel.<br />Syntax:  /ChanServ Set channel URL {url}<br />Examples:  /ChanServ set #bloom url http://www.lala.com = inserts the URL http://www.lala.com.<br />/chanserv set #bloom url = No URL set and if there was a former URL, it was deleted.<br /><br />* SET EMAIL<br />Explanation:  This allows you to set up an E-mail address that will be associated to the channel to be viewed whenever someone uses the INFO command.  If this command is used without inputting an address, no E-mail address will be posted.<br />Syntax:  /ChanServ SET channel EMAIL {address}<br />Examples:  /chanserv set #caramba bart@wherever.com = to add E-mail bart@wherever.com<br />/chanserv set #caramba = to remove E-mail.<br /><br />* SET ENTRYMSG<br />Explanation: This sets a message which will be sent via /notice to users when they enter the channel.  If no parameter (message) is given, this erases the entry message that would be sent upon entering the channel.<br />Syntax:  /ChanServ SET channel ENTRYMSG {message}<br />Examples:  /chanserv set #caramba entrymsg Welcome to #caramba! = to set the message "Welcome to #caramba!"<br />/chanserv set #caramba entrymsg = this removes the entry message.<br /><br />* SET BANTYPE<br />Explanation:  Sets the ban type that will be used by ChanServ whenever it needs to ban someone from your channel.  The bantype options are 0-3 and can be selected and then later altered if you wish.<br />0 = ban in the form *!user@host<br />1 = ban in the form *!*user@host<br />2 = ban in the form *!*@host<br />3 = ban in the form *!*user@*.domain<br />Syntax:  /ChanServ SET channel BANTYPE number<br />Example:  /chanserv set #banhammer 2 <br /><br />* SET KEEPTOPIC<br />Explanation:  This enables or disables the option of keeping a topic in the channel even after the last user leaves.  The topic is restored when the channel is next used.  <br />Syntax:  /ChanServ SET channel KEEPTOPIC {ON | OFF}<br />Example:  /chanserv set #banhammer keeptopic on<br /><br />* SET TOPICLOCK<br />Explanation:  This enables or disables the topic lock option for a channel.  When TOPICLOCK is set ON, ChanServ will not allow the channel topic to be changed via the /topic command.  <br />Syntax:  /ChanServ SET channel TOPICLOCK {ON | OFF}<br />Example:  /chanserv set #bruhaha topiclock on<br /><br />* SET MLOCK<br />Explanation:  MLOCK serves as a way to lock in channel mode preferences that with the /mode command, would be erased when the channel is emptied.  To see a list of channel modes, check out 'Channel Modes' in this FAQ section of the site.  ChanServ allows you to define whether you want certain channel modes to be on, off or free to be either on or off.  The SET MLOCK command mode parameter is constructed exactly the same way as a /MODE command.  Modes followed by a '+' are locked on.  Modes with a '-' are locked off.  Each use of this command will remove ALL modes previously locked in before, so copy in the modes you want to remain and want turned off each time.  <br />Syntax:  /ChanServ SET channel MLOCK +modes-modes<br />Examples:  /chanserv set #boogie mlock +nt-iklps = This forces modes 'n' and 't' on, while disabling modes 'i,k,l,p,s'.  <br />/chanserv set #channel mlock +knst-ilmp my-key = This forces modes 'k,n,s,t' to on and disables modes 'i,l,m'off.  It also forces the channel KEY to be "my-key".<br />/chanserv set #channel mlock + = This removes the mode lock so that all channel modes are free to be either on or off.  Ops can then add modes temporarily with the /MODE command.<br />Note:  If you set a mode-locked KEY, as shown in the second example above, you should also SET RESTRICTED ON (see SET RESTRICTED) or anyone entering the channel when it is empty will be able to see the KEY.<br /><br />* SET PEACE<br />Explanation:  This command activates or disables the 'peace' option for a channel.  When PEACE is set, a user will not be able to kick, ban or remove a channel status of a user that has a level superior or equal to his/hers via ChanServ commands.  <br />/Syntax:  /ChanServ SET channel PEACE {ON | OFF}<br />Example:  /chanserv set #rabbit-hole peace on<br /><br />* SET PRIVATE<br />Explanation:  This enables or disables the private option for a channel.  When PRIVATE is set ON, a search by /msg ChanServ LIST will not include the channel in any lists.  The /list command will also not place the channel in the over all list.<br />Syntax:  /ChanServ SET channel PRIVATE {ON | OFF}<br />Example:  /chanserv set #rabbit-hole private off<br /><br />* SET RESTRICTED<br />Explanation:  This enables or disables the restricted access option for a channel.  When restricted access is set on, users who are not on the Access List will instead be kicked and banned from the channel.  <br />Syntax:  /ChanServ SET channel RESTRICTED {ON | OFF}<br />Example:  /chanserv set #baba restricted on<br /><br />* SET SECURE<br />Explanation:  This enables or disables ChanServ's security features for a given channel.  When SECURE is set ON, only uers who have registered nicknames with ChanServ and Identified with their password will be given access (ops functions) to the channel as controlled by the Access List.<br />Syntax:  /ChanServ SET channel SECURE {ON | OFF}<br />Example:  /chanserv set #starseekers secure off<br /><br />* SET SECUREOPS<br />Explanation:  This enables or disables the Secure Ops option for a channel.  If this is set on, only users who are on the userlist will gain ops and those who are not on the list will not be allowed chanop status.<br />Syntax:  /ChanServ SET channel SECUREOPS {ON | OFF}<br />Example:  /chanserv set #starseekers secureops on<br /><br />* SET SECUREFOUNDER <br />Explanation:  This command enables or disables the Secure Founder option for a channel.  When this is set on, only the real Founder will be able to drop the channel, change its password, change the Founder and the Successor.  Any other Founders set by level after the initial one will not be able to.<br />Syntax:  /ChanServ SET channel SECUREFOUNDER {ON | OFF}<br />Example:  /chanserv set #starseekers securefounder on<br /><br />* SET SIGNKICK<br />Explanation:  When this is enabled, kicks issued with the ChanServ KICK command will have the nick that used the command as part of the reason for the kick.  If you use LEVEL, those who have a level that is superior or equal to the SIGNKICK Level assigned will not have their kicks signed.  See /msg ChanServ HELP LEVELS for further information on SorceryNet, or LEVELS on this page.<br />Syntax:  /msg ChanServ SET channel SIGNKICK {ON | LEVEL | OFF}<br />Example:  /chanserv set #kazoo signkick on<br /><br />* SET XOP <br />Explanation:  This enables or disables the xOP lists system for a channel.  When xOP is set, you have to use the AOP/SOP/VOP/HOP commands in order to grant channel privileges to users.  Otherwise, you have to use the ACCESS command.  Please see ACCESS to learn more on this page so you can decide what is right for your channel.  On a technical note, when you switch from Access list to xOP lists system, your Level definitions and user levels will be altered.  You will find that the values will be different if you switch back to the Access system.  If you switch to the xOP lists system from Access, you will want to double check that the users in the list are set as you want them and adjust as needed.  Switching from xOP lists system to the Access list system, however, causes no problems.<br />Syntax:  /ChanServ SET channel XOP {ON | OFF}<br />Example:  /chanserv set #kazoo xop off<br /><br />* SET OPNOTICE<br />Explanation:  Activating this implies that ChanServ will send a notice to the channel whenever the OP or DEOP commands are used for a user in the channel.  Turning it off means that no message shall be sent.<br />Syntax:  /ChanServ SET channel OPNOTICE {ON | OFF}<br />Example:  /chanserv set #kazoo opnotice on<br /><br />* AOP <br />Explanation:  This maintains the AOP (AutoOP) list for a channel.  The AOP list will give users the right to be auto-opped on your channel, unban and invite themselves to the channel as needed and to have their greet message show when they join the channel, amongst some other privileges.  Only SOP and above may add or delete AOPs.  However, any user on the AOP list may use the AOP LIST command.  If this command is disabled for your channel, you will<br />need to use the Access list or switch to the xOP list so that the function is available.  /Chanserv help ACCESS for more information on the Access List and /Chanserv help SET XOP for information on the XOP list.<br />Syntax:  /ChanServ AOP channel ADD nick <br />Example:  /chanserv aop #rawr add Snoopy = Adds user Snoopy to the AOP list.<br />Syntax:  /ChanServ AOP channel DEL {nick | entry-number(s)}<br />Examples:  /chanserv aop #rawr del Snoopy = Removes Snoopy from the AOP list.<br />/chanserv aop #rawr del 2 = removes the second AOP in the AOP list.<br />/chanserv aop #rawr del 1-2 = This will remove the first two AOPs from the list.  <br />Syntax:  /ChanServ AOP channel LIST [mask | list]<br />/chanserv aop #rawr list 2-5, 7-9 = This will list the 2nd-5th users and 7th-9th users in the AOP List<br />Syntax:  /ChanServ AOP channel CLEAR<br />Example:  /ChanServ aop #rawr clear = This will clear the AOP list entirely.  Only Founders can do this command.<br /><br />* HOP <br />Explanation:  This maintains the HOP (HalfOP) list for a channel, which grants the selected users the right to be auto-halfopped in your channel.  This functions much the same as the AOP commands do.  The HOP ADD, HOP DEL and HOP LIST commands are limited to AOPs and above.  If this command is disabled for your channel, you will need to use the Access list or switch to the xOP list so that the function is available.  /Chanserv help ACCESS for more information on the Access List and /Chanserv help SET XOP for information on the XOP list.<br />Syntax:  /ChanServ HOP channel ADD nick<br />Example:  /chanserv hop #rawr add Snoopy = This adds user Snoopy to the HOP list.<br />Syntax:  /ChanServ HOP channel DEL {nick | entry-number(s)}<br />Examples:  /chanserv hop #rawr del Snoopy = Removes Snoopy from the HOP list.<br />/chanserv hop #rawr del 2 = removes the second HOP in the HOP list.<br />/chanserv hop #rawr del 1-2 = This will remove the first two HOPs from the list.  <br />Syntax:  /ChanServ HOP channel LIST [mask | list]<br />/chanserv hop #rawr list 2-5, 7-9 = This will list the 2nd-5th users and 7th-9th users in the HOP List<br />Syntax:  /ChanServ HOP channel CLEAR<br />Example:  /ChanServ hop #rawr clear = This will clear the HOP list entirely.  Only Founders can do this command.<br />    <br />* SOP <br />Explanation:  This maintains the SOP (SuperOP) list for the channel.  SOPs have all the privileges that AOPs do but also can use the AutoKick and BadWords lists, can read and send channel memos and so on.  AOPs and above can use the List function here. The channel Founder may add or delete from the SOP list.  If this command is disabled for your channel, you will need to use the Access list or switch to the xOP list so that the function is available.  /Chanserv help ACCESS for more information on the Access List and /Chanserv help SET XOP for information on the XOP list.<br />Syntax:  /ChanServ SOP channel ADD nick<br />Example:  /chanserv sop #rawr add Snoopy = This adds user Snoopy to the SOP list.<br />Syntax:  /ChanServ SOP channel DEL {nick | entry-number(s)}<br />Examples:  /chanserv sop #rawr del Snoopy = Removes Snoopy from the SOP list.<br />/chanserv sop #rawr del 2 = removes the second HOP in the SOP list.<br />/chanserv sop #rawr del 1-2 = This will remove the first two SOPs from the list.  <br />Syntax:  /ChanServ SOP channel LIST [mask | list]<br />/chanserv sop #rawr list 2-5, 7-9 = This will list the 2nd-5th users and 7th-9th users in the SOP List<br />Syntax:  /ChanServ SOP channel CLEAR<br />Example:  /ChanServ sop #rawr clear = This will clear the SOP list entirely.  Only Founders can do this command.<br /><br />* VOP <br />Explanation:  This maintains the VOP (VoicePeople) list for a channel.  VOP list users are auto-voiced upon entering a channel, so long as they have Identified to NickServ first.  They can also auto-voice themselves, which can assist them from being moderated. The VOP ADD, VOP DEL and VOP LIST commands are limited to AOPs or above.  If this command is disabled for your channel, you will need to use the Access list or switch to the xOP list so that the function is available.  /Chanserv help ACCESS for more information on the Access List and /Chanserv help SET XOP for information on the XOP list.<br />Syntax:  /ChanServ VOP channel ADD nick<br />Example:  /chanserv vop #rawr add Snoopy = This adds user Snoopy to the VOP list.<br />Syntax:  /ChanServ VOP channel DEL {nick | entry-number(s)}<br />Examples:  /chanserv vop #rawr del Snoopy = Removes Snoopy from the VOP list.<br />/chanserv vop #rawr del 2 = removes the second HOP in the VOP list.<br />/chanserv vop #rawr del 1-2 = This will remove the first two VOPs from the list.  <br />Syntax:  /ChanServ VOP channel LIST [mask | list]<br />/chanserv vop #rawr list 2-5, 7-9 = This will list the 2nd-5th users and 7th-9th users in the VOP List<br />Syntax:  /ChanServ VOP channel CLEAR<br />Example:  /ChanServ vop #rawr clear = This will clear the VOP list entirely.  Only Founders can do this command.<br /><br />* ACCESS <br />Explanation:  This maintains the Access list for a channel.  The Access list specifies which users are allowed chanop status.  It also determines what ChanServ commands will function for the OP in the channel.  Different user levels allow for access to different subsets of privileges.  To add someone to the Access list, the user must have a higher Level than the Level intended for the user being added.  If you wish to change the level someone has in your channel Access list, you may do so by doing the ACCESS ADD command with the new intended level added.  <br />Syntax:  /ChanServ ACCESS channel ADD nick level<br />Examples: /chanserv access #brawl add Bob 5 = Sets Bob as a user with AOP capabilities.<br />/chanserv access #brawl add Bob 10 = This will change Bob to a Level 10, granting him SOP capabilities.<br />Syntax:  /ChanServ ACCESS channel DEL {nick | entry-number(s)}<br />Examples: /chanserv access #brawl del Bob = Removes Bob from the Access List, effectively removing Ops of any sort from the channel.<br />/chanserv access #brawl del 4-7 = This removes the 4th through 7th Ops on the Access List.<br />Syntax:  /ChanServ ACCESS channel LIST {mask | list}<br />Example: /chanserv access #brawl list 2-5,7-9 = Lists access entries numbered 2 through 5 and 7 through 9 for the channel #brawl.  <br />Syntax:  /ChanServ ACCESS channel CLEAR<br />Example: /chanserv access #brawl clear = This clears the entire Access list for the channel.  Only channel Founders can do this command.<br /><br />* ACCESS LEVELS<br />Explanation:  By default, the following Access levels are defined:<br />Founder = Full access to ChanServ functions and automatic opping upon entering the channel.  Note that only one person may have Founder status.  (It cannot be given using the ACCESS command.)<br />10 = Access to AKICK command, automatic opping, may add Ops of lower level to the Access list.<br />5 = Automatic opping, bans and some channel modes.<br />4 = Automatic half-opping.<br />3 = Automatic voicing.<br />0 = No special privileges.  Can be opped by other ops (unless SECUREOPS is set ON).<br />&lt;0 = May not be opped.<br />Note:  These levels may be changed or new ones can even be added using the LEVELS command.  See LEVELS below or on SorceryNet type in: /ChanServ HELP LEVELS for more information.  <br />    <br />* AKICK<br />Explanation:  Akicks are permanent kick/bans against a user.  If the user who is akicked from your channel attempts to join, ChanServ will automatically kick and ban the user.  The AKICK ADD command will add the given nick or usermask to the AutoKick list.  If a reason is given with the command, it will be used, but if not, the default reason is "You have been banned from the channel".  When akicking a registered nick, the NickServ account will be added to the Akick list instead of the mask.  All users within that nickgroup will then be akicked from the channel. The AKICK STICK command permanently bans the given mask on the channel.  If someone attmepts to remove the ban, ChanServ will automatically reset it.  This cannot be used for registered nicks.  The AKICK UNSTICK command cancels the effect of the STICK command, so you will be able to unset the ban again on the channel. Keep in mind that when removing bans from the Akick List, you will want to also remove any bans manually that were set as these will not be removed, whether the akick is there or not.  <br />Syntax:  /ChanServ AKICK channel ADD {nick | mask} [reason]<br />Example:  /chanserv akick #catsrule add *!*@a52371.6ca5ee35.123.456.imsk flooded the channel. Nick: Cake = A mask was used as well as a message.<br />Syntax:  /ChanServ AKICK channel STICK mask<br />Example:  /chanserv akick #catsrule stick Carlton!*@* = You cannot use this command for registered nicks. Otherwise it works just fine.<br />Syntax:  /ChanServ AKICK channel UNSTICK mask<br />Example:  /chanserv akick #catsrule unstick Carlton!*@* = Removes Carlton!*@* off the list.<br />Syntax:  /ChanServ AKICK channel DEL {nick | mask | entry-number(s)} <br />Examples:  /chanserv akick #catsrule del Carlton = The akick is deleted by the nick.<br />/chanserv akick #catsrule del *!*@a52371.6ca5ee35.123.456.imsk = the akick is deleted by the mask.<br />/chanserv akick #catsrule del 12 = This deletes the 12th akick set on the list.<br />Syntax:  /ChanServ AKICK channel LIST {mask | entry-number(s)}<br />Example:  /chanserv akick #catsrule list 4 = This lists the 4th akick done on the channel.  If the '4' was not placed here, it would list all akicks.<br />Syntax:  /ChanServ AKICK channel VIEW {mask | entry-number(s)}<br />Example:  /chanserv akick #catsrule view 3-5 = This brings up a more detailed version of the akicks than 'LIST' will. The 3-5th akicks will be listed.<br />Syntax:  /ChanServ AKICK channel ENFORCE <br />Example: /chanserv akick #catsrule enforce = The AKICK ENFORCE command causes ChanServ to enforce the current AKICK llist by removing those users who match an AKICK mask.<br />Syntax:  /ChanServ AKICK channel CLEAR <br />Example:  /chanserv akick #catsrule clear = Only a Founder may set this, but the channel AKICK list will be cleared.<br /><br />* LEVELS<br />Explanation:  The LEVELS command allows you to have 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, along with the LEVELS 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 ACCESS LEVELS).  For a list of the Level features and functions that can be set, see HELP LEVELS DESC on SorceryNet or you can peruse them here.<br />AUTODEOP     Channel operator status disallowed<br />AUTOHALFOP   Automatic mode +h<br />AUTOOP       Automatic channel operator status<br />AUTOPROTECT  Automatic mode +a<br />AUTOVOICE    Automatic mode +v<br />NOJOIN       Not allowed to join channel<br />SIGNKICK     No signed kick when SIGNKICK LEVEL is used<br />ACC-LIST     Allowed to view the access list<br />ACC-CHANGE   Allowed to modify the access list<br />AKICK        Allowed to use AKICK command<br />SET          Allowed to use SET command (not FOUNDER/PASSWORD)<br />BAN          Allowed to use BAN command<br />BANME        Allowed to ban him/herself<br />CLEAR        Allowed to use CLEAR command<br />GETKEY       Allowed to use GETKEY command<br />HALFOP       Allowed to use HALFOP/DEHALFOP commands<br />HALFOPME     Allowed to (de)halfop him/herself<br />INFO         Allowed to use INFO command with ALL option<br />KICK         Allowed to use KICK command<br />KICKME       Allowed to kick him/herself<br />INVITE       Allowed to use INVITE command<br />OPDEOP       Allowed to use OP/DEOP commands<br />OPDEOPME     Allowed to (de)op him/herself<br />PROTECT      Allowed to use PROTECT/DEPROTECT commands<br />PROTECTME    Allowed to (de)protect him/herself<br />TOPIC        Allowed to use TOPIC command<br />UNBAN        Allowed to use UNBAN command<br />VOICE        Allowed to use VOICE/DEVOICE commands<br />VOICEME      Allowed to (de)voice him/herself<br />MEMO         Allowed to list/read channel memos<br />ASSIGN       Allowed to assign/unassign a bot<br />BADWORDS     Allowed to use BADWORDS command<br />FANTASIA     Allowed to use fantaisist commands<br />GREET        Greet message displayed<br />NOKICK       Never kicked by the bot's kickers<br />SAY          Allowed to use SAY and ACT commands<br />- <br />Syntax:  /ChanServ LEVELS channel SET type level<br />Example:  /chanserv levels #whazzup set greet 5 = This sets the level in which an OP must be in your channel to do the 'GREET' privilege in your channel.  In this case, it is set to 5, so anyone AOP and above can.<br />Syntax:  /ChanServ LEVELS channel {DIS | DISABLE} type<br />Example:  /chanserv levels #whazzup dis kickme = Removes the automatic feature to allow certain low level ops to kick themselves.<br />Syntax:  /ChanServ LEVELS channel LIST<br />Example:  /chanserv levels #whazzup list = gives you a list of the levels and how they are assigned.<br />Syntax:  /Chanserv LEVELS channel RESET <br />Example:  /chanserv levels #whazzup reset = Resets the channel levels to the original default levels.<br /><br />* INFO <br />Explanation:  This lists the information about a registered channel, including its Founder, time of registration, last time the channel was used, the description set for the channel and the modes the channel has locked if any.  If ALL is specified, the entry message and Successor will also be displayed.  By default, the ALL option is limited to those with Founder Access on the channel.<br />Syntax:  /ChanServ INFO channel [ALL]<br />Example:  /chanserv info #bree all <br /><br />* LIST<br />Explanation:  Lists all registered channels matching the criteria given.  Channels set to PRIVATE will not be listed in the search.  <br />Syntax:  /ChanServ LIST pattern<br />Example:  /chanserv list rpg = To list all non-private rooms with 'rpg' in the channel name.<br /><br />* OP <br />Explanation:  Ops a selected nick on a channel.  If the nick is not given with the command, it will op you.  aif the channel and nick are not given, it will op you on all channels that you are on, provided you have the rights to do so.  By default, this command is limited to AOPs/Level 5 Access or above on the channel.  <br />Syntax:  /ChanServ OP channel nick<br />Example: /chanserv op #fair Betty = This will OP Betty, so long as the one who used the command is an AOP or higher and the access permits it.<br />Example: /chanserv op #fair = This will op you if you have AOP/Level 5 Access to the channel, placing a @ in front of your name.<br /><br />DEOP<br />Explanation:  This command Deops a selected nick on the channel.  If the nick is not given, it will deop you.  If the channel and nick are not given, it will deop you in all of the channels you are in, provided you have the rights to (implying you have AOPs/Level 5 Access).<br />Syntax:  /ChanServ DEOP channel nick<br />Example: /chanserv deop #fair = This deops you in the channel #fair.<br />Example:  /chanserv deop = This deops you in all channels in which you are an AOP/Level 5 Access op or higher.<br /><br />* VOICE<br />Explanation:  This command voices a selected nick on a channel.  If the nick is not given, it will voice you.  If the channel and nick are not given, it will voice you on all of the channels you are on, provided you have the Access.  By default, VOPs/Level 3 Access and above can do self-voicing.<br />Syntax:  /ChanServ VOICE channel nick<br />Example:  /chanserv voice #fair Pete = This grants Pete a Voice, indicated by +v appearing in front of his name.<br />Example:  /chanserv voice #fair = Voices yourself in the channel #fair.<br /><br />* DEVOICE <br />Explanation:  This command is the reverse of VOICE.  If a nick is not given, it will devoice you.  If the channel and nick are not given, it will devoice you on all channels you are on, provided you are a VOP/have Level 3 Access.<br />Syntax:  /ChanServ DEVOICE channel nick<br />Example:  /chanserv devoice #fair = This devoices you in #fair.<br /><br />* HALFOP <br />Explanation:  Halfops a selected nick on the channel.  If the nick is not given, it will halfop you.  If the channel and nick are not provided, it will halfop you on all of the channels you are on, provided you have the proper access of HOP/Level 4 or above.<br />Syntax:  /ChanServ HALFOP #channel nick<br />Example:  /chanserv halfop #ogres Patches = This grants halfops to the user Patches.<br /><br />* DEHALFOP <br />Explanation:  Dehalfops a selected nick on a channel.  If the nick is not given, it will dehalfop you.  If the channel and nick are not provided, it will halfop you on all of the channels you are on, provided you have the proper access of HOP/Level 4 or above.<br />Syntax:  /ChanServ DEHALFOP #channel nick<br />Example:  /chanserv dehalfop =  This will dehalfop you on all of the channels that you have HOP/Level 4 Access or above.<br /><br />* PROTECT<br />Explanation:  This command protects a selected nick on a channel.  If the nick is not given, it will protect you.  If the channel and nick are not given, it will protect you on all of the channels you are on, provided you have the Access.  By default, this is limited to the Founder and/or to SOPs or those that have Level 10 Access and above on the channel for self protecting.<br />Syntax:  /ChanServ PROTECT #channel nick<br />Example:  /chanserv protect #bounce = You are now protected on #bounce.<br /><br />* DEPROTECT<br />Explanation:  This command deprotects a selected nick on a channel.  If the nick is not given, it will deprotect you.  If the channel and nick are not given, it will deprotect you on all of the channels you are on, provided you have the Access.  By default, this is limited to the Founder and/or to SOPs or those that have Level 10 Access and above on teh channel for self deprotecting.<br />Syntax:  /ChanServ DEPROTECT #channel nick<br />Example:  /chanserv deprotect #bounce = You are now deprotected on #bounce<br /><br />* OWNER<br />Explanation:  This command gives you owner status on the channel.  If the channel is not given, it will give you owner status on all channels you are on, provided you have the proper Founder access.  <br />Syntax:  /ChanServ OWNER #channel<br />Example:  /chanserv owner #bounce = This gives you owner status in #bounce.<br /><br />* DEOWNER <br />Explanation:  This command removes your owner status on the channel.  If the channel is not given, it will remove status on all channels that you are on, provided you have the proper Founder access.<br />Syntax:  /ChanServ DEOWNER #channel<br />Example:  /chanserv deowner #bounce<br /><br />* INVITE<br />Explanation:  This command tells ChanServ to invite you into the given channel.  By default, this is limited to AOPs/Level 5 Access and above on the channel. <br />Syntax:  /ChanServ INVITE channel<br />Example:  /chanserv invite #bounce<br /><br />* BAN <br />Explanation:  This tells ChanServ to ban a selected nick on a channel.  If a nick is not given, it will ban you.  If a channel and nick are not given, it will ban you on all of the channels you are on.  By default, this is limited to AOPs or those with Level 5 Access or above on the channel.<br />Syntax:  /ChanServ BAN channel<br />Example:  /chanserv ban #bounce = Bans you from #bounce.<br /><br />* UNBAN <br />Explanation:  This tells ChanServ to remove all bans preventing you from entering the given channel.  By default, this is limited to AOPs or those with Level 5 Access or above on the channel.<br />Syntax:  /ChanServ UNBAN channel<br />Example:  /chanserv unban #bounce = removes any channel bans set on you in #bounce<br /><br />* KICK<br />Explanation:  This command will kick a selected nick on a channel.  If the nick is not given, it will kick you.  If the channel and nick are not given, it will kick you on all channels you are on, provided you have AOPs or Level 5 Access and above in the channel.<br />Syntax:  /ChanServ KICK channel nick reason<br />Example:  /chanserv kick #icicle Link being a pain = You have kicked Link from #icicle for being a pain.<br />Example:  /chanserv kick #icicle = You have just kicked yourself out of #icicle.<br /><br />* TOPIC<br />Explanation:  This causes ChanServ to set the channel top ic to the one specified.  If the topic is not given, an empty topic is set.  This command is most useful in conjunction with SET TOPICLOCK.  By default, this is limited to those with Founder Access on the channel.<br />Syntax:  /ChanServ TOPIC channel topic<br />Example:  /chanserv topic #icicle I am so bored today! = Changes the topic to 'I am so bored today!'<br />Example:  /chanserv topic #icicle = Sets no topic.<br /><br />* CLEAR<br />Explanation:  This command instructs ChanServ to clear certain settings on the channel.  These can be any of the following and is limited by default to those with Founder access only:   <br />MODES    Resets all modes on the channel (i.e. clears modes i,k,l,m,n,p,s,t).<br />BANS     Clears all bans on the channel.<br />EXCEPTS  Clears all excepts on the channel.<br />INVITES  Clears all invites on the channel.<br />OPS      Removes channel-operator status (mode +o) from all channel operators.<br />HOPS     Removes channel-halfoperator status (mode +h) from all channel halfoperators, if supported.<br />VOICES   Removes "voice" status (mode +v) from anyone with that mode set.<br />USERS    Removes (kicks) all users from the channel.<br />Syntax:  /ChanServ CLEAR channel what<br />Example:  /chanserv clear #icicle bans = This will clear all of the bans on the channel #icicle.<br /> Chanserv Commands <br />ChanServ allows you to register, control and alter various aspects of channels.  It gives you the ability to customize a channel, ops privileges and more through the commands listed below, as well as providing a solid defense against malicious users who attempt thefts of channels, flooding, etc.  You can access help on IRC by typing in your status window '/chanserv help'.  All of the commands are listed here with more detail and solid examples.  For further aid, you are welcome to bring your inquiries to #sorcery where we will be glad to assist you. <br /><br /><br />* REGISTER<br />Explanation: This command registers a channel into the ChanServ database.  You must have a registered nick, be identified to it and be an op in a channel you would wish to register.  If you need assistance registering your nick, do the command: '/nickserv help register'.  Preferably, use a different password than the one you used to register your nick.  The description can be anything short that tells a bit about what the purpose of the channel is for.  When you register a channel, you become the Founder and as such, can change all of the channel settings and ChanServ automatically grants the Founder channel-operator privileges upon entering the room.  To grant functions to ops who will assist you in running the channel, see /ChanServ ACCESS. <br />Syntax: /ChanServ REGISTER #channel password description <br />Example:  /chanserv register #sorcery ExeCuto1 A room full of unusual people.<br /><br />* IDENTIFY<br />Explanation:  This command gives proof to ChanServ that you are the Founder of the given channel.  Many commands require you to use the Identify command prior to using them.  The password you use here is the same one that you registered the channel with. <br />Syntax:  /ChanServ identify #channel password <br />Example:  /chanserv identify #sorcery ExeCuto1<br />    <br />* LOGOUT<br />Explanation:  This command logs the selected nickname out; meaning that the user would have to re-identify him/herself to regain access.  If you are the Founder of the channel, you have the power to log out anyone from ChanServ.  No one else has this privilege and can only log out themselves.<br />Syntax:  /ChanServ LOGOUT channel nickname<br />Example:  /chanserv logout #orange Bloo<br /><br />* DROP <br />Explanation:  You can use this command to unregister a channel that you are the Founder of.  You must use the IDENTIFY command first.  Once a channel is dropped, it may be registered by the first op to the room, as it has become available.  On SorceryNet, you can do '/chanserv help set option' (replacing 'option' with one of the options below) to get an understanding of what these commands do.  You can also read on in this section for a more in depth look.<br />Syntax:  /ChanServ DROP channel<br />Example:  /chanserv drop #orange<br /><br />* SET<br />Explanation:  This allows the channel Founder to set various channel options.  <br />Syntax:  /ChanServ SET channel option parameters<br />Options:  <br />FOUNDER - Sets the Founder of a channel. <br />SUCCESSOR - Set a successor for a channel.<br />PASSWORD - Set the Founder password for the channel.<br />DESC - Set a channel description.<br />URL - Associate a URL with the channel.<br />EMAIL - Associate an E-mail address with the channel.<br />ENTRYMSG - Set a message to be sent to users when they enter the channel.<br />BANTYPE - Set how Services has bans on the channel<br />MLOCK - Lock channel modes on or off.<br />KEEPTOPIC - Retain a topic when the channel is not in use.<br />OPNOTICE - Send a notice when OP/DEOP commands are used.<br />PEACE - Regulate the use of critical commands.<br />PRIVATE - Hide the channel from the LIST command.<br />RESTRICTED - Restrict access to the channel.<br />SECURE - Activate ChanServ security features.<br />SECUREOPS - Provides stricter control of chanop status.<br />SECUREFOUNDER - Provides stricter control of channel Founder status.<br />SIGNKICK - Sign kicks that are done with the KICK command.<br />TOPICLOCK - The topic can only be changed with the TOPIC command.<br />XOP - Toggles the user privilege system<br /><br />* SET FOUNDER<br />Explanation:  This changes the Founder of a channel.  The new nickname to be set as Founder must be registered.<br />Syntax:  /ChanServ SET channel FOUNDER nick<br />Example:  /chanserv set #blah founder Pita<br /><br />* SET SUCCESSOR<br />Explanation:  This function allows a Founder to choose a successor for the channel.  If the Founder's nick expires or is dropped while the channel is still registered, the Successor will inherit the channel as the new Founder.  If, for some reason, the Successor has too many channels registered to him/her, the channel instead will be dropped.  The Successor must have a registered nick.  <br />Syntax:  /ChanServ set channel SUCCESSOR nick<br />Example:  /chanserv set #blah Luke<br /><br />* SET PASSWORD<br />Explanation:  This allows the Founder to change the password that is used to Identify as the Founder of the channel.  The Founder must Identify to the channel prior to using this command.<br />Syntax:  /ChanServ SET channel PASSWORD password<br />Example:  /chanserv set #zomg password 234lalarawr93<br /><br />* SET DESC<br />Explanation:  This command allows you to set up a description for the channel.  This will show up in LIST and INFO commands.<br />Syntax:  /ChanServ SET channel DESC description<br />Example:  /ChanServ SET #zomg desc a channel totally about whatever zomg. <br /><br />* SET URL <br />Explanation:  Allows you to associate a URL to the channel which will be displayed whenever someone requests information on the channel with the INFO command.  If you give no parameter, instead of providing a new URL, this will delete any current URL listed for the channel.<br />Syntax:  /ChanServ Set channel URL {url}<br />Examples:  /ChanServ set #bloom url http://www.lala.com = inserts the URL http://www.lala.com.<br />/chanserv set #bloom url = No URL set and if there was a former URL, it was deleted.<br /><br />* SET EMAIL<br />Explanation:  This allows you to set up an E-mail address that will be associated to the channel to be viewed whenever someone uses the INFO command.  If this command is used without inputting an address, no E-mail address will be posted.<br />Syntax:  /ChanServ SET channel EMAIL {address}<br />Examples:  /chanserv set #caramba bart@wherever.com = to add E-mail bart@wherever.com<br />/chanserv set #caramba = to remove E-mail.<br /><br />* SET ENTRYMSG<br />Explanation: This sets a message which will be sent via /notice to users when they enter the channel.  If no parameter (message) is given, this erases the entry message that would be sent upon entering the channel.<br />Syntax:  /ChanServ SET channel ENTRYMSG {message}<br />Examples:  /chanserv set #caramba entrymsg Welcome to #caramba! = to set the message "Welcome to #caramba!"<br />/chanserv set #caramba entrymsg = this removes the entry message.<br /><br />* SET BANTYPE<br />Explanation:  Sets the ban type that will be used by ChanServ whenever it needs to ban someone from your channel.  The bantype options are 0-3 and can be selected and then later altered if you wish.<br />0 = ban in the form *!user@host<br />1 = ban in the form *!*user@host<br />2 = ban in the form *!*@host<br />3 = ban in the form *!*user@*.domain<br />Syntax:  /ChanServ SET channel BANTYPE number<br />Example:  /chanserv set #banhammer 2 <br /><br />* SET KEEPTOPIC<br />Explanation:  This enables or disables the option of keeping a topic in the channel even after the last user leaves.  The topic is restored when the channel is next used.  <br />Syntax:  /ChanServ SET channel KEEPTOPIC {ON | OFF}<br />Example:  /chanserv set #banhammer keeptopic on<br /><br />* SET TOPICLOCK<br />Explanation:  This enables or disables the topic lock option for a channel.  When TOPICLOCK is set ON, ChanServ will not allow the channel topic to be changed via the /topic command.  <br />Syntax:  /ChanServ SET channel TOPICLOCK {ON | OFF}<br />Example:  /chanserv set #bruhaha topiclock on<br /><br />* SET MLOCK<br />Explanation:  MLOCK serves as a way to lock in channel mode preferences that with the /mode command, would be erased when the channel is emptied.  To see a list of channel modes, check out 'Channel Modes' in this FAQ section of the site.  ChanServ allows you to define whether you want certain channel modes to be on, off or free to be either on or off.  The SET MLOCK command mode parameter is constructed exactly the same way as a /MODE command.  Modes followed by a '+' are locked on.  Modes with a '-' are locked off.  Each use of this command will remove ALL modes previously locked in before, so copy in the modes you want to remain and want turned off each time.  <br />Syntax:  /ChanServ SET channel MLOCK +modes-modes<br />Examples:  /chanserv set #boogie mlock +nt-iklps = This forces modes 'n' and 't' on, while disabling modes 'i,k,l,p,s'.  <br />/chanserv set #channel mlock +knst-ilmp my-key = This forces modes 'k,n,s,t' to on and disables modes 'i,l,m'off.  It also forces the channel KEY to be "my-key".<br />/chanserv set #channel mlock + = This removes the mode lock so that all channel modes are free to be either on or off.  Ops can then add modes temporarily with the /MODE command.<br />Note:  If you set a mode-locked KEY, as shown in the second example above, you should also SET RESTRICTED ON (see SET RESTRICTED) or anyone entering the channel when it is empty will be able to see the KEY.<br /><br />* SET PEACE<br />Explanation:  This command activates or disables the 'peace' option for a channel.  When PEACE is set, a user will not be able to kick, ban or remove a channel status of a user that has a level superior or equal to his/hers via ChanServ commands.  <br />/Syntax:  /ChanServ SET channel PEACE {ON | OFF}<br />Example:  /chanserv set #rabbit-hole peace on<br /><br />* SET PRIVATE<br />Explanation:  This enables or disables the private option for a channel.  When PRIVATE is set ON, a search by /msg ChanServ LIST will not include the channel in any lists.  The /list command will also not place the channel in the over all list.<br />Syntax:  /ChanServ SET channel PRIVATE {ON | OFF}<br />Example:  /chanserv set #rabbit-hole private off<br /><br />* SET RESTRICTED<br />Explanation:  This enables or disables the restricted access option for a channel.  When restricted access is set on, users who are not on the Access List will instead be kicked and banned from the channel.  <br />Syntax:  /ChanServ SET channel RESTRICTED {ON | OFF}<br />Example:  /chanserv set #baba restricted on<br /><br />* SET SECURE<br />Explanation:  This enables or disables ChanServ's security features for a given channel.  When SECURE is set ON, only uers who have registered nicknames with ChanServ and Identified with their password will be given access (ops functions) to the channel as controlled by the Access List.<br />Syntax:  /ChanServ SET channel SECURE {ON | OFF}<br />Example:  /chanserv set #starseekers secure off<br /><br />* SET SECUREOPS<br />Explanation:  This enables or disables the Secure Ops option for a channel.  If this is set on, only users who are on the userlist will gain ops and those who are not on the list will not be allowed chanop status.<br />Syntax:  /ChanServ SET channel SECUREOPS {ON | OFF}<br />Example:  /chanserv set #starseekers secureops on<br /><br />* SET SECUREFOUNDER <br />Explanation:  This command enables or disables the Secure Founder option for a channel.  When this is set on, only the real Founder will be able to drop the channel, change its password, change the Founder and the Successor.  Any other Founders set by level after the initial one will not be able to.<br />Syntax:  /ChanServ SET channel SECUREFOUNDER {ON | OFF}<br />Example:  /chanserv set #starseekers securefounder on<br /><br />* SET SIGNKICK<br />Explanation:  When this is enabled, kicks issued with the ChanServ KICK command will have the nick that used the command as part of the reason for the kick.  If you use LEVEL, those who have a level that is superior or equal to the SIGNKICK Level assigned will not have their kicks signed.  See /msg ChanServ HELP LEVELS for further information on SorceryNet, or LEVELS on this page.<br />Syntax:  /msg ChanServ SET channel SIGNKICK {ON | LEVEL | OFF}<br />Example:  /chanserv set #kazoo signkick on<br /><br />* SET XOP <br />Explanation:  This enables or disables the xOP lists system for a channel.  When xOP is set, you have to use the AOP/SOP/VOP/HOP commands in order to grant channel privileges to users.  Otherwise, you have to use the ACCESS command.  Please see ACCESS to learn more on this page so you can decide what is right for your channel.  On a technical note, when you switch from Access list to xOP lists system, your Level definitions and user levels will be altered.  You will find that the values will be different if you switch back to the Access system.  If you switch to the xOP lists system from Access, you will want to double check that the users in the list are set as you want them and adjust as needed.  Switching from xOP lists system to the Access list system, however, causes no problems.<br />Syntax:  /ChanServ SET channel XOP {ON | OFF}<br />Example:  /chanserv set #kazoo xop off<br /><br />* SET OPNOTICE<br />Explanation:  Activating this implies that ChanServ will send a notice to the channel whenever the OP or DEOP commands are used for a user in the channel.  Turning it off means that no message shall be sent.<br />Syntax:  /ChanServ SET channel OPNOTICE {ON | OFF}<br />Example:  /chanserv set #kazoo opnotice on<br /><br />* AOP <br />Explanation:  This maintains the AOP (AutoOP) list for a channel.  The AOP list will give users the right to be auto-opped on your channel, unban and invite themselves to the channel as needed and to have their greet message show when they join the channel, amongst some other privileges.  Only SOP and above may add or delete AOPs.  However, any user on the AOP list may use the AOP LIST command.  If this command is disabled for your channel, you will<br />need to use the Access list or switch to the xOP list so that the function is available.  /Chanserv help ACCESS for more information on the Access List and /Chanserv help SET XOP for information on the XOP list.<br />Syntax:  /ChanServ AOP channel ADD nick <br />Example:  /chanserv aop #rawr add Snoopy = Adds user Snoopy to the AOP list.<br />Syntax:  /ChanServ AOP channel DEL {nick | entry-number(s)}<br />Examples:  /chanserv aop #rawr del Snoopy = Removes Snoopy from the AOP list.<br />/chanserv aop #rawr del 2 = removes the second AOP in the AOP list.<br />/chanserv aop #rawr del 1-2 = This will remove the first two AOPs from the list.  <br />Syntax:  /ChanServ AOP channel LIST [mask | list]<br />/chanserv aop #rawr list 2-5, 7-9 = This will list the 2nd-5th users and 7th-9th users in the AOP List<br />Syntax:  /ChanServ AOP channel CLEAR<br />Example:  /ChanServ aop #rawr clear = This will clear the AOP list entirely.  Only Founders can do this command.<br /><br />* HOP <br />Explanation:  This maintains the HOP (HalfOP) list for a channel, which grants the selected users the right to be auto-halfopped in your channel.  This functions much the same as the AOP commands do.  The HOP ADD, HOP DEL and HOP LIST commands are limited to AOPs and above.  If this command is disabled for your channel, you will need to use the Access list or switch to the xOP list so that the function is available.  /Chanserv help ACCESS for more information on the Access List and /Chanserv help SET XOP for information on the XOP list.<br />Syntax:  /ChanServ HOP channel ADD nick<br />Example:  /chanserv hop #rawr add Snoopy = This adds user Snoopy to the HOP list.<br />Syntax:  /ChanServ HOP channel DEL {nick | entry-number(s)}<br />Examples:  /chanserv hop #rawr del Snoopy = Removes Snoopy from the HOP list.<br />/chanserv hop #rawr del 2 = removes the second HOP in the HOP list.<br />/chanserv hop #rawr del 1-2 = This will remove the first two HOPs from the list.  <br />Syntax:  /ChanServ HOP channel LIST [mask | list]<br />/chanserv hop #rawr list 2-5, 7-9 = This will list the 2nd-5th users and 7th-9th users in the HOP List<br />Syntax:  /ChanServ HOP channel CLEAR<br />Example:  /ChanServ hop #rawr clear = This will clear the HOP list entirely.  Only Founders can do this command.<br />    <br />* SOP <br />Explanation:  This maintains the SOP (SuperOP) list for the channel.  SOPs have all the privileges that AOPs do but also can use the AutoKick and BadWords lists, can read and send channel memos and so on.  AOPs and above can use the List function here. The channel Founder may add or delete from the SOP list.  If this command is disabled for your channel, you will need to use the Access list or switch to the xOP list so that the function is available.  /Chanserv help ACCESS for more information on the Access List and /Chanserv help SET XOP for information on the XOP list.<br />Syntax:  /ChanServ SOP channel ADD nick<br />Example:  /chanserv sop #rawr add Snoopy = This adds user Snoopy to the SOP list.<br />Syntax:  /ChanServ SOP channel DEL {nick | entry-number(s)}<br />Examples:  /chanserv sop #rawr del Snoopy = Removes Snoopy from the SOP list.<br />/chanserv sop #rawr del 2 = removes the second HOP in the SOP list.<br />/chanserv sop #rawr del 1-2 = This will remove the first two SOPs from the list.  <br />Syntax:  /ChanServ SOP channel LIST [mask | list]<br />/chanserv sop #rawr list 2-5, 7-9 = This will list the 2nd-5th users and 7th-9th users in the SOP List<br />Syntax:  /ChanServ SOP channel CLEAR<br />Example:  /ChanServ sop #rawr clear = This will clear the SOP list entirely.  Only Founders can do this command.<br /><br />* VOP <br />Explanation:  This maintains the VOP (VoicePeople) list for a channel.  VOP list users are auto-voiced upon entering a channel, so long as they have Identified to NickServ first.  They can also auto-voice themselves, which can assist them from being moderated. The VOP ADD, VOP DEL and VOP LIST commands are limited to AOPs or above.  If this command is disabled for your channel, you will need to use the Access list or switch to the xOP list so that the function is available.  /Chanserv help ACCESS for more information on the Access List and /Chanserv help SET XOP for information on the XOP list.<br />Syntax:  /ChanServ VOP channel ADD nick<br />Example:  /chanserv vop #rawr add Snoopy = This adds user Snoopy to the VOP list.<br />Syntax:  /ChanServ VOP channel DEL {nick | entry-number(s)}<br />Examples:  /chanserv vop #rawr del Snoopy = Removes Snoopy from the VOP list.<br />/chanserv vop #rawr del 2 = removes the second HOP in the VOP list.<br />/chanserv vop #rawr del 1-2 = This will remove the first two VOPs from the list.  <br />Syntax:  /ChanServ VOP channel LIST [mask | list]<br />/chanserv vop #rawr list 2-5, 7-9 = This will list the 2nd-5th users and 7th-9th users in the VOP List<br />Syntax:  /ChanServ VOP channel CLEAR<br />Example:  /ChanServ vop #rawr clear = This will clear the VOP list entirely.  Only Founders can do this command.<br /><br />* ACCESS <br />Explanation:  This maintains the Access list for a channel.  The Access list specifies which users are allowed chanop status.  It also determines what ChanServ commands will function for the OP in the channel.  Different user levels allow for access to different subsets of privileges.  To add someone to the Access list, the user must have a higher Level than the Level intended for the user being added.  If you wish to change the level someone has in your channel Access list, you may do so by doing the ACCESS ADD command with the new intended level added.  <br />Syntax:  /ChanServ ACCESS channel ADD nick level<br />Examples: /chanserv access #brawl add Bob 5 = Sets Bob as a user with AOP capabilities.<br />/chanserv access #brawl add Bob 10 = This will change Bob to a Level 10, granting him SOP capabilities.<br />Syntax:  /ChanServ ACCESS channel DEL {nick | entry-number(s)}<br />Examples: /chanserv access #brawl del Bob = Removes Bob from the Access List, effectively removing Ops of any sort from the channel.<br />/chanserv access #brawl del 4-7 = This removes the 4th through 7th Ops on the Access List.<br />Syntax:  /ChanServ ACCESS channel LIST {mask | list}<br />Example: /chanserv access #brawl list 2-5,7-9 = Lists access entries numbered 2 through 5 and 7 through 9 for the channel #brawl.  <br />Syntax:  /ChanServ ACCESS channel CLEAR<br />Example: /chanserv access #brawl clear = This clears the entire Access list for the channel.  Only channel Founders can do this command.<br /><br />* ACCESS LEVELS<br />Explanation:  By default, the following Access levels are defined:<br />Founder = Full access to ChanServ functions and automatic opping upon entering the channel.  Note that only one person may have Founder status.  (It cannot be given using the ACCESS command.)<br />10 = Access to AKICK command, automatic opping, may add Ops of lower level to the Access list.<br />5 = Automatic opping, bans and some channel modes.<br />4 = Automatic half-opping.<br />3 = Automatic voicing.<br />0 = No special privileges.  Can be opped by other ops (unless SECUREOPS is set ON).<br />&lt;0 = May not be opped.<br />Note:  These levels may be changed or new ones can even be added using the LEVELS command.  See LEVELS below or on SorceryNet type in: /ChanServ HELP LEVELS for more information.  <br />    <br />* AKICK<br />Explanation:  Akicks are permanent kick/bans against a user.  If the user who is akicked from your channel attempts to join, ChanServ will automatically kick and ban the user.  The AKICK ADD command will add the given nick or usermask to the AutoKick list.  If a reason is given with the command, it will be used, but if not, the default reason is "You have been banned from the channel".  When akicking a registered nick, the NickServ account will be added to the Akick list instead of the mask.  All users within that nickgroup will then be akicked from the channel. The AKICK STICK command permanently bans the given mask on the channel.  If someone attmepts to remove the ban, ChanServ will automatically reset it.  This cannot be used for registered nicks.  The AKICK UNSTICK command cancels the effect of the STICK command, so you will be able to unset the ban again on the channel. Keep in mind that when removing bans from the Akick List, you will want to also remove any bans manually that were set as these will not be removed, whether the akick is there or not.  <br />Syntax:  /ChanServ AKICK channel ADD {nick | mask} [reason]<br />Example:  /chanserv akick #catsrule add *!*@a52371.6ca5ee35.123.456.imsk flooded the channel. Nick: Cake = A mask was used as well as a message.<br />Syntax:  /ChanServ AKICK channel STICK mask<br />Example:  /chanserv akick #catsrule stick Carlton!*@* = You cannot use this command for registered nicks. Otherwise it works just fine.<br />Syntax:  /ChanServ AKICK channel UNSTICK mask<br />Example:  /chanserv akick #catsrule unstick Carlton!*@* = Removes Carlton!*@* off the list.<br />Syntax:  /ChanServ AKICK channel DEL {nick | mask | entry-number(s)} <br />Examples:  /chanserv akick #catsrule del Carlton = The akick is deleted by the nick.<br />/chanserv akick #catsrule del *!*@a52371.6ca5ee35.123.456.imsk = the akick is deleted by the mask.<br />/chanserv akick #catsrule del 12 = This deletes the 12th akick set on the list.<br />Syntax:  /ChanServ AKICK channel LIST {mask | entry-number(s)}<br />Example:  /chanserv akick #catsrule list 4 = This lists the 4th akick done on the channel.  If the '4' was not placed here, it would list all akicks.<br />Syntax:  /ChanServ AKICK channel VIEW {mask | entry-number(s)}<br />Example:  /chanserv akick #catsrule view 3-5 = This brings up a more detailed version of the akicks than 'LIST' will. The 3-5th akicks will be listed.<br />Syntax:  /ChanServ AKICK channel ENFORCE <br />Example: /chanserv akick #catsrule enforce = The AKICK ENFORCE command causes ChanServ to enforce the current AKICK llist by removing those users who match an AKICK mask.<br />Syntax:  /ChanServ AKICK channel CLEAR <br />Example:  /chanserv akick #catsrule clear = Only a Founder may set this, but the channel AKICK list will be cleared.<br /><br />* LEVELS<br />Explanation:  The LEVELS command allows you to have 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, along with the LEVELS 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 ACCESS LEVELS).  For a list of the Level features and functions that can be set, see HELP LEVELS DESC on SorceryNet or you can peruse them here.<br />AUTODEOP     Channel operator status disallowed<br />AUTOHALFOP   Automatic mode +h<br />AUTOOP       Automatic channel operator status<br />AUTOPROTECT  Automatic mode +a<br />AUTOVOICE    Automatic mode +v<br />NOJOIN       Not allowed to join channel<br />SIGNKICK     No signed kick when SIGNKICK LEVEL is used<br />ACC-LIST     Allowed to view the access list<br />ACC-CHANGE   Allowed to modify the access list<br />AKICK        Allowed to use AKICK command<br />SET          Allowed to use SET command (not FOUNDER/PASSWORD)<br />BAN          Allowed to use BAN command<br />BANME        Allowed to ban him/herself<br />CLEAR        Allowed to use CLEAR command<br />GETKEY       Allowed to use GETKEY command<br />HALFOP       Allowed to use HALFOP/DEHALFOP commands<br />HALFOPME     Allowed to (de)halfop him/herself<br />INFO         Allowed to use INFO command with ALL option<br />KICK         Allowed to use KICK command<br />KICKME       Allowed to kick him/herself<br />INVITE       Allowed to use INVITE command<br />OPDEOP       Allowed to use OP/DEOP commands<br />OPDEOPME     Allowed to (de)op him/herself<br />PROTECT      Allowed to use PROTECT/DEPROTECT commands<br />PROTECTME    Allowed to (de)protect him/herself<br />TOPIC        Allowed to use TOPIC command<br />UNBAN        Allowed to use UNBAN command<br />VOICE        Allowed to use VOICE/DEVOICE commands<br />VOICEME      Allowed to (de)voice him/herself<br />MEMO         Allowed to list/read channel memos<br />ASSIGN       Allowed to assign/unassign a bot<br />BADWORDS     Allowed to use BADWORDS command<br />FANTASIA     Allowed to use fantaisist commands<br />GREET        Greet message displayed<br />NOKICK       Never kicked by the bot's kickers<br />SAY          Allowed to use SAY and ACT commands<br />- <br />Syntax:  /ChanServ LEVELS channel SET type level<br />Example:  /chanserv levels #whazzup set greet 5 = This sets the level in which an OP must be in your channel to do the 'GREET' privilege in your channel.  In this case, it is set to 5, so anyone AOP and above can.<br />Syntax:  /ChanServ LEVELS channel {DIS | DISABLE} type<br />Example:  /chanserv levels #whazzup dis kickme = Removes the automatic feature to allow certain low level ops to kick themselves.<br />Syntax:  /ChanServ LEVELS channel LIST<br />Example:  /chanserv levels #whazzup list = gives you a list of the levels and how they are assigned.<br />Syntax:  /Chanserv LEVELS channel RESET <br />Example:  /chanserv levels #whazzup reset = Resets the channel levels to the original default levels.<br /><br />* INFO <br />Explanation:  This lists the information about a registered channel, including its Founder, time of registration, last time the channel was used, the description set for the channel and the modes the channel has locked if any.  If ALL is specified, the entry message and Successor will also be displayed.  By default, the ALL option is limited to those with Founder Access on the channel.<br />Syntax:  /ChanServ INFO channel [ALL]<br />Example:  /chanserv info #bree all <br /><br />* LIST<br />Explanation:  Lists all registered channels matching the criteria given.  Channels set to PRIVATE will not be listed in the search.  <br />Syntax:  /ChanServ LIST pattern<br />Example:  /chanserv list rpg = To list all non-private rooms with 'rpg' in the channel name.<br /><br />* OP <br />Explanation:  Ops a selected nick on a channel.  If the nick is not given with the command, it will op you.  aif the channel and nick are not given, it will op you on all channels that you are on, provided you have the rights to do so.  By default, this command is limited to AOPs/Level 5 Access or above on the channel.  <br />Syntax:  /ChanServ OP channel nick<br />Example: /chanserv op #fair Betty = This will OP Betty, so long as the one who used the command is an AOP or higher and the access permits it.<br />Example: /chanserv op #fair = This will op you if you have AOP/Level 5 Access to the channel, placing a @ in front of your name.<br /><br />DEOP<br />Explanation:  This command Deops a selected nick on the channel.  If the nick is not given, it will deop you.  If the channel and nick are not given, it will deop you in all of the channels you are in, provided you have the rights to (implying you have AOPs/Level 5 Access).<br />Syntax:  /ChanServ DEOP channel nick<br />Example: /chanserv deop #fair = This deops you in the channel #fair.<br />Example:  /chanserv deop = This deops you in all channels in which you are an AOP/Level 5 Access op or higher.<br /><br />* VOICE<br />Explanation:  This command voices a selected nick on a channel.  If the nick is not given, it will voice you.  If the channel and nick are not given, it will voice you on all of the channels you are on, provided you have the Access.  By default, VOPs/Level 3 Access and above can do self-voicing.<br />Syntax:  /ChanServ VOICE channel nick<br />Example:  /chanserv voice #fair Pete = This grants Pete a Voice, indicated by +v appearing in front of his name.<br />Example:  /chanserv voice #fair = Voices yourself in the channel #fair.<br /><br />* DEVOICE <br />Explanation:  This command is the reverse of VOICE.  If a nick is not given, it will devoice you.  If the channel and nick are not given, it will devoice you on all channels you are on, provided you are a VOP/have Level 3 Access.<br />Syntax:  /ChanServ DEVOICE channel nick<br />Example:  /chanserv devoice #fair = This devoices you in #fair.<br /><br />* HALFOP <br />Explanation:  Halfops a selected nick on the channel.  If the nick is not given, it will halfop you.  If the channel and nick are not provided, it will halfop you on all of the channels you are on, provided you have the proper access of HOP/Level 4 or above.<br />Syntax:  /ChanServ HALFOP #channel nick<br />Example:  /chanserv halfop #ogres Patches = This grants halfops to the user Patches.<br /><br />* DEHALFOP <br />Explanation:  Dehalfops a selected nick on a channel.  If the nick is not given, it will dehalfop you.  If the channel and nick are not provided, it will halfop you on all of the channels you are on, provided you have the proper access of HOP/Level 4 or above.<br />Syntax:  /ChanServ DEHALFOP #channel nick<br />Example:  /chanserv dehalfop =  This will dehalfop you on all of the channels that you have HOP/Level 4 Access or above.<br /><br />* PROTECT<br />Explanation:  This command protects a selected nick on a channel.  If the nick is not given, it will protect you.  If the channel and nick are not given, it will protect you on all of the channels you are on, provided you have the Access.  By default, this is limited to the Founder and/or to SOPs or those that have Level 10 Access and above on the channel for self protecting.<br />Syntax:  /ChanServ PROTECT #channel nick<br />Example:  /chanserv protect #bounce = You are now protected on #bounce.<br /><br />* DEPROTECT<br />Explanation:  This command deprotects a selected nick on a channel.  If the nick is not given, it will deprotect you.  If the channel and nick are not given, it will deprotect you on all of the channels you are on, provided you have the Access.  By default, this is limited to the Founder and/or to SOPs or those that have Level 10 Access and above on teh channel for self deprotecting.<br />Syntax:  /ChanServ DEPROTECT #channel nick<br />Example:  /chanserv deprotect #bounce = You are now deprotected on #bounce<br /><br />* OWNER<br />Explanation:  This command gives you owner status on the channel.  If the channel is not given, it will give you owner status on all channels you are on, provided you have the proper Founder access.  <br />Syntax:  /ChanServ OWNER #channel<br />Example:  /chanserv owner #bounce = This gives you owner status in #bounce.<br /><br />* DEOWNER <br />Explanation:  This command removes your owner status on the channel.  If the channel is not given, it will remove status on all channels that you are on, provided you have the proper Founder access.<br />Syntax:  /ChanServ DEOWNER #channel<br />Example:  /chanserv deowner #bounce<br /><br />* INVITE<br />Explanation:  This command tells ChanServ to invite you into the given channel.  By default, this is limited to AOPs/Level 5 Access and above on the channel. <br />Syntax:  /ChanServ INVITE channel<br />Example:  /chanserv invite #bounce<br /><br />* BAN <br />Explanation:  This tells ChanServ to ban a selected nick on a channel.  If a nick is not given, it will ban you.  If a channel and nick are not given, it will ban you on all of the channels you are on.  By default, this is limited to AOPs or those with Level 5 Access or above on the channel.<br />Syntax:  /ChanServ BAN channel<br />Example:  /chanserv ban #bounce = Bans you from #bounce.<br /><br />* UNBAN <br />Explanation:  This tells ChanServ to remove all bans preventing you from entering the given channel.  By default, this is limited to AOPs or those with Level 5 Access or above on the channel.<br />Syntax:  /ChanServ UNBAN channel<br />Example:  /chanserv unban #bounce = removes any channel bans set on you in #bounce<br /><br />* KICK<br />Explanation:  This command will kick a selected nick on a channel.  If the nick is not given, it will kick you.  If the channel and nick are not given, it will kick you on all channels you are on, provided you have AOPs or Level 5 Access and above in the channel.<br />Syntax:  /ChanServ KICK channel nick reason<br />Example:  /chanserv kick #icicle Link being a pain = You have kicked Link from #icicle for being a pain.<br />Example:  /chanserv kick #icicle = You have just kicked yourself out of #icicle.<br /><br />* TOPIC<br />Explanation:  This causes ChanServ to set the channel top ic to the one specified.  If the topic is not given, an empty topic is set.  This command is most useful in conjunction with SET TOPICLOCK.  By default, this is limited to those with Founder Access on the channel.<br />Syntax:  /ChanServ TOPIC channel topic<br />Example:  /chanserv topic #icicle I am so bored today! = Changes the topic to 'I am so bored today!'<br />Example:  /chanserv topic #icicle = Sets no topic.<br /><br />* CLEAR<br />Explanation:  This command instructs ChanServ to clear certain settings on the channel.  These can be any of the following and is limited by default to those with Founder access only:   <br />MODES    Resets all modes on the channel (i.e. clears modes i,k,l,m,n,p,s,t).<br />BANS     Clears all bans on the channel.<br />EXCEPTS  Clears all excepts on the channel.<br />INVITES  Clears all invites on the channel.<br />OPS      Removes channel-operator status (mode +o) from all channel operators.<br />HOPS     Removes channel-halfoperator status (mode +h) from all channel halfoperators, if supported.<br />VOICES   Removes "voice" status (mode +v) from anyone with that mode set.<br />USERS    Removes (kicks) all users from the channel.<br />Syntax:  /ChanServ CLEAR channel what<br />Example:  /chanserv clear #icicle bans = This will clear all of the bans on the channel #icicle.<br /> NickServ 2010-08-30T06:50:42Z 2010-08-30T06:50:42Z http://www.sorcery.net/index.php?option=com_content&view=article&id=247:nickserv&catid=105:faqs&Itemid=78 SorceryNet jc@sorcery.net Nickserv Commands<br /><br />Nickserv enables a user to register a nick in order to own the nick and have the benefits that come with it.  There are quite a few functions and options that come with registering a nick to include being able to be auto-opped in a channel, receiving and sending memos, registering your own channel and grouping other nicks.  The list provided below gives the commands for NickServ with detailed explanations and examples.  You may also find quick support by typing '/nickserv help' in your status window which will give you this list to peruse on SorceryNet.<br /><br /><br />* REGISTER<br />Explanation: This command will register a nick to you.  Your e-mail is used to send you out an authentication code for confirming your nick registry and may be used later to help you recover your nick if you lose your password.  Make sure to put a real e-mail in.  All e-mails are confidential and for your use only.  Nicks are automatically set to be hidden from other users who may use INFO on a nick.  Nick registrations expire after 30 days if not identified to.  See 'Identify' for further information.  Do not give out your password to anyone and make the password something that is not easily thought up by other users.  <br />Syntax: /NickServ REGISTER password e-mail<br />Example: /nickserv register vegetable cornyemail@blankmail.net <br />Note:  Passwords that you make are case sensitive and there can be no spaces between the letters.  Also, do not put any symbols around the e-mail such as { } or [ ].  The e-mail will be incorrect if you do so.<br /><br />* CONFIRM<br />Explanation:  You will receive an e-mail after you register your nick.  Go to the e-mail you registered your nick with and open the letter from 'services'.  A line will read like this:  [Please type " /msg NickServ confirm cLqc6RpR62" into your IRC client to complete the registration.] Copy or type in /msg nickserv confirm [number given] to your IRC client window while being in the appropriate nick and hit Enter.  This will finish your registration process.<br />Example: /nickserv confirm cLqc6RpR62<br /><br />* ENTERCODE <br />Explanation:  This allows you to enter the passcode you received after losing a password and going to an Oper in #sorcery to have a new code sent to you. Be in the nick before using this command.<br />Syntax:  /NickServ ENTERCODE passcode<br />Example:  /nickserv entercode cl23KHGki3<br /><br />* GROUP<br />Explanation: This command allows a new nickname you have selected to join a registered nickname's group.  The password after this will be the same as any other nick in the Group.  You will also be able to share your dominant nick's configuration, memos, channel privileges and more.  Prior to using this command, identify to your target nick by changing to the target nick and doing the Identify command.  After, change back to the nick you want to Group.  You can only be in one group at a time and group merging is not possible.  If you register another nick, you will need to drop it to put it in the group.  <br />Syntax:  /NickServ GROUP target password<br />Example: nick target = Kenny  password for nick registered = peanutbutter<br />/nickserv group Kenny peanutbutter<br /><br />* IDENTIFY<br />Explanation:  After registering a nick, you will want to identify to it in order to keep the nick registered to you.  Failure to do so will cause the nick to drop after 30 days, making it available again to other users.  You also may not be able to use the nick if you do not identify to it within a minute if your settings for the nick are set that way.  The network does this automatically so if you wish to change the options, you will need to adjust this yourself.  Identifying to your nick also grants you the ability to use the privileges that come with a registered nick such as channel ops and access to your memos.  The password is the same one that you registered your nick with.  <br />Syntax:  /NickServ IDENTIFY password<br />Example:  Password = pepsi<br />/nickserv identify pepsi<br />Shortcut:  /ns id pepsi<br /><br />* LOGOUT<br />Explanation:  This reverses the effect of the Identify command, but will not ask you to re-identify to the nick, so long as you do not lose your connection or change nicks.<br />Syntax:  /NickServ LOGOUT<br />Example:  /nickserv logout<br /><br />* DROP<br />Explanation:  This command will drop the registered nickname from the NickServ database.  A nick that has been dropped is available for anyone to register.  You will need to have identified to your nick prior to using this command.  <br />Syntax:  /NickServ DROP nickname<br />Example: nick is Junkie<br />/nickserv drop Junkie<br /><br />* ACCESS<br />Explanation:  This command can modify or display the access list for your nick.  It is the list of addresses that will automatically be recognized by NickServ so that you have access to use the nick.  If you want to use the nick from a different address, you need to use the Identify command for NickServ to recognize you.<br />Syntax:  /NickServ ACCESS ADD mask<br />/NickServ ACCESS DEL mask<br />/NickServ ACCESS LIST<br />Examples:  <br />/nickserv access add Jen@*.blah.com = Allows access to the ident user Jen when connecting from any machine in the blah.com domain.<br />/nickserv access del Jen@*.blah.com = Removes the access granted by the above command.<br />/nickserv access list = Gives you the current access list.<br /><br />* SET<br />Explanation:  There are various options you can set for your nick and registry. Each option listed below will have further instructions here or you can use /nickserv help set option.  You must be Identified to your nick before you can use these commands.<br />Syntax:  /NickServ SET option parameters<br />Options:<br />DISPLAY - Changes the display nick of your Group in Services.<br />PASSWORD - This allows you to change your password.<br />LANGUAGE - Sets the language that Services will use when sending messages to you.<br />URL - Place in a url which will be associated with your nickname.<br />EMAIL - Sets an email to be associated with your nick and allows you to alter it if your email you registered with has changed.<br />ICQ - Allows you to place an ICQ number in to be viewed by others.<br />GREET - Place a greet message to go with your nickname.<br />KILL - Allows you to turn on the nick protection timer or disengage it. Also allows you to set the timer in which a nick will be forcibly changed.<br />SECURE - Turn nickname security on or off. This is the prompt to change your nick. <br />PRIVATE - Prevents your nickname from appearing in a /nickserv list used.<br />HIDE - Gives the option of hiding email, status, usermask, last quit message and whether you are online or not.<br />MSG - Sets how Services will communicate with you. If this is set 'on', Services will message you instead of sending Notices.<br />AUTOOP - On or off. This allows ChanServ to op you automatically when you enter a channel you have autoops in if set to 'on.  If 'off', ChanServ will not op you automatically.<br /><br />* SET DISPLAY<br />Explanation:  This changes the display used to refer to your nickname Group in Services.  The new display must be a nick within your Group and in order to change it, you must be in the nickname and identified to it before using this command.  When someone asks for info on a nick, the dominant display nickname will show up.<br />Syntax:  /NickServ SET DISPLAY new-Display<br />Example: /nickserv set display Claw<br /><br />* SET PASSWORD<br />Explanation:  This allows you to change your password.  You must identify to the nick with the former password before you can do this command.<br />Syntax:  /NickServ SET PASSWORD new-password<br />Example: /nickserv set PASSWORD speeddemon23<br /><br />* SET LANGUAGE<br />Explanation:  This changes the language that Services will use when sending you messages. <br />Syntax:  /NickServ SET LANGUAGE number<br />The following is a list of the supported languages and the number.<br />1 = English<br />2 = Francais (French)<br />3 = Deutsch (German)<br />4 = Italiano (Italian)<br />5 = Português (Portuguese)<br />6 = Español (Spanish)<br />7 = Türkçe (Turkish)<br />8 = Catala (Catalan)<br />9 = ÅëëçíéêÜ (Greek)<br />10 = Nederlands (Dutch)<br />11 = Ðóññêèé (Russian)<br />12 = Magyar (Hungarian)<br />13 = Polski (Polish)<br />Example:  /nickserv set language 4 = for Italian.<br /><br />* SET URL<br />Explanation:  This will associate a URL with your nickname and can be viewed when someone does an Info request on your nick.<br />Syntax:  /NickServ SET URL url<br />Example:  /nickserv set url http:www.wherever.com<br /><br />* SET EMAIL<br />Explanation:  Sets an E-mail address to your nickname.  This address can be displayed when someone uses the Info command.  You can also hide it by doing the SET HIDE command.  Setting an email allows you to recover a forgotten password.<br />Syntax:  /NickServ SET EMAIL address<br />Example:  /nickserv set email blahsomething@gmallz.com<br /><br />* SET ICQ<br />Explanation:  Puts in an ICQ number that will show up when someone uses an INFO command on your nick.<br />Syntax:  /NickServ SET ICQ number<br />/example: /nickserv set ICQ 2342392333<br /><br />* SET GREET<br />Explanation:  This will set your nick up with a message that will be displayed when joining a channel that has the GREET option enabled, provided you have the necessary op access.  <br />Syntax: /NickServ SET GREET message<br />Example: /nickserv set GREET I have arrived. All rejoice and give offerings.<br /><br />* SET KILL<br />Explanation: This turns the automatic protection for your nick on or off and also enables you to change the timer before NickServ will forcibly remove the nick from someone.  QUICK allows only 20 seconds for someone to change nicks or Identify instead of the usual 60 seconds.  IMMED will force the user's nick to be changed immediately without being warned first.  It is -strongly- suggested that you do not use the IMMED option if you are unfamiliar with it, as it will prevent even the nick owner from getting the nick if Access is not set correctly.  There is no remote identifying at this time.<br />Syntax:  /NickServ SET KILL {ON | QUICK | IMMED | OFF} <br />Example:  /nickserv set kill on = sets kill on<br />/nickserv set kill off = turns kill off<br />/nickserv set quick on = sets the time to 20 seconds before the nick is forcibly removed.<br /><br />* SET SECURE<br />Explanation:  This turns NickServ's security features on or off for your registered nick.  With SECURE set ON, you must enter your password before you will be recognized as the owner of the nick, regardless of whether you have set your address on the ACCESS list or not.  However, if you are on the ACCESS list, NickServ will not auto-kill you, regardless of the setting of the KILL option.  Setting this to OFF will remove the prompt to identify to NickServ, allowing anyone to use the nick, though it will give a message that the nick is registered to someone else.<br />/Syntax:  /NickServ SET SECURE {ON | OFF}<br />Examples: /nickserv set secure on<br />/nickserv set secure off<br /><br />* SET PRIVATE<br />Explanation:  If set to ON, your nickname will not appear in a nickname list generated with NickServ's LIST command.  With PRIVATE set off, users may see your nick with the LIST command.  Anyone who knows your nickname, whether this is set on or off, can still get information on the nick by using the INFO command.<br />Syntax:  /NickServ SET PRIVATE {ON | OFF}<br />Examples: /nickserv set private on<br />/nickserv set private off<br /><br />* SET HIDE<br />Explanation: This allows certain information that you do not want displayed, when someone uses a NickServ INFO command on your nick, to be hidden.  <br />Syntax: /NickServ SET HIDE [EMAIL | STATUS | USERMASK | QUIT] {ON | OFF}<br />Examples:  /nickserv set hide email on = hides email. /nickserv set hide email off = allows it to appear in INFO checks.<br />/nickserv set hide status on or off = shows Services access status or not.<br />/nickserv set hide usermask on or off = hides last seen user@hostmask info, or not if off.<br />/nickserv set hide quit on or off = hides or reveals the last quit message you had when leaving SorceryNet.<br />Note:  Hostmasking is done on SorceryNet whether the usermask option is set on or off.<br /><br />* SET MSG<br />Explanation:  This allows you to select the way Services will be communicating with you.  With SET MSG ON, Services will send you messages.  With this option off (standard), Services will send you Notices instead.<br />Syntax:  /NickServ SET MSG {ON | OFF}<br />Examples: /nickserv set msg on<br />/nickserv set msg off<br /><br />* UPDATE<br />Explanation:  This updates your current status.  It will check for new memos, sets needed chanmodes (ModeonID) and updates your userflags such as lastseentime, etc.<br />Syntax:  /NickServ UPDATE<br />Example: /nickserv update<br /><br />* RECOVER<br />Explanation:  Using this command allows you to recover your nickname if someone else has taken it and you have the KILL option set OFF.  It does the same thing that NickServ does automatically when the KILL option is on.  If you use this option, NickServ brings a fake user online with the apprehended nickname so the other user is forcibly disconnected.  It will remain online for 60 seconds to ensure the other user does not just reconnect immediately so that you have time to reclaim your nick.  If you wish to get the nick back sooner than 60 seconds, you can use the RELEASE command.<br />Syntax: /NickServ RECOVER nickname {password}<br />Example: /nickserv recover Suzy saywhat23<br /><br />* RELEASE<br />Explanation:  Use of this command instructs NickServ to release the hold on your nickname that is caused by automatic KILL protection or by use of the RECOVER command.  Usually the nick will be held by NickServ for 60 seconds but this allows you to cut the time to immediate.<br />Syntax: /NickServ RELEASE nickname {password}<br />Example: /nickserv release Suzy saywhat23<br /><br />* GHOST<br />Explanation: Occasionally, your internet connection is cut off abruptly but IRC may recognize you as still being online.  You can acquire your nick back by using this command, which will terminate "ghost's" connection.  <br />Syntax:  /NickServ GHOST nickname {password}<br />Example:  /nickserv ghost Suzy saywhat23<br /><br />* INFO<br />Explanation:  This displays information about the target nickname such as the owner of the nick, last seen address and time on and some nick options such as URLs set.  To hide some of this information, a user may use the SET HIDE command.  If you are identified to the nick you are looking up information on, you will be shown all of the information; regardless of whether you have set it to Hide or not.<br />Syntax:  /NickServ INFO nickname = provides some info.  You will see the option to get more information with 'all'<br />Syntax:  /NickServ INFO nickname ALL = provides all of the information possible to be collected on the nick.<br />Example:  /nickserv info James <br />/nickserv info James all<br /><br />* LIST<br />Explanation:  Lists all registered nicknames which match a set of parameters, in nick!user@host format.  Nicks with the SET PRIVATE option ON will not be displayed.  Note that a pattern preceding with '#' specifies the range.<br />Syntax:  /Nickserv LIST pattern<br />Examples: /nickserv list *!haha@joke.com = Lists all nicks owned by haha@joke.com<br />/nickserv list *bot*!*@* = Lists all registered nicks with 'bot' in their names. <br />/nickserv list *!*@*.ick.org = Lists all nicks owned by users in the ick.org domain.<br />/nickserv list #50-100 = Lists the 50th through 100th nick in the current list order.<br /><br />* ALIST<br />Explanation:  Lists all channels you have access (ops of any kind) on.  Optionally, you can specify a level in XOP or ACCESS format (see ChanServ Help for more info).  The resulting list will only include channels where you have the specified level of access requested.<br />Syntax:  /NickServ ALIST [Level]<br />Examples:  /nickserv alist founder = Lists all channels you have Founder access in.<br />/nickserv alist aop = Lists all channels where you have AOP access or greater.<br />/nickserv alist 10 = Lists all channels where you have level 10 (SOP) access or greater.<br />Note:  Channels that have no expiration will have a '!' before the channel name.  <br /><br />* GLIST<br />Explanation:  This lists all nicks in your Group.<br />Syntax: /NickServ GLIST<br />Example:  /nickserv glist<br /><br />* STATUS<br />Explanation:  This command used on a nick will return the nickname as well as a code from 0 to 3.  If no nickname is specified, your own Status will be given.<br />0 - no such user is online or the nickname is not registered.<br />1 - user is not recognized as the nickname's owner.<br />2 - user recognized as the nickname's owner via access list only.<br />3 - user recognized as the nickname's owner via password identification.<br />Syntax:  /NickServ STATUS nickname<br />Example: /nickserv status JD<br />Note:  You can request more than one nick at a time with this command; up to 16.<br />Example: /nickserv status JD Mark Lassie_is_a_Dog What <br />This will return a status code for JD, Mark, Lassie_is_a_Dog and What, on individual lines.<br /> Nickserv Commands<br /><br />Nickserv enables a user to register a nick in order to own the nick and have the benefits that come with it.  There are quite a few functions and options that come with registering a nick to include being able to be auto-opped in a channel, receiving and sending memos, registering your own channel and grouping other nicks.  The list provided below gives the commands for NickServ with detailed explanations and examples.  You may also find quick support by typing '/nickserv help' in your status window which will give you this list to peruse on SorceryNet.<br /><br /><br />* REGISTER<br />Explanation: This command will register a nick to you.  Your e-mail is used to send you out an authentication code for confirming your nick registry and may be used later to help you recover your nick if you lose your password.  Make sure to put a real e-mail in.  All e-mails are confidential and for your use only.  Nicks are automatically set to be hidden from other users who may use INFO on a nick.  Nick registrations expire after 30 days if not identified to.  See 'Identify' for further information.  Do not give out your password to anyone and make the password something that is not easily thought up by other users.  <br />Syntax: /NickServ REGISTER password e-mail<br />Example: /nickserv register vegetable cornyemail@blankmail.net <br />Note:  Passwords that you make are case sensitive and there can be no spaces between the letters.  Also, do not put any symbols around the e-mail such as { } or [ ].  The e-mail will be incorrect if you do so.<br /><br />* CONFIRM<br />Explanation:  You will receive an e-mail after you register your nick.  Go to the e-mail you registered your nick with and open the letter from 'services'.  A line will read like this:  [Please type " /msg NickServ confirm cLqc6RpR62" into your IRC client to complete the registration.] Copy or type in /msg nickserv confirm [number given] to your IRC client window while being in the appropriate nick and hit Enter.  This will finish your registration process.<br />Example: /nickserv confirm cLqc6RpR62<br /><br />* ENTERCODE <br />Explanation:  This allows you to enter the passcode you received after losing a password and going to an Oper in #sorcery to have a new code sent to you. Be in the nick before using this command.<br />Syntax:  /NickServ ENTERCODE passcode<br />Example:  /nickserv entercode cl23KHGki3<br /><br />* GROUP<br />Explanation: This command allows a new nickname you have selected to join a registered nickname's group.  The password after this will be the same as any other nick in the Group.  You will also be able to share your dominant nick's configuration, memos, channel privileges and more.  Prior to using this command, identify to your target nick by changing to the target nick and doing the Identify command.  After, change back to the nick you want to Group.  You can only be in one group at a time and group merging is not possible.  If you register another nick, you will need to drop it to put it in the group.  <br />Syntax:  /NickServ GROUP target password<br />Example: nick target = Kenny  password for nick registered = peanutbutter<br />/nickserv group Kenny peanutbutter<br /><br />* IDENTIFY<br />Explanation:  After registering a nick, you will want to identify to it in order to keep the nick registered to you.  Failure to do so will cause the nick to drop after 30 days, making it available again to other users.  You also may not be able to use the nick if you do not identify to it within a minute if your settings for the nick are set that way.  The network does this automatically so if you wish to change the options, you will need to adjust this yourself.  Identifying to your nick also grants you the ability to use the privileges that come with a registered nick such as channel ops and access to your memos.  The password is the same one that you registered your nick with.  <br />Syntax:  /NickServ IDENTIFY password<br />Example:  Password = pepsi<br />/nickserv identify pepsi<br />Shortcut:  /ns id pepsi<br /><br />* LOGOUT<br />Explanation:  This reverses the effect of the Identify command, but will not ask you to re-identify to the nick, so long as you do not lose your connection or change nicks.<br />Syntax:  /NickServ LOGOUT<br />Example:  /nickserv logout<br /><br />* DROP<br />Explanation:  This command will drop the registered nickname from the NickServ database.  A nick that has been dropped is available for anyone to register.  You will need to have identified to your nick prior to using this command.  <br />Syntax:  /NickServ DROP nickname<br />Example: nick is Junkie<br />/nickserv drop Junkie<br /><br />* ACCESS<br />Explanation:  This command can modify or display the access list for your nick.  It is the list of addresses that will automatically be recognized by NickServ so that you have access to use the nick.  If you want to use the nick from a different address, you need to use the Identify command for NickServ to recognize you.<br />Syntax:  /NickServ ACCESS ADD mask<br />/NickServ ACCESS DEL mask<br />/NickServ ACCESS LIST<br />Examples:  <br />/nickserv access add Jen@*.blah.com = Allows access to the ident user Jen when connecting from any machine in the blah.com domain.<br />/nickserv access del Jen@*.blah.com = Removes the access granted by the above command.<br />/nickserv access list = Gives you the current access list.<br /><br />* SET<br />Explanation:  There are various options you can set for your nick and registry. Each option listed below will have further instructions here or you can use /nickserv help set option.  You must be Identified to your nick before you can use these commands.<br />Syntax:  /NickServ SET option parameters<br />Options:<br />DISPLAY - Changes the display nick of your Group in Services.<br />PASSWORD - This allows you to change your password.<br />LANGUAGE - Sets the language that Services will use when sending messages to you.<br />URL - Place in a url which will be associated with your nickname.<br />EMAIL - Sets an email to be associated with your nick and allows you to alter it if your email you registered with has changed.<br />ICQ - Allows you to place an ICQ number in to be viewed by others.<br />GREET - Place a greet message to go with your nickname.<br />KILL - Allows you to turn on the nick protection timer or disengage it. Also allows you to set the timer in which a nick will be forcibly changed.<br />SECURE - Turn nickname security on or off. This is the prompt to change your nick. <br />PRIVATE - Prevents your nickname from appearing in a /nickserv list used.<br />HIDE - Gives the option of hiding email, status, usermask, last quit message and whether you are online or not.<br />MSG - Sets how Services will communicate with you. If this is set 'on', Services will message you instead of sending Notices.<br />AUTOOP - On or off. This allows ChanServ to op you automatically when you enter a channel you have autoops in if set to 'on.  If 'off', ChanServ will not op you automatically.<br /><br />* SET DISPLAY<br />Explanation:  This changes the display used to refer to your nickname Group in Services.  The new display must be a nick within your Group and in order to change it, you must be in the nickname and identified to it before using this command.  When someone asks for info on a nick, the dominant display nickname will show up.<br />Syntax:  /NickServ SET DISPLAY new-Display<br />Example: /nickserv set display Claw<br /><br />* SET PASSWORD<br />Explanation:  This allows you to change your password.  You must identify to the nick with the former password before you can do this command.<br />Syntax:  /NickServ SET PASSWORD new-password<br />Example: /nickserv set PASSWORD speeddemon23<br /><br />* SET LANGUAGE<br />Explanation:  This changes the language that Services will use when sending you messages. <br />Syntax:  /NickServ SET LANGUAGE number<br />The following is a list of the supported languages and the number.<br />1 = English<br />2 = Francais (French)<br />3 = Deutsch (German)<br />4 = Italiano (Italian)<br />5 = Português (Portuguese)<br />6 = Español (Spanish)<br />7 = Türkçe (Turkish)<br />8 = Catala (Catalan)<br />9 = ÅëëçíéêÜ (Greek)<br />10 = Nederlands (Dutch)<br />11 = Ðóññêèé (Russian)<br />12 = Magyar (Hungarian)<br />13 = Polski (Polish)<br />Example:  /nickserv set language 4 = for Italian.<br /><br />* SET URL<br />Explanation:  This will associate a URL with your nickname and can be viewed when someone does an Info request on your nick.<br />Syntax:  /NickServ SET URL url<br />Example:  /nickserv set url http:www.wherever.com<br /><br />* SET EMAIL<br />Explanation:  Sets an E-mail address to your nickname.  This address can be displayed when someone uses the Info command.  You can also hide it by doing the SET HIDE command.  Setting an email allows you to recover a forgotten password.<br />Syntax:  /NickServ SET EMAIL address<br />Example:  /nickserv set email blahsomething@gmallz.com<br /><br />* SET ICQ<br />Explanation:  Puts in an ICQ number that will show up when someone uses an INFO command on your nick.<br />Syntax:  /NickServ SET ICQ number<br />/example: /nickserv set ICQ 2342392333<br /><br />* SET GREET<br />Explanation:  This will set your nick up with a message that will be displayed when joining a channel that has the GREET option enabled, provided you have the necessary op access.  <br />Syntax: /NickServ SET GREET message<br />Example: /nickserv set GREET I have arrived. All rejoice and give offerings.<br /><br />* SET KILL<br />Explanation: This turns the automatic protection for your nick on or off and also enables you to change the timer before NickServ will forcibly remove the nick from someone.  QUICK allows only 20 seconds for someone to change nicks or Identify instead of the usual 60 seconds.  IMMED will force the user's nick to be changed immediately without being warned first.  It is -strongly- suggested that you do not use the IMMED option if you are unfamiliar with it, as it will prevent even the nick owner from getting the nick if Access is not set correctly.  There is no remote identifying at this time.<br />Syntax:  /NickServ SET KILL {ON | QUICK | IMMED | OFF} <br />Example:  /nickserv set kill on = sets kill on<br />/nickserv set kill off = turns kill off<br />/nickserv set quick on = sets the time to 20 seconds before the nick is forcibly removed.<br /><br />* SET SECURE<br />Explanation:  This turns NickServ's security features on or off for your registered nick.  With SECURE set ON, you must enter your password before you will be recognized as the owner of the nick, regardless of whether you have set your address on the ACCESS list or not.  However, if you are on the ACCESS list, NickServ will not auto-kill you, regardless of the setting of the KILL option.  Setting this to OFF will remove the prompt to identify to NickServ, allowing anyone to use the nick, though it will give a message that the nick is registered to someone else.<br />/Syntax:  /NickServ SET SECURE {ON | OFF}<br />Examples: /nickserv set secure on<br />/nickserv set secure off<br /><br />* SET PRIVATE<br />Explanation:  If set to ON, your nickname will not appear in a nickname list generated with NickServ's LIST command.  With PRIVATE set off, users may see your nick with the LIST command.  Anyone who knows your nickname, whether this is set on or off, can still get information on the nick by using the INFO command.<br />Syntax:  /NickServ SET PRIVATE {ON | OFF}<br />Examples: /nickserv set private on<br />/nickserv set private off<br /><br />* SET HIDE<br />Explanation: This allows certain information that you do not want displayed, when someone uses a NickServ INFO command on your nick, to be hidden.  <br />Syntax: /NickServ SET HIDE [EMAIL | STATUS | USERMASK | QUIT] {ON | OFF}<br />Examples:  /nickserv set hide email on = hides email. /nickserv set hide email off = allows it to appear in INFO checks.<br />/nickserv set hide status on or off = shows Services access status or not.<br />/nickserv set hide usermask on or off = hides last seen user@hostmask info, or not if off.<br />/nickserv set hide quit on or off = hides or reveals the last quit message you had when leaving SorceryNet.<br />Note:  Hostmasking is done on SorceryNet whether the usermask option is set on or off.<br /><br />* SET MSG<br />Explanation:  This allows you to select the way Services will be communicating with you.  With SET MSG ON, Services will send you messages.  With this option off (standard), Services will send you Notices instead.<br />Syntax:  /NickServ SET MSG {ON | OFF}<br />Examples: /nickserv set msg on<br />/nickserv set msg off<br /><br />* UPDATE<br />Explanation:  This updates your current status.  It will check for new memos, sets needed chanmodes (ModeonID) and updates your userflags such as lastseentime, etc.<br />Syntax:  /NickServ UPDATE<br />Example: /nickserv update<br /><br />* RECOVER<br />Explanation:  Using this command allows you to recover your nickname if someone else has taken it and you have the KILL option set OFF.  It does the same thing that NickServ does automatically when the KILL option is on.  If you use this option, NickServ brings a fake user online with the apprehended nickname so the other user is forcibly disconnected.  It will remain online for 60 seconds to ensure the other user does not just reconnect immediately so that you have time to reclaim your nick.  If you wish to get the nick back sooner than 60 seconds, you can use the RELEASE command.<br />Syntax: /NickServ RECOVER nickname {password}<br />Example: /nickserv recover Suzy saywhat23<br /><br />* RELEASE<br />Explanation:  Use of this command instructs NickServ to release the hold on your nickname that is caused by automatic KILL protection or by use of the RECOVER command.  Usually the nick will be held by NickServ for 60 seconds but this allows you to cut the time to immediate.<br />Syntax: /NickServ RELEASE nickname {password}<br />Example: /nickserv release Suzy saywhat23<br /><br />* GHOST<br />Explanation: Occasionally, your internet connection is cut off abruptly but IRC may recognize you as still being online.  You can acquire your nick back by using this command, which will terminate "ghost's" connection.  <br />Syntax:  /NickServ GHOST nickname {password}<br />Example:  /nickserv ghost Suzy saywhat23<br /><br />* INFO<br />Explanation:  This displays information about the target nickname such as the owner of the nick, last seen address and time on and some nick options such as URLs set.  To hide some of this information, a user may use the SET HIDE command.  If you are identified to the nick you are looking up information on, you will be shown all of the information; regardless of whether you have set it to Hide or not.<br />Syntax:  /NickServ INFO nickname = provides some info.  You will see the option to get more information with 'all'<br />Syntax:  /NickServ INFO nickname ALL = provides all of the information possible to be collected on the nick.<br />Example:  /nickserv info James <br />/nickserv info James all<br /><br />* LIST<br />Explanation:  Lists all registered nicknames which match a set of parameters, in nick!user@host format.  Nicks with the SET PRIVATE option ON will not be displayed.  Note that a pattern preceding with '#' specifies the range.<br />Syntax:  /Nickserv LIST pattern<br />Examples: /nickserv list *!haha@joke.com = Lists all nicks owned by haha@joke.com<br />/nickserv list *bot*!*@* = Lists all registered nicks with 'bot' in their names. <br />/nickserv list *!*@*.ick.org = Lists all nicks owned by users in the ick.org domain.<br />/nickserv list #50-100 = Lists the 50th through 100th nick in the current list order.<br /><br />* ALIST<br />Explanation:  Lists all channels you have access (ops of any kind) on.  Optionally, you can specify a level in XOP or ACCESS format (see ChanServ Help for more info).  The resulting list will only include channels where you have the specified level of access requested.<br />Syntax:  /NickServ ALIST [Level]<br />Examples:  /nickserv alist founder = Lists all channels you have Founder access in.<br />/nickserv alist aop = Lists all channels where you have AOP access or greater.<br />/nickserv alist 10 = Lists all channels where you have level 10 (SOP) access or greater.<br />Note:  Channels that have no expiration will have a '!' before the channel name.  <br /><br />* GLIST<br />Explanation:  This lists all nicks in your Group.<br />Syntax: /NickServ GLIST<br />Example:  /nickserv glist<br /><br />* STATUS<br />Explanation:  This command used on a nick will return the nickname as well as a code from 0 to 3.  If no nickname is specified, your own Status will be given.<br />0 - no such user is online or the nickname is not registered.<br />1 - user is not recognized as the nickname's owner.<br />2 - user recognized as the nickname's owner via access list only.<br />3 - user recognized as the nickname's owner via password identification.<br />Syntax:  /NickServ STATUS nickname<br />Example: /nickserv status JD<br />Note:  You can request more than one nick at a time with this command; up to 16.<br />Example: /nickserv status JD Mark Lassie_is_a_Dog What <br />This will return a status code for JD, Mark, Lassie_is_a_Dog and What, on individual lines.<br /> General FAQ 2010-08-30T06:50:09Z 2010-08-30T06:50:09Z http://www.sorcery.net/index.php?option=com_content&view=article&id=246:general&catid=105:faqs&Itemid=78 SorceryNet jc@sorcery.net <p>Frequently Asked Questions<br /><br /><br />This section is made as a quick tutorial for frequently asked questions on how to use the Services we provide.  It, by no means explains all of the functions available to you as a user, but will get you started.  For more in depth explanations and further options, please check out the Help area of this site or feel free to drop into #help and we will be happy to assist you.  You can also browse through the commands yourself on SorceryNet.<br /><br /><br />TERMINOLOGY<br /><br />There are quite a few terms used on IRC that may be different from other chat services which you are used to.  Here is a list of terms to acclimate yourself with while using Sorcery.net.  <br /><br />Akick - A 'permanent' ban from a channel until it is removed from a list by an op.  <br /><br />Ban - If a ban is set on a person from a channel, the user can no longer enter the channel until it is lifted or until the channel is empty.<br /><br />Channel - This is sometimes referred to as a 'room'.  You must be in a channel to talk to others. <br /><br />Hostmask - This is the info you get after your nick.  Pete@27a9d71d.twcma.rep.123455.com.hmsk.  'Pete' is the alias.  After the @ is the hostmask.  <br /><br />IRC - Internet Relay Chat.  <br /><br />IRCop - IRCops help maintain the network and assist users with troublemakers and with understanding commands etc on the network.  You can speak to IRCops and get assistance in #help.<br /><br />Kick - A person can kick another from a channel, meaning that user was removed and can rejoin.<br /><br />Moderation - If the channel is set +m, anyone not voiced or opped will be unable to converse in the channel.<br /><br />Nick - A nickname.  The name you choose to use while chatting. <br /><br />Op - A person in the channel who has a @ by his/her name.  This person is either in charge of the channel or at least has the ability to do some commands in the room such as kicking, banning and moderating a channel.<br /><br />HalfOp - Uses the % symbol.  Halfops are between a voice and Op, having some limited power to voice people who join or kick/ban those who are voiced or not voiced.  <br /><br />Voice - A person with a +v by his/her nick is voiced.  This implies that if a channel is moderated, the individual can still chat and be seen by others.   <br /> <br /><br />You can see further terminology in the Glossary.<br /><br /><br />Pertaining to the Server/Network<br /><br />Question:  I'm being portscanned when I connect, why?<br />Answer:  Our servers check if your computer is running an open proxy. This is just an automated check done for every connection. There's nothing to worry about.<br /><br />Question:  I was klined from the server for running an open proxy or having a compromised IP or Tor.<br />Answer:  We use a black list and IPs that match will be automatically banned from the server.  If you wish to chat here, you will need to follow the directions the kline message gives you to do so.  If it says to email kline@sorcery.net, do so with the complete message.<br /><br />Question:  I was klined for being an abusive user, whether it was me or not.  How can I get back on Sorcery?<br />Answer:  Email kline@sorcery.net with the complete kline message you receive.  If you are not the person in which the kline was meant for, please indicate so in your email.  If you are the user who did something against SorceryNet policy, the kline staff will make a decision as to whether to continue the kline or not.  Whatever you do, do not ban evade or else the penalty may be increased.  If you had a faulty script or something of that nature, fix the problem and then email kline@sorcery.net indicating you have done so and you will be permitted back onto the network.  Friends may come into #help to speak to an IRCop over klines but the situation may be remedied sooner by emailing the kline staff.  They are prompt and generally get back with people on the same day or the next. <br /><br />Question:  Does SorceryNet support SSL?<br />Answer: Yes, we do.<br /><br />Question:  Does SorceryNet support ipv6?<br />Answer:  Yes, we do on specific servers.  <br /><br /><br />Pertaining to NICKS<br /><br />Question:  How do I change nicks?<br />Answer:  /nick newnick<br />Example: /nick Pete<br />Note:  This will change your nick to Pete, if it is available.  If a nick comes up as not available, that means someone else has registered it and/or it is in use currently.  If you receive a message to change the nick or you will lose it, this means that someone else has registered the nick, so quickly just do the command again with a new nickname and sooner or later you will find a free nick.<br /><br />Question:  How can I register a nick?<br />Answer:  Get into the nick you wish to register. Then use this command: /nickserv register passwordhere <br />Example: If your password you choose is 'pepsi', the command should look like this: <br />/nickserv register pepsi<br />Note:  Make sure to -not- put in your nick in with the command.  Just add a password as Nickserv will know you are registering the nick you are in at the time you use the command.  After registering, you must identify to your nick at least once every 30 days or it will become available to others again.  Passwords are case-sensitive.<br /><br />Question:  How do I identify to a nick?<br />Answer:  Be in the nick you registered.  You will note that you have about 30 seconds to identify by the prompt.  Put in this command: <br />/nickserv id password-you-chose<br />Example:  Going by the example above, with the password being 'pepsi', /nickserv id pepsi<br /><br />Question:  How do I drop a currently registered nick?<br />Answer:  If you wish to drop a nick you own, use /nickserv drop while in the nick.  Of course, you will have to be identified to the nick before this will work.  Once done, this makes your nick available to other users.<br /><br />Question:  Do you have nick 'grouping'? <br />Answer:  Yes, we do.  You may group nicks instead of registering each individual one, which will attach the new nick to the registered nick you use.  While in the new nick you wish to group, do this command: /nickserv group target(Your registered nick) password(the password you registered the target nick under).<br /><br />Question:  Someone stole my nick and I did not register it prior or it dropped due to not identifying on time (within 25 days).  What do I do?<br />Answer:  For the majority of cases, you are just out of luck.  Nickserv is there for you so that you can claim a nick and whether you have used the nick for 3 years or 3 days, if it is not registered, you are putting it up on the market for anyone to use or take.  All we can suggest is to message the person and ask politely if the user will relinquish the nick.  If not, you will need to wait for the nick to drop so that you can have it again and choose a new nick in the mean time.  If someone is being malicious and taking nicks just to be cruel, you may come to #help and the IRCops can determine whether it is within the rules to release the nicks in question or not.  <br /><br />Question:  Someone stole my nick (or channel) and changed the password?  What can I do?<br />Answer:  Ask for the nick back and if denied, come to #help and report the person to an IRCop.  It may take a bit of time but a check can be done to determine whether the nick was stolen or not.  If it was, it will be returned to you.  We do strongly suggest that you do not give your password out to -anyone- and the same applies for a registered channel.  If you do so, you may be on your own. <br /><br />Question:  How long can my nick be?<br />Answer: It was changed from 17 to 24 characters.  <br /><br /><br />Pertaining to OTHER USERS<br /><br /><br />Question:  How can I find out if a nick is registered to someone without having to try to use the nick?<br />Answer:  You can use this command:  /nickserv info nick and this will let you know if the nick is available or it is already taken.  This also Tells you how long the nick has been registered and when it was last used. <br />Example: /nickserv info Pete<br /><br />Question:  How do I find out if someone is on the network currently?<br />Answer:  Use the /whois nick command.  If the person is not online you will receive a message of 'no such nick/channel'.  If the person is online, you will get back a response with the person's masked hostmask and the channels the person is currently in that are public.  <br /><br />Question:  How do I kick and/or ban someone out of my channel?<br />Answer:  In most IRC clients, you can highlight the user's name in the nick list and then right click.  Go to 'Commands' and hit the Kick option.  Below the Kick option, there should be a ban option you can use if you wish for the person to not be able to return to the channel.  You must be opped to do this command.  If you do not have this option, you can use chanserv to akick the person (a permanent ban until you remove it) or you can set mode +b manually. (/mode #channel +b user)<br /><br />Question:  How do I ignore someone?<br />Answer:  If a user is harassing you or you just want to not receive any PMs from the person, or see his/her comments in the channel you both are in, you can use this function.  The command is /ignore nick<br />Example:  /ignore Pete <br /><br />Question:  How do I remove an Ignore I have set?<br />Answer:  /unignore nick works in most cases.  If this does not work, you may have to go into your Address Book and find 'Control'.  In this area, you can remove the nick.  Some clients may have other ways of deleting ignored nicks so you may have to use a search engine to find the answer.  Most irc client sites are pretty good at providing such answers, but if you cannot find out, come into #help and we will try to assist you.<br /><br /><br /><br />Pertaining to CHANNELS<br /><br />Question:  How do I find a channel to join?<br />Answer:  Do the command: /list.  This will bring up all of the non-secret channels on the network.  You can then peruse through the list and see their topics.  You can also browse the site here and see some channels listed.  If you are interested in rpgs, take a look in #rpg-hub.<br />Example:  /list<br /><br />Question:  How do I join a channel?<br />Answer:  If the channel is open to be joined by anyone, you may simply type /join #channel.<br />Example:  /join #help<br /><br />Question:  How do I register a channel?<br />Answer:  Be in the channel you wish to register and be an op, which implies you have a @ by your nick.  If you and others are in the available channel and someone else has ops or no one does, this command will not work.  Simply ask others to leave, then part and rejoin quickly so that you will be the first in the channel.  After, use the command:  /chanserv register #channel password description.  <br />Example:  The channel name for the example will be #green.  The password will be 'oval'.  <br />/chanserv register #green oval A channel about green things.<br />Note:  A channel will drop if the Founder fails to identify to a channel every 30 days.  If a Founder is gone for 30 days, the channel will drop or pass onto a successor, if the Founder names one. <br /><br />Question:  Why won't Chanserv recognize me when I enter a channel I have auto-ops in?<br />Answer:  You need to be identified with Nickserv prior to entering the channel.  Simply part the channel and identify to Nickserv and re-enter the channel.<br /><br />Question:  Someone banned me from a channel for no good reason.  What can be done?<br />Answer:  Channel founders and the ops they assign can ban someone from their channel for any reason at all, whether you could be considered harassing or not.  Sorcery IRCops will not interfere in this as it is the right of any founder to set up his/her channel so long as it follows SorceryNet guidelines.  The best thing we can suggest is to private message the founder or an op of the channel itself and ask to be allowed in.  If you are denied or there is no response, move on.  There are plenty of other channels on SorceryNet and hopefully you will find a more welcoming room elsewhere.  <br /><br />Question:  A user is ban evading and continues to return to my channel.  How do I get rid of him/her?<br />Answer:  If you have set any bans you have set for the individual, do not remove them and come to #help for assistance from an IRCop.  If you had set akicks (/chanserv akick #channel person's-ident reason), put in the person's nick or some identifying message as to who the user is so that the IRCops can see your efforts.  If the individual is a ban evader, this goes against SorceryNet policy and IRCops will help to ensure the ban evader no longer joins your channel.<br /><br />Question:  Many bots are joining my room and flooding or spamming.  What can I do?<br />Answer:  You can report any bots/clones that are attacking your room by joining #help and we will be happy to assist you.  However, here are some helpful things you can do for your room meanwhile.  First step, set mode +i.  (/mode #channel +i)  This sets the channel to invite only, which implies that users attempting to join your channel will fail until this is removed.  Members of the channel can message an op and an op can invite them in or drop the +i.  Next step if you wish, try setting a limit on what number of people can join your channel by doing +l (/mode #channel +l number). Another way to handle it is to voice the members of your channel and then set the channel to +m which moderates the channel (/mode #channel +m).  Anyone not voiced cannot speak in the channel but they can join and part.  There are other useful modes, which you can explore, listed under Channel Modes.  Feel free to explore the options to set up your channel as you would like.  <br /><br />Question:  What are the channel levels that can be assigned to ops?<br />Answer:  Below is the rough outline, whether you use number levels to assign or set via the level label.  For more information, please see /chanserv help access and/or /chanserv help set #chan xop to choose which option you would prefer to use in auto-opping users.<br />Founder - Level 15 = The channel founder is the owner of the channel.  The channel founder can do any commands available.<br />SOP - Level 10 or higher = The channel SOP or Super Op can set akicks and auto-op members, on top of other op functions for lower ops.<br />AOP - Level 5 up to 9 = Auto-Op.  A person can ban, kick, set temporary modes to a channel, change topics and VOP or HOP users as well as other simple functions.<br />HOP - Level 4 = HalfOp. The user can voice the channel, moderate and invite, as well as ban users below Level 4 and can change topics.<br />VOP - Level 3 = Voice.  The user is voiced so that if the channel is moderated (+m), he or she can still speak.<br />0 = The user has no level and is not opped in any way in the channel.<br />&lt;0 = The user cannot be auto-opped in the channel.<br /><br /><br /><br />Pertaining to MEMOS<br /><br />Question:  Why can I not send a memo to another user?<br />Answer:  You must be registered and identified to your nick to send memos.  Also, that user must have a registered nick to receive memos. <br /><br />Question:  How do I send a memo to another user?<br />Answer:  If the criteria above is met, type /memoserv send nick your message.  <br />Example:  If the user's nick is Carl and your message is 'How are you doing?', it would look like this: <br />/memoserv send Carl How are you doing? <br /><br />Question:  How do I read a memo from another user?<br />Answer:  The command is /memoserv read #.  If you have received a memo from someone and it is your first, type in:<br />Example:  /memoserv read 1<br /><br /><br /><br />For more information on these commands and others, you can be on SorceryNet and type in: <br />/nickserv help <br />/chanserv help<br />/memoserv help<br />/gameserv help <br />/botserv help <br /><br />SHORTCUTS<br /><br />If you wish to, in most clients, you can shorten some of the Services command words.<br /><br />/ns = /nickserv<br />/cs = /chanserv<br />/ms = /memoserv<br />/gs = /gameserv<br />/bs = /botserv<br /><br /><br />You may also feel free to check out the information in more detail on this website or join #help for further assistance.</p> <p>Frequently Asked Questions<br /><br /><br />This section is made as a quick tutorial for frequently asked questions on how to use the Services we provide.  It, by no means explains all of the functions available to you as a user, but will get you started.  For more in depth explanations and further options, please check out the Help area of this site or feel free to drop into #help and we will be happy to assist you.  You can also browse through the commands yourself on SorceryNet.<br /><br /><br />TERMINOLOGY<br /><br />There are quite a few terms used on IRC that may be different from other chat services which you are used to.  Here is a list of terms to acclimate yourself with while using Sorcery.net.  <br /><br />Akick - A 'permanent' ban from a channel until it is removed from a list by an op.  <br /><br />Ban - If a ban is set on a person from a channel, the user can no longer enter the channel until it is lifted or until the channel is empty.<br /><br />Channel - This is sometimes referred to as a 'room'.  You must be in a channel to talk to others. <br /><br />Hostmask - This is the info you get after your nick.  Pete@27a9d71d.twcma.rep.123455.com.hmsk.  'Pete' is the alias.  After the @ is the hostmask.  <br /><br />IRC - Internet Relay Chat.  <br /><br />IRCop - IRCops help maintain the network and assist users with troublemakers and with understanding commands etc on the network.  You can speak to IRCops and get assistance in #help.<br /><br />Kick - A person can kick another from a channel, meaning that user was removed and can rejoin.<br /><br />Moderation - If the channel is set +m, anyone not voiced or opped will be unable to converse in the channel.<br /><br />Nick - A nickname.  The name you choose to use while chatting. <br /><br />Op - A person in the channel who has a @ by his/her name.  This person is either in charge of the channel or at least has the ability to do some commands in the room such as kicking, banning and moderating a channel.<br /><br />HalfOp - Uses the % symbol.  Halfops are between a voice and Op, having some limited power to voice people who join or kick/ban those who are voiced or not voiced.  <br /><br />Voice - A person with a +v by his/her nick is voiced.  This implies that if a channel is moderated, the individual can still chat and be seen by others.   <br /> <br /><br />You can see further terminology in the Glossary.<br /><br /><br />Pertaining to the Server/Network<br /><br />Question:  I'm being portscanned when I connect, why?<br />Answer:  Our servers check if your computer is running an open proxy. This is just an automated check done for every connection. There's nothing to worry about.<br /><br />Question:  I was klined from the server for running an open proxy or having a compromised IP or Tor.<br />Answer:  We use a black list and IPs that match will be automatically banned from the server.  If you wish to chat here, you will need to follow the directions the kline message gives you to do so.  If it says to email kline@sorcery.net, do so with the complete message.<br /><br />Question:  I was klined for being an abusive user, whether it was me or not.  How can I get back on Sorcery?<br />Answer:  Email kline@sorcery.net with the complete kline message you receive.  If you are not the person in which the kline was meant for, please indicate so in your email.  If you are the user who did something against SorceryNet policy, the kline staff will make a decision as to whether to continue the kline or not.  Whatever you do, do not ban evade or else the penalty may be increased.  If you had a faulty script or something of that nature, fix the problem and then email kline@sorcery.net indicating you have done so and you will be permitted back onto the network.  Friends may come into #help to speak to an IRCop over klines but the situation may be remedied sooner by emailing the kline staff.  They are prompt and generally get back with people on the same day or the next. <br /><br />Question:  Does SorceryNet support SSL?<br />Answer: Yes, we do.<br /><br />Question:  Does SorceryNet support ipv6?<br />Answer:  Yes, we do on specific servers.  <br /><br /><br />Pertaining to NICKS<br /><br />Question:  How do I change nicks?<br />Answer:  /nick newnick<br />Example: /nick Pete<br />Note:  This will change your nick to Pete, if it is available.  If a nick comes up as not available, that means someone else has registered it and/or it is in use currently.  If you receive a message to change the nick or you will lose it, this means that someone else has registered the nick, so quickly just do the command again with a new nickname and sooner or later you will find a free nick.<br /><br />Question:  How can I register a nick?<br />Answer:  Get into the nick you wish to register. Then use this command: /nickserv register passwordhere <br />Example: If your password you choose is 'pepsi', the command should look like this: <br />/nickserv register pepsi<br />Note:  Make sure to -not- put in your nick in with the command.  Just add a password as Nickserv will know you are registering the nick you are in at the time you use the command.  After registering, you must identify to your nick at least once every 30 days or it will become available to others again.  Passwords are case-sensitive.<br /><br />Question:  How do I identify to a nick?<br />Answer:  Be in the nick you registered.  You will note that you have about 30 seconds to identify by the prompt.  Put in this command: <br />/nickserv id password-you-chose<br />Example:  Going by the example above, with the password being 'pepsi', /nickserv id pepsi<br /><br />Question:  How do I drop a currently registered nick?<br />Answer:  If you wish to drop a nick you own, use /nickserv drop while in the nick.  Of course, you will have to be identified to the nick before this will work.  Once done, this makes your nick available to other users.<br /><br />Question:  Do you have nick 'grouping'? <br />Answer:  Yes, we do.  You may group nicks instead of registering each individual one, which will attach the new nick to the registered nick you use.  While in the new nick you wish to group, do this command: /nickserv group target(Your registered nick) password(the password you registered the target nick under).<br /><br />Question:  Someone stole my nick and I did not register it prior or it dropped due to not identifying on time (within 25 days).  What do I do?<br />Answer:  For the majority of cases, you are just out of luck.  Nickserv is there for you so that you can claim a nick and whether you have used the nick for 3 years or 3 days, if it is not registered, you are putting it up on the market for anyone to use or take.  All we can suggest is to message the person and ask politely if the user will relinquish the nick.  If not, you will need to wait for the nick to drop so that you can have it again and choose a new nick in the mean time.  If someone is being malicious and taking nicks just to be cruel, you may come to #help and the IRCops can determine whether it is within the rules to release the nicks in question or not.  <br /><br />Question:  Someone stole my nick (or channel) and changed the password?  What can I do?<br />Answer:  Ask for the nick back and if denied, come to #help and report the person to an IRCop.  It may take a bit of time but a check can be done to determine whether the nick was stolen or not.  If it was, it will be returned to you.  We do strongly suggest that you do not give your password out to -anyone- and the same applies for a registered channel.  If you do so, you may be on your own. <br /><br />Question:  How long can my nick be?<br />Answer: It was changed from 17 to 24 characters.  <br /><br /><br />Pertaining to OTHER USERS<br /><br /><br />Question:  How can I find out if a nick is registered to someone without having to try to use the nick?<br />Answer:  You can use this command:  /nickserv info nick and this will let you know if the nick is available or it is already taken.  This also Tells you how long the nick has been registered and when it was last used. <br />Example: /nickserv info Pete<br /><br />Question:  How do I find out if someone is on the network currently?<br />Answer:  Use the /whois nick command.  If the person is not online you will receive a message of 'no such nick/channel'.  If the person is online, you will get back a response with the person's masked hostmask and the channels the person is currently in that are public.  <br /><br />Question:  How do I kick and/or ban someone out of my channel?<br />Answer:  In most IRC clients, you can highlight the user's name in the nick list and then right click.  Go to 'Commands' and hit the Kick option.  Below the Kick option, there should be a ban option you can use if you wish for the person to not be able to return to the channel.  You must be opped to do this command.  If you do not have this option, you can use chanserv to akick the person (a permanent ban until you remove it) or you can set mode +b manually. (/mode #channel +b user)<br /><br />Question:  How do I ignore someone?<br />Answer:  If a user is harassing you or you just want to not receive any PMs from the person, or see his/her comments in the channel you both are in, you can use this function.  The command is /ignore nick<br />Example:  /ignore Pete <br /><br />Question:  How do I remove an Ignore I have set?<br />Answer:  /unignore nick works in most cases.  If this does not work, you may have to go into your Address Book and find 'Control'.  In this area, you can remove the nick.  Some clients may have other ways of deleting ignored nicks so you may have to use a search engine to find the answer.  Most irc client sites are pretty good at providing such answers, but if you cannot find out, come into #help and we will try to assist you.<br /><br /><br /><br />Pertaining to CHANNELS<br /><br />Question:  How do I find a channel to join?<br />Answer:  Do the command: /list.  This will bring up all of the non-secret channels on the network.  You can then peruse through the list and see their topics.  You can also browse the site here and see some channels listed.  If you are interested in rpgs, take a look in #rpg-hub.<br />Example:  /list<br /><br />Question:  How do I join a channel?<br />Answer:  If the channel is open to be joined by anyone, you may simply type /join #channel.<br />Example:  /join #help<br /><br />Question:  How do I register a channel?<br />Answer:  Be in the channel you wish to register and be an op, which implies you have a @ by your nick.  If you and others are in the available channel and someone else has ops or no one does, this command will not work.  Simply ask others to leave, then part and rejoin quickly so that you will be the first in the channel.  After, use the command:  /chanserv register #channel password description.  <br />Example:  The channel name for the example will be #green.  The password will be 'oval'.  <br />/chanserv register #green oval A channel about green things.<br />Note:  A channel will drop if the Founder fails to identify to a channel every 30 days.  If a Founder is gone for 30 days, the channel will drop or pass onto a successor, if the Founder names one. <br /><br />Question:  Why won't Chanserv recognize me when I enter a channel I have auto-ops in?<br />Answer:  You need to be identified with Nickserv prior to entering the channel.  Simply part the channel and identify to Nickserv and re-enter the channel.<br /><br />Question:  Someone banned me from a channel for no good reason.  What can be done?<br />Answer:  Channel founders and the ops they assign can ban someone from their channel for any reason at all, whether you could be considered harassing or not.  Sorcery IRCops will not interfere in this as it is the right of any founder to set up his/her channel so long as it follows SorceryNet guidelines.  The best thing we can suggest is to private message the founder or an op of the channel itself and ask to be allowed in.  If you are denied or there is no response, move on.  There are plenty of other channels on SorceryNet and hopefully you will find a more welcoming room elsewhere.  <br /><br />Question:  A user is ban evading and continues to return to my channel.  How do I get rid of him/her?<br />Answer:  If you have set any bans you have set for the individual, do not remove them and come to #help for assistance from an IRCop.  If you had set akicks (/chanserv akick #channel person's-ident reason), put in the person's nick or some identifying message as to who the user is so that the IRCops can see your efforts.  If the individual is a ban evader, this goes against SorceryNet policy and IRCops will help to ensure the ban evader no longer joins your channel.<br /><br />Question:  Many bots are joining my room and flooding or spamming.  What can I do?<br />Answer:  You can report any bots/clones that are attacking your room by joining #help and we will be happy to assist you.  However, here are some helpful things you can do for your room meanwhile.  First step, set mode +i.  (/mode #channel +i)  This sets the channel to invite only, which implies that users attempting to join your channel will fail until this is removed.  Members of the channel can message an op and an op can invite them in or drop the +i.  Next step if you wish, try setting a limit on what number of people can join your channel by doing +l (/mode #channel +l number). Another way to handle it is to voice the members of your channel and then set the channel to +m which moderates the channel (/mode #channel +m).  Anyone not voiced cannot speak in the channel but they can join and part.  There are other useful modes, which you can explore, listed under Channel Modes.  Feel free to explore the options to set up your channel as you would like.  <br /><br />Question:  What are the channel levels that can be assigned to ops?<br />Answer:  Below is the rough outline, whether you use number levels to assign or set via the level label.  For more information, please see /chanserv help access and/or /chanserv help set #chan xop to choose which option you would prefer to use in auto-opping users.<br />Founder - Level 15 = The channel founder is the owner of the channel.  The channel founder can do any commands available.<br />SOP - Level 10 or higher = The channel SOP or Super Op can set akicks and auto-op members, on top of other op functions for lower ops.<br />AOP - Level 5 up to 9 = Auto-Op.  A person can ban, kick, set temporary modes to a channel, change topics and VOP or HOP users as well as other simple functions.<br />HOP - Level 4 = HalfOp. The user can voice the channel, moderate and invite, as well as ban users below Level 4 and can change topics.<br />VOP - Level 3 = Voice.  The user is voiced so that if the channel is moderated (+m), he or she can still speak.<br />0 = The user has no level and is not opped in any way in the channel.<br />&lt;0 = The user cannot be auto-opped in the channel.<br /><br /><br /><br />Pertaining to MEMOS<br /><br />Question:  Why can I not send a memo to another user?<br />Answer:  You must be registered and identified to your nick to send memos.  Also, that user must have a registered nick to receive memos. <br /><br />Question:  How do I send a memo to another user?<br />Answer:  If the criteria above is met, type /memoserv send nick your message.  <br />Example:  If the user's nick is Carl and your message is 'How are you doing?', it would look like this: <br />/memoserv send Carl How are you doing? <br /><br />Question:  How do I read a memo from another user?<br />Answer:  The command is /memoserv read #.  If you have received a memo from someone and it is your first, type in:<br />Example:  /memoserv read 1<br /><br /><br /><br />For more information on these commands and others, you can be on SorceryNet and type in: <br />/nickserv help <br />/chanserv help<br />/memoserv help<br />/gameserv help <br />/botserv help <br /><br />SHORTCUTS<br /><br />If you wish to, in most clients, you can shorten some of the Services command words.<br /><br />/ns = /nickserv<br />/cs = /chanserv<br />/ms = /memoserv<br />/gs = /gameserv<br />/bs = /botserv<br /><br /><br />You may also feel free to check out the information in more detail on this website or join #help for further assistance.</p>