Basic Channel Moderating Guide



Table of Contents

Basic Channel Moderator Commands
Kicking
Banning/Unbanning
Kickbans
Muting/Unmuting
Maintaining the ban list

Using the Network Bot to aid in Channel Moderating
Enabling badword list enforcement
Enabling flood enforcement
Enabling repeat enforcement
Enabling capslock enforcement
Enabling color enforcement
Enabling bold enforcement
Enabling underline enforcement
Enabling reverse enforcement

Basic Channel modes and Settings
A)Muting a channel
B)Blocking specific words in a channel
C)Stripping colored text in a channel
D)Delaying a kicked user from quickly rejoining a channel
E)Blocking nickname changes in a channel
F)Hiding a channel from /whois and /list results
G)Setting a channel to invite only
H)Setting flood protection
Changing the channel topic
Changing the channel entry message



A More Advanced Channel Moderation Section

Advanced Channel Moderator Commands
Ranged Bans
Timed Bans
Akicks
Viewing Akick lists
Enforcing Akicks
Force parting/Removing usernames

Advanced Channel Settings
Clear Commands:
A) Clearing all bans from a channel
B) Clearing all akicks from a channel
C) Clearing all users from a channel
D) Clearing all channel modes from a channel

Restricting entry to a channel:
A) Using the RESTRICTED channel setting
B) Setting the channel to invite only
C) Using other channel modes to restrict entry
Locking channel modes (MLOCK)

Managing channel ownership:
A) Setting a channel successor
B) Changing the registered channel founder
C) Changing the channel description
D) Adding more than one owner/founder-level users to a channel

Regulating Ranks within a Channel
Setting PEACE
Setting SECUREOPS

Setting exemptions to restrictions on a channel:
A) Ban exemptions (channel mode +e)
B) Restriction exemptions (channel mode +X)
C) Invite-only exemptions (channel mode +I)





Basic Channel Moderating Commands

Kicking

Kicking forcefully removes a user from the channel, and the target user is allowed to rejoin immediately after a kick is performed. There are several methods available to kick a user from a channel:

Basic KICK command:
/kick <username> <optional reason>

Using chanserv:
/cs kick <#channel> <username> <optional reason>
or
/msg chanserv kick <#channel> <username> <optional reason>

Using a fantasy command:
!kick <username> <optional reason>
or
!k <username> <optional reason>


If you need to kick more than one person at the same time for the same reason you can separate their names with commas (don't include spaces between the names and commas).

Banning

Banning blocks a user from joining a channel if their host or other identifiable information matches an entry on the ban list. The basic ban command will not remove the target from the channel. If you use the command on a target that is currently in the channel that target will no longer be able to post anything to that channel, and once they exit they will be unable to rejoin until the ban is removed.

On this network using host bans are encouraged for general banning purposes. When banning a host, it is recommended to replace the username and ident portion with wildcards.
An example of a good host ban is /ban *!*@targeting.user.host.beyond.the.at.sign.

If you must kick and ban a user at the same time, ban first then kick. Or, use the KICKBAN command.

Basic ban command
/ban <host>
To unban:
/unban <host>

Using a Fantasy command:
!ban <host>
or
!b <host>


The fantasy unban command currently only works on usernames present in the channel. To unban a host use the basic or channel mode unban version.
!unban <host>

Using a channel mode:
/mode <#channel> +b <host>
To unban:
/mode <#channel> -b <host>


Kickbans

KICKBAN is a KICK and BAN command that is conveniently merged into one, and is usually the ban command of choice when the target is present in the channel. Use one of the UNBAN commands above if you need to remove a ban set through a kickban.

Using chanserv:
Chanserv's default ban command will kick the user from the channel after the ban is set. You can also set an optional expiration timer to a ban with +time.
/cs ban <#channel> <+optional time> <username> <optional reason>
or
/msg chanserv ban <#channel> <+optional time> <username> <optional reason>

Examples:
/msg chanserv ban #Fishtopia Kittycat no stealing fish will ban Kittycat from #Fishtopia with the kick reason being "no stealing fish."
/msg chanserv ban #channel +5h Bob123 stop spamming will ban Bob123 from #channel for 5 hours with the kick reason being "stop spamming."

Using a Fantasy command:
!kickban <username> <optional reason>
or
!kb <username> <optional reason>


A /kickban <username> <optional reason> command does exist, but only a few clients can properly read this particular command line (like xchat). For that reason it is recommended to use one of the KICKBAN commands listed above instead.


Mute bans

A mute is a type of modified ban that can be performed by anyone who has access to the basic ban command. Muting prevents the target from posting anything into the channel, but allows the target to freely exit and rejoin the channel while the mute is in effect.

Mutes can be added to nearly all ban formats; all it requires is the presence of m: before the hostmask.

Basic mute:
/ban m:<hostmask>
To unmute:
/unban m:<hostmask>

Using a channel mode:
/mode <#channel> +b m:<hostmask>
to unmute:
/mode <#channel> -b m:<hostmask>

When using a fantasy command, the basic unban command is used to remove a mute:
!mute username
To unmute:
!unban username

Example: muting username!ident@targeting.user.host.beyond.the.at.sign would be written as
/ban m:*!*@targeting.user.host.beyond.the.at.sign

Maintaining the ban list

Good channel moderation involves maintaining the channel's ban list, such as removing outdated bans and making sure the channel ban list doesn't reach its max limit. This network normally supports up to 60 ban entries per channel.

The banlist of a channel will automatically clear if all users leave and the channel becomes empty. If the channel constantly empties it is recommended to set AKICKs instead of normal bans if a ban needs to last for an extended period of time (see the section on AKICKs).

To view the banlist of a channel you can use the ban channel mode without any parameters attached.

Using a channel mode:
/mode <#channel> +b


To cull entries on a ban list, IRC clients often have built in ban list management features which allow you to either press an unban button next to each entry, or allow you to select multiple entries followed by pushing an unban button. Use the basic UNBAN commands to remove banlist entries manually.




Using the Network Bot to Aid in Channel Moderating

A network-provided channel channel bot can be utilized to help enforce the rules of your channel when actual moderators may not be immediately available. In order for the bot to kick or ban a user upon a trigger you will need to turn on each trigger type. If you don't want the bot to issue any bans for users repeatedly triggering kicks, when custom configuring the bot settings use 0 as the kick before ban number.

For further information about bot kick enforcement use /bs help kick or /msg botserv help kick.

Enabling badwords list enforcement

When this setting is activated, the bot will kick when a user posts a trigger entry that is on the channel's badwords list. To turn on kick for badwords use:
/bs kick badwords <#channel> on <amount of kicks before a ban>
or
/msg botserv kick badwords <#channel> on <amount of kicks before a ban>


The badwords trigger entries will aslo need to be added to the channel badwords list. To add entries to the badwords list use:
/bs badwords <#channel> add <word> <optional parameter>
or
/msg botserv badwords <#channel> add <word> <optional parameter>

Optional parameters specify trigger restrictions:
SINGLE - kick/ban will only be triggered if the user says the entire word by itself
START - kick/ban will only be triggered if the user starts a word with the trigger word
END - kick/ban will only be triggered if the user ends a word with the trigger word
(If no optional parameter is specified the bot will kick if the trigger is posted in any unbroken form.)


To delete an entry from the badwords list use:
/bs badwords <#channel> del <word or the entry number(s) the word(s) are assigned to>
or
/msg botserv badwords <#channel> del <word or the entry number(s) the word(s) are assigned to>


See /bs help badwords or /msg botserv help badwords for more information about the badwords list.

Enabling flood enforcement

Flooding is referred to the act of a nickname submitting a large number of posts in a set amount of time. To turn on kick for flooding use:
/bs kick flood <#channel> on <number of kicks before ban> <number of lines> <number of seconds>
or
/msg botserv kick flood <#channel> on <number of kicks before ban> <number of lines> <number of seconds>

If the line or seconds are not specified, the bot will kick if a user posts more than 6 times within 10 seconds.
Use /bs help kick flood or /msg botserv help kick flood for further information.

Enabling repeat enforcement

Repeating is when a user consecutively posts the same line over and over. To turn on kick for repeating use the following command:
/bs kick repeat <#channel> on <number of kicks before a ban> <number of repeated lines>
or
/msg botserv kick repeat <#channel> on <number of kicks before a ban> <number of repeated lines>

If the optional parameters are not specified then the bot will kick if a user repeats posts 3 times in a row.
Use /bs help kick repeat or /msg botserv help kick repeat for further information.

Enabling capslock enforcement

Capslocking is when a user posts messages which contain a portion or the entirety of the message in capital letters. To turn on kick for caps use:
/bs kick caps <#channel> on <amount of kicks before a ban> <minimum character length required> <minimum percentage of caps>
or
/msg botserv kick caps <#channel> on <amount of kicks before a ban> <minimum character length required> <minimum percentage of caps>

If the length and percentage parameters are not specified then the bot will kick if a line consisting of more than 10 characters and at least 25% caps is posted.
Use /bs help kick caps or /msg botserv help kick caps for more information.

Enabling color enforcement

Turning this on will trigger the bot to kick whenever someone posts a message that contains colors to the channel. This setting is rarely used due to a channel mode that can strip colors from messages in a more effective manner. To turn on kick for colors use the following command:
/bs kick colors <#channel> on <number of kicks before ban>
or
/msg botserv kick colors <#channel> on <number of kicks before ban>

Use /bs help kick colors or /msg botserv help kick colors for further information.

Enabling bolds enforcement

The bot can be configured to kick whenever a user posts something in bold print. To turn this on, use:
/bs kick bolds <#channel> on <number of kicks before ban>
or
/msg botserv kick bolds <#channel> on <number of kicks before ban>

Use /bs help kick bolds or /msg botserv help kick bolds for further information.

Enabling underlines enforcement

The bot can be configured to kick whenever a user posts something that contains underlines. To turn this on, use:
/bs kick underlines <#channel> on <number of kicks before ban>
or
/msg botserv kick underlines <#channel> on <number of kicks before ban>

Use /bs help kick underlines or /msg botserv help kick underlines for further information.

Enabling reverses enforcement

The bot can be configured to kick whenever a user posts reversed text (reversed text is essentially flipping the fore and background colors of a text using an IRC client shortcut key). This setting is rarely used due to a channel mode that can strip colors from messages in a more effective manner. To turn this on, use:
/bs kick reverses <#channel> on <number of kicks before ban>
or
/msg botserv kick reverses <#channel> on <number of kicks before ban>

Use /bs help kick reverses or /msg botserv help kick reverses for further information.



Basic Channel Modes and Settings

It is highly recommended to become familiar with all of the different channel modes by visiting /helpop chmodes. Below are some of the more commonly used channel modes on this network. Note that channel modes are case sensitive, so +M will do something different from +m.

Commonly set channel modes:

A) Muting a channel (mode +m)
Muting a channel prevents anyone who is below the rank of voice from posting messages into the channel, and is useful to quickly silence channel users so that users with ranked permissions can post to the channel without the interruption of non-ranked users.

/mode <#channel> +m
To remove a channel mute use
/mode <#channel> -m


B) Blocking target words from being posted into a channel (mode +g)
The badwords bot trigger will kick people when a target word is typed, but channel mode +g will completely block a message that contains a target word or phrase from being posted to the channel at all. Wildcards are often included for blocked target words because the likelihood of a user typing only that target by itself is slim.

/mode <#channel> +g <target>
To remove a blocked word use
/mode <#channel> -g <target>

Examples: Blocking any posts containing the symbol "#": /mode <#channel> +g *#*
Blocking any posts ending with the phrase "I hate fish": /mode <#channel> +g *I?hate?fish

To view the list of currently blocked words on a channel, use /mode <#channel> +g.

C) Stripping colored text in a channel (mode +S)
To remove any fore or background colors that a user may include in a message that is posted to the channel, use channel mode +S.

/mode <#channel> +S
To remove this mode use
/mode <#channel> -S


D) Delaying a kicked user from quickly rejoining a channel (mode +J <seconds>)
When set, anyone who is kicked from a channel will not be allowed to rejoin for the specified amount of time. This delay is also enforced upon users who have auto-rejoin enabled.

/mode <#channel> +J <amount of seconds>
To remove this mode use
/mode <#channel> -J


E) Blocking nickname changes in a channel (mode +N)
If people constantly changing nicknames are bothersome, this nonick channel mode will prevent the /nick command from working. Note that people who use /sidentify in the channel will still have their nick changed even when this mode is active.

/mode <#channel> +N
To remove this mode use
/mode <#channel> -N


F) Hiding a channel from /whois and /list results (mode +s)
If you don't want your channel to be visible to general channel inquiries you may set the channel to be secret. When this mode is enabled the channel will no longer show up in the channel list of people being WHOISed from outside the channel, and will also be hidden from the network LIST results.

/mode <#channel> +s
To remove this mode use
/mode <#channel> -s


G) Setting a channel to invite only (mode +i)
Setting a channel to invite on this network will only permit people who are assigned to certain ranks on the access list or match an invite exception to join a channel. To set a channel to be invite only use:

/mode <#channel> +i
To remove this mode use
/mode <#channel> -i

To join a channel that is set to invite only, you must be invited by yourself or a channel occupant before you are allowed to join it. If the invite is successful you will be notified of an invitation.
/cs invite <#channel>
or
/msg chanserv invite <#channel>
For more information about invite exemptions, see Invite-only exemptions (channel mode +I).


H) Setting flood protection (mode +f [*]<lines>:<seconds>)
When set, anyone whose posts exceed the amount of lines within the time frame specified will be kicked by the network server. This channel setting may not be necessary if you have a network channel bot with flood kick turned on.

/mode <#channel> +f <lines posted>:<amount of seconds>
To remove this mode use
/mode <#channel> -f

Example: A flood kick that is triggered when someone posts 4 lines in 2 seconds would be /mode <#channel> +f 4:2

This channel mode can also be set to kickban anyone who meets the flood trigger by including * before the specified lines parameter. To activate channel mode +f with the ban option use:
/mode <#channel> +f *<lines posted>:<amount of seconds>

Example: A flood kickban triggered when someone types 7 lines in 5 seconds would be /mode <#channel> +f *7:5.

Changing the channel topic

Channel topics are displayed to anyone who joins the channel or uses the LIST and CS INFO command on that channel, and can provide necessary and helpful information to visitors. To change a channel topic use:

/topic <topic message>

Using a Fantasy command:
!topic <topic message>

Using chanserv:
/cs topic <#channel> <topic message>
or
/msg chanserv topic <#channel> <topic message>

If you use !topic without a message attached it will display the current channel topic.

Changing the channel entry message

Channel entry messages are similar to channel topics in that they are displayed to everyone who joins, but it is sent in the format of a notice (from the channel's network bot or Chanserv). For further information you can use /cs help entrymsg or /msg chanserv help entrymsg.

To set an entry message use:
/cs entrymsg <#channel> add <entry message>
or
/msg chanserv entrymsg <#channel> add <entry message>

To remove an entry message use the following. If there is only one entrymsg set, the entry number is 1.
/cs entrymsg <#channel> del <entry number>
or
/msg chanserv entrymsg <#channel> del <entry number>

You can have multiple entry messages per channel. To view them all at once without rejoining, use:
/cs entrymsg <#channel> list
or
/msg chanserv entrymsg <#channel> list

If you would like to clear all of the entrymsgs in a channel, you can use the following:
/cs entrymsg <#channel> clear
or
/msg chanserv entrymsg <#channel> clear






A More Advanced Channel Moderation Section

The following commands are much easier to work with once you are familiar with the basic commands listed above.

Ranged Bans

Range bans use strategically placed wildcards to allow a ban to affect a wider range of target hostmasks. A type of range ban is already in use when employing wildcards for the username and ident of a ban, but wildcards can also be applied to any section of a target's hostmask to ban a range of hosts, nicknames, IPs, idents or even entire ISPs.

Use range bans wisely.

A) Range banning hosts
In this example a user has three slightly different hosts that share a common group of numbers.
username!ident@hidden-123.890.IP
username2!ident@hidden-456.890.IP
username3!ident@hidden-789.890.IP
Instead of three individual bans you can range ban them as one entry by replacing the unrelated portion of the host with a wildcard:
/ban *!*@*.890.IP
When this ban is in effect it will prevent anyone with a hostmask ending in .890.IP from joining the channel. This goes into effect even if the user has a vhost activated.

If you want to ban people that join using only the middle part of a host, put a wildcard before and after it.
The hostmask for the example below is username!ident@hidden-278.814.IP
/ban *!*@*278* Will ban any host containing the numbers 278
/ban *!*@*278.* Will ban any host containing a middle segment ending in 278
/ban *!*@*-278.* Will ban any host that only contains 278 near the start of the displayed portion of a host
/ban *!*@*.IP will ban anyone with a host that ends in .IP

B) Range banning nicknames
If you want to prevent certain words from being used as nicknames in your channel you can range ban those too.
As an example, you can ban nicknames containing the word fish anywhere in the name with /ban *fish*!*@*.
/ban fish*!*@* will ban nicknames that start with fish
/ban *fish!*@* will ban nicknames ending with fish
/ban fish!*@* will only ban the nickname that is specifically "fish" because no wildcards were included in the username section of the hostmask.

C) Range banning idents
Ident range bans are especially useful if you want to ban a specific IRC webclient that inserts its name into the ident field.
/ban *!Frogchat@* would ban anyone with the exact ident named Frogchat.
/ban *!fire*@* would ban anyone with an ident starting with fire.

The general rule of ranged bans is that the less information you provide within the wildcards, the more inclusive the ban becomes. Ultimately, setting a range ban of *!*@* would ban everyone in the channel including you, so avoid using that wide of a range.

Timed Bans

Timed bans are bans with a set expiration date that is enforced by the network servers, and can be applied to already existing bans. When the time set to a timed ban expires the target will be automatically removed from the banlist.

The duration of the ban can be set from seconds to weeks: Use s for seconds, m for minutes, d for days and w for weeks.
/tban <#channel> <time duration> <hostmask>

Using a Fantasy command:
!ban <+time duration> <hostmask>
or
!kb <+time duration> <username> <optional reason>

Example: time banning HiUsername!ident@targeting.user.host.beyond.the.at.sign for 13 hours would be written as
/tban <#channel> 13h *!*@targeting.user.host.beyond.the.at.sign or !ban +13h *!*@targeting.user.host.beyond.the.at.sign if using the fantasy command.


Akicks

AKICKs are automatic kickbans that will ban and kick any user that matches the target hostmask upon entry. Akicks are saved to a separate target list from normal bans, and they will remain in effect even if the entire normal ban list is cleared. In addition, akicks will not clear if a channel is emptied.

To add a target to the akick list use:
/cs akick <#channel> add <hostmask> <optional reason>
or
/msg chanserv akick <#channel> add <hostmask> <optional reason>

To remove an akick use:
/cs akick <#channel> del <hostmask or entry list numbers>
/msg chanserv akick <#channel> del <hostmask or entry list numbers>

Using a Fantasy command:
!akick add <hostmask> <optional reason>
To remove an akick use
!akick del <hostmask> <optional reason>


Viewing akick lists

There are two ways you can view an akick list, which is by using AKICK LIST or AKICK VIEW. The commands are in essence the same, but AKICK VIEW will also display the username that set the akick as well as the date an akick was added.
/cs akick <#channel> <list or view>
or
/msg chanserv akick <#channel> <list or view>

Using a Fantasy command:
!akick <list or view>


Enforcing akicks

If you set an akick and want it to immediately enforce it upon the userlist use:
/cs akick <#channel> enforce
or
/msg chanserv akick <#channel> enforce

This will automatically kickban any users that match akick target specifications.

Force parting/Removing users

There are users that have auto-rejoin set to their IRC client, and the auto-rejoin setting may become troublesome to channel moderators if the user is immediately rejoining the channel after being kicked. If a channel does not have join delay enabled and you don't wish to ban them you can remove them or force them to part from the channel.

Fpart will force exit the user via a part message:
/fpart <#channel> <userame> <optional reason>

Removing a nickname will force exit the user via a removal message:
/remove <username> <#channel> <optional reason>

Users who are fparted or removed will be able to immediately rejoin a channel if they manually type in the join command on their client, but auto-rejoin will not be activated.




Advanced Channel Settings

Clearing commands

Clearing commands can quickly empty a channel or list if such an occasion is ever needed. They are rarely used, but are good to know in case of channel emergencies. Below are some of the more frequently used clearing commands.

Most clearing commands are only available to those with founder level permissions or flags on a channel.

A) Clearing all bans from a channel
When used, all entries of the normal ban list will be removed
/cs mode <#channel> clear bans
or
/msg chanserv mode <#channel> clear bans

Using a fantasy command:
!mode clear bans


B) Clearing akicks from a channel
When used, all entries of the akick list will be removed.
/cs akick <#channel> clear
or
/msg chanserv akick <#channel> clear

Using a fantasy command:
!akick clear


C) Clearing users from a channel
If you have founder command access, you can clear all users on a channel with a wide-ranged kick, which will kick everyone at your access rank and lower (including you):
/cs kick <#channel> *
or
/msg chanserv kick <#channel> *

Using a fantasy command:
!kick *



D) Clearing channel modes from a channel
When used, all of the non-permanent/locked channel modes will be removed.
/cs mode <#channel> clear
or
/msg chanserv mode <#channel> clear

Using a fantasy command:
!mode clear


Restricting entry to a channel

Restricting channels are useful for setting a channel to private use only, or if you need to temporarily limit the types of users that can enter the channel. There are several different methods to achieve this, depending on how restricted you want the channel to be.

A) Using the RESTRICTED channel setting
When the channel RESTRICTED setting is turned on only users who are on that channel's access list will be able to join and stay. If a user not on the channel's access list joins they will be automatically kickbanned by chanserv or the network's channel bot.
/cs set restricted <#channel> on
or
/msg chanserv set restricted <#channel> on

To remove the RESTRICTED setting use:
/cs set restricted <#channel> off
or
/msg chanserv set restricted <#channel> off

B) Setting the channel to invite only
See the section on channel mode +i for further information. If you intend to use invite as a permanent means of security it is recommended to add channel mode +i to the mlock list.


C) Using other channel modes to restrict entry
Channel modes are very useful, and again, it is highly recommended to get to know them (see /helpop chmodes). Below are some channel modes that are not as widely used as the invite mode, but are great for restricting channel entry in specific situations.

+j <number of people joining> <seconds> -Limits the amount of users that can enter the channel in a specified amount of seconds.
+z -Prevents users who are not on an SSL connection from joining the channel
+R -Prevents users using unregistered or unidentified nicknames from joining the channel.
+k <key> -Requires channel visitors to type a channel key with the join command before being allowed to enter the channel. See below.

Setting the channel to keyed mode requires you to choose a key (similar to a password) as the mode is set.
/mode <#channel> +k <channel key>
to remove this mode use
/mode <#channel> -k

A keyed entry can used for light or temporary channel security due to the fact that the key will be visible to anyone currently in the channel, unless you set the channel to RESTRICTED. Channel mode +k will also be removed if the channel becomes empty except if this channel mode is mode locked. To join a channel with a channel key set, use:
/j <#channel> <channel key>

Locking channel modes

Channel modes that are not automatically set by the network are lost when a channel becomes empty, unless you mode lock them. When mode lock is in effect the channel modes saved will remain on the channel, and if the channel empties those modes will be automatically re-enforced as soon as a client joins it.

Mode locks can set channel modes to be permanently on or permanently off. Permanently off means that if someone sets a channel mode such as +m to a channel mode locked to -m, the mode lock will automatically set that channel mode back to -m, and permanently on is vice versa.

For more information on mode locks use /cs help mode or /msg chanserv help mode.

Adding channel modes to the lock list:
/cs mode <#channel> lock add +/-<desired channel modes>
or
/msg chanserv mode <#channel> lock add +/-<desired channel modes>

Example: /msg chanserv mode #channel lock add +s-i will lock the channel mode +s to be permanently on, and not allow +i to be set as long as this mode is locked.

Removing locked channel modes:
/cs mode <#channel> lock del <undesired channel modes that were listed>
or
/msg chanserv mode <#channel> lock del <undesired channel modes that were listed>

Example: /msg chanserv mode #channel lock del -i will delete the -i mode that was set to the channel above.

You can view the list of all locked modes on the channel using:
/cs mode <#channel> lock list
or
/msg chanserv mode <#channel> lock list

Managing Channel Ownership and Information

The channel information and ownership settings are normally restricted to channel founders, or someone who has founder permissions on a channel.

For more information and to see the full list of commands available see /cs help set or /msg chanserv help set.

A) Setting a channel successor
When a channel successor is set, the registered channel founder status will be transferred to whomever is set as the successor if the current channel founder's nickgroup becomes de-registered. The channel successor should be a registered username.
/cs set successor <#channel> <username>
or
/msg chanserv set successor <#channel> <username>

To unset a channel successor, use the command without including the username:
/cs set successor <#channel>
or
/msg chanserv set successor <#channel>

For more information about setting channel successors see /cs help set successor or /msg chanserv help set successor.

B) Changing the registered channel founder
To change the registered founder of the channel, it is recommended for both parties to have access to founder/owner permissions.
/cs set founder <#channel> <username>
or
/msg chanserv set founder <#channel> <username>

For more information about channel successors see /cs help set founder or /msg chanserv help set founder.

C) Changing the channel description
To change the description of the channel that is displayed when commands such as /cs info is used, use the command below. You can also use the word description instead of desc.
/cs set desc <#channel> <description here>
or
/msg chanserv set desc <#channel> <description here>

For more information about setting channel descriptions see /cs help set desc or /msg chanserv help set desc.

D) Adding more than one owner/founder-level users to a channel
Users with an access level of 10000 would be granted many of the same founder-level permissions as the registered founder of the channel, as long as they are logged in and identified. Some commands may still be restricted to the registered founder only, depending on your access setting.

Having owner/founder level access will not replace being the registered founder of that channel. For this reason it is recommended to set a channel successor to prevent a channel from de-registering if the current founder's nickgroup becomes de-registered.

For more information on setting users to owner level see Adding People to the channel Access list.




Regulating Ranks Within a Channel

This area covers a few basic settings that help to regulate the activities of ranked members in a channel. These settings are not mandatory and a channel can run fine without them.

Setting PEACE

Setting PEACE will prevent a user from kicking or banning any username that is set to a rank equal or higher than them.

For more information on the PEACE setting use /cs help set peace or /msg chanserv help set peace.

/cs set peace <#channel> on
or
/msg chanserv set peace <#channel> on

To remove PEACE use:
/cs set peace <#channel> off
or
/msg chanserv set peace <#channel> off


Setting SECUREOPS

When SECUREOPS is in effect, any temporary channel rank that is set to OP or higher will be automatically removed by chanserv or the network channel bot. This setting is helpful in preventing ranked users from giving tempoary ranks of OP or higher to unauthorized nicknames on the userlist.

For more information about SECUREOPS see /cs help set secureops or /msg chanserv help set secureops.

/cs set secureops <#channel> on
or
/msg chanserv set secureops <#channel> on

To remove the SECUREOPS setting use:
/cs set secureops <#channel> off
or
/msg chanserv set secureops <#channel> off

Setting exceptions to restrictions on a channel

Certain restrictions in a channel (such as text and color blocks set from channel commands) will affect all users in a channel, including moderators/ranked users. This may not be desirable, so there are channel modes that can set exemptions for certain channel ranks and hosts.


A) Ban exceptions using channel mode +e
Any target hostmask set to channel mode +e will be exempt from bans that may be triggered in the channel. In order to ban a target on the exception list, first remove their hostmask from the ban exception list then ban as normal.

/mode <#channel> +e <hostmask>
To remove this mode use
/mode <#channel> -e <hostmask>

You can view the list of exemptions on a channel by using /mode <#channel> +e.


B) Restriction exceptions using channel mode +X
Channel mode +X allows specified ranked users to be exempted from restrictions set by other channel modes.
To view all of the +X exceptions currently set to a channel use /mode <#channel> +X.

/mode <#channel> +X <restriction name>:<minimum rank that is exempted>

To remove an exception use
/mode <#channel> -X <restriction name>:<minimum rank that is exempted>

Restrictions available for exemption:
filter (from mode +g)
nonick (from mode +N)
stripcolor (from mode +S)
blockcolor (from mode +c)
blockcaps (from mode +B)
flood (from mode +f)
nickflood (from mode +F)
noctcp (from mode +C)
regmoderated (from mode +M)

Ranks available for exemption:
v (voice)
h (halfop)
o (channel operator)
a (admin/protected)
q (owner/founder)

Examples:
/mode <#channel> +X nonick:h will allow anyone with halfop or higher to change nicknames in a channel set to +N.
/mode <#channel> +X stripcolor:v will allow anyone with voice or higher to post colorful messages to a channel set to +S.
/mode <#channel> +X filter:a will allow anyone with admin or higher to post words blocked by channel mode +g.


C) Invite-only exceptions using channel mode +I
Setting an invite exception allows a user with a matching hostmask or nickgroup to join an invite-only channel without the need to send self-invites prior to joining each time.

/mode <#channel> +I <hostmask>
to remove this mode use:
/mode <#channel> -I <hostmask>

Invite exceptions can also be set to a main registered username, which is helpful if a user has multiple nicknames in a nickgroup, and all had unique vhosts set to them. When this exception is added a user can exempt their main registered nickname, then freely join the channel using any of the other nicks in that same nickgroup, as long as the user is properly logged in and identified.
/mode <#channel> +I R:<main username>
to remove this mode use:
/mode <#channel> -I R:<main username>

Note that if the channel empties the invite exemptions will be cleared.

This concludes the basic channel moderator guide. If you have any questions feel free to drop by #help, or use one of our support e-mails to get in touch with us.