So you’ve registered your channel, what can you do next? Well if you want to set your channel up in a special way to do a certain thing, you can customise it using the /cs levels command.
Although you will probably want to keep some of them as default options, you may choose to change some of them.
- You can see the list of levels for your channel by doing /cs levels #channel list.
- To change levels you use the command /cs levels #channel set option level.
- To disable a level you can use the command /cs levels #channel dis option.
NOTE: AUTODEOP and NOJOIN are maximum levels while all others are minimum levels, setting a level to 0 will mean the level applies to registered identified nicknames and to -1 or lower will mean any unregistered nickname, otherwise the level you set it to refers to the level of the nickname on your channel's access list.
|Default cs levels|
|Feature or Function||Default level||Description|
|AUTODEOP||-1||Channel operator status disallowed (does not work on SwiftIRC)|
|AUTOHALFOP||4||The level you want a nickname to get automatic halfop, some channel owners will want their channel to autohalfop everyone that joins: /cs levels #channel set autohalfop 0|
|AUTOOP||5||The level at which the nickname will get automatic op, it is generally advisable not to change this to 0 as channel ops have access to change exceptions, bans and other modes.|
|AUTOPROTECT||10||The level at which the nickname will be given +a, users with +a have access to a wider range of modes in your channel so be careful when lowering the number of access needed for autoprotect.|
|AUTOVOICE||3||A lot of channel owners like to set this to level -1 or 0, this will auto voice everybody that joins.|
|NOJOIN||-2||This defines the maximum level at which somebody cannot join a channel, you could set it to 2 and therefore only people with voice access can join the channel. Alternatively you can set the channel to restricted using /cs set #chan restricted on|
|SIGNKICK||(disabled)||You can define the level needed for the person’s name to show up in the /cs kick and ban commands, handy if you want to kick somebody without revealing who did it, a nuisance if you’re being kicked by that person.|
|ACC-LIST||1||The level at which people can do the command /cs access #channel list and see everybody’s access in the channel. If you don’t want people with only 3 access to see everybody else’s access you can up this level or disable it.|
|ACC-CHANGE||10||The level at which the nickname can add new people to the access list. You can normally keep this at 10 but if you want a channel that is very exclusive you could set it to 9999 so only you and your chosen few may add access.|
|AKICK||10||The level at which a nickname can use /cs akick. Channel owners often will up the level of this command or disable it as the akick command can kick protected users so it can be quite devastating, especially if someone akicks *!*@*|
|SET||(disabled)||The level at which people can change the options in /cs help set (Not FOUNDER and PASSWORD). You may want to change this if you want to allow your channel ops to have greater control over the channel and be able to set an ENTRYMSG change the DESC and other things to do with your channel.|
|BAN||5||The lever a user needs to ban other users. You could up this command if you don’t like people using the /cs ban command, but putting the level of this up will not stop users doing the /ban command.|
|BANME||5||The level a user needs to ban themselves. Not much benefit in changing this setting.|
|CLEAR||(disabled)||This changes the access somebody needs to clear exceptions, bans and invite exceptions. Halfops and up can already manually change bans and invite exceptions in the channel.|
|GETKEY||5||The level a user needs to do /cs getkey #channel. If your channel is taken over, an op set a key or if you want to be able to lock users from a channel and don’t want to use +I you can raise this level so only a certain access level can get the key and rejoin the channel. DO NOT DISABLE THIS COMMAND as it will be vital for your ops to regain entry to the channel if somebody takes it over.|
|HALFOP||5||The ability to use /cs halfop command, widely unused so no need to change it.|
|HALFOPME||4||The ability for halfops to halfop themselves, not much use as using /ns update would give the same effect if they have the access.|
|INFO||(disabled)||Ability to use the ALL option while doing /cs info #channel, you could lower this if you wanted your ops to be able to see what settings are set on the channel.|
|KICK||5||Controls the use of /cs kick command, although this does not stop users using normal kick commands like /kick.|
|KICKME||5||Ability to use /cs kick on yourself, no need to change this command as a user can still use other commands to kick themselves.|
|INVITE||5||Controls who can and can’t use /cs invite when the channel has invite only set on it, You may want to raise/lower this depending on what you use your channel for, for example you could create a controlled channel with +I where users of level 3 can invite themselves however it would be easier to do /cs set #chan restricted on|
|OPDEOP||5||Allowed to use OP/DEOP commands.|
|OPDEOPME||5||Allowed to (de)op him/herself.|
|PROTECT||(disabled)||Controls usage of ChanServ for a user to +a others.|
|PROTECTME||10||Controls usage of ChanServ for a user to +a him/herself. Widely unused as replaced by service bot commands or /ns update.|
|TOPIC||(disabled)||Controls use of /cs topic command, but people with ranks in channels can still change the topic even without this command so it has not much use.|
|UNBAN||5||An important command for owners and channel ops to use if they are banned from a channel and need to get back in, although it can become a nuisance when trying to ban lower ranked ops, so you may want to raise it.|
|VOICE||5||Allowed to use VOICE/DEVOICE commands. Widely unused, replaced by /ns update and /mode #chan +v commands.|
|VOICEME||3||Allowed to (de)voice him/herself. Widely unused, replaced by /ns update and /mode #chan +v commands.|
|MEMO||10||Changes the level the user needs to be able to read channel memos, you should make this higher if your channel is likely to receive memos that contain important information.|
|ASSIGN||(disabled)||Allows users to assign/unassign a services bot, you shouldn’t lower this as it is easily abused by spam assigning and unassigning of bots.|
|BADWORDS||10||Controls who can and can’t add badwords and control the badword list for BotServ, if you don’t want this command to be abused by people adding single letters that can result in lots of kicks you may want to raise the level.|
|FANTASIA||3||Allowed to use fantasia commands, for example !voice, !kb – You would normally want to keep this at 3.|
|GREET||5||The level you want BotServ to show a usernames greet, some channel owners prefer it at 0 so they can see everybody’s greet while some like to set it high so the channel is not spammed with greets.|
|NOKICK||1||Defines the level the user needs to be below to get kicked by the commands in /bs kick.|
|SAY or ACT||(completely disabled on SwiftIRC due to abuse)|