Set (ChanServ Command)
This command allows you to change various channel settings. While channel registrations are tied to individual account holders, channels can have their settings changed individually, and channels owned by the same account can behave differently. This command provides a way of controlling those settings. There are 18 different settings which can be controlled, most of them by people with SOP access, a few requiring founder access, and one (noexpire) requiring IRC operator access. For brevity, all command examples assume that #channel is the name of your channel. The following 19 settings can be changed.
This controls whether people are automatically given the appropriate channel modes upon joining the channel. This is set to on by default, because the vast majority of users are expected to want to have this set. This setting overrides the NickServ setting of the same name if this setting is turned off, but will not override it if this setting is turned on. If you wish to turn this setting off for your channel, use the following command:
/msg ChanServ set autoop #channel off
This controls how services will ban a user whenever a ban is issued by services in the channel. This applies to bans because of akicks by ChanServ or because of bans issued by either ChanServ or BotServ. One of four possible numbers, ranging from 0 to 3, can be used to set the ban type as follows:
This is set to 2 by default for all new channel registrations. Unless you are absolutely certain of what you are doing, you should keep this setting at 2 or 3. To change this setting to 3, you can issue the following command:
/msg ChanServ set bantype #channel 3
This modifies the channel's description, which appears whenever someone runs an info command on your channel. This is aliased to the description command also offered by ChanServ, which is not covered here as usage is identical. This command accepts 1 argument, the description for your channel. To set your channel's description to "Coolest channel ever", use this command:
/msg ChanServ set #channel Coolest channel ever
This modifies the channel's email address, which appears whenever someone runs an info command on your channel. This is mostly useful to offer people channel support. By default, it is unset when you register a channel, and you are not required to ever set this. If you want to change the channel's email to [email protected], you can do so with this command:
/msg ChanServ set email #channel [email protected]
Unlike setting this with NickServ, you do not need to confirm your email address. However if you do set this, you must own the email address. If we get complaints of spam because you used someone else's email address, the channel will be suspended as this will be considered a terms of service violation.
This command sets the channel founder. This command can only be used by the current channel founder while they are identified to their NickServ account. Note that there is no undoing this command. Once you relinquish foundership of a channel to another user, you lose all your access to that channel and the new founder is not obligated to give you any status in return or even allow you to use the channel anymore. Therefore, you must use this command with care. This command accepts 1 argument, the registered nickname to transfer foundership to. To transfer foundership to nick1, use this command:
/msg ChanServ set founder #channel nick1
This setting determines whether or not ChanServ will attempt to remember the channel modes set on any given channel. If turned on, ChanServ will remember these channel modes and attempt to reset them if the channel becomes empty and is then recreated while still registered. This is turned on by default for new registrations. This command accepts 1 argument, either the word on or off to toggle this setting. To turn this off, you use the following command:
/msg ChanServ set keepmodes #channel off
Same as above, but applies to a channel's topic instead of the channel modes. This setting is turned on by default. This command accepts 1 argument, either the word on or off to toggle the setting.
This IRC operator only command keeps a channel from expiring. This is to be used only on official network channels and not channels personally owned by network staff or people they know. For obvious reasons, this is turned off by default. This command accepts 1 argument, either the word on or off to toggle this setting. To enable this setting, you would issue the following command:
/msg ChanServ set noexpire #channel on
This command determines how channel operators can use ChanServ commands on one another. If this setting is on, then channel operators will not be able to use ChanServ to remove users, channel modes, or bans issued by other users who have equal or higher access to themselves. This does not prevent the use of IRC commands for this purpose. This setting is enabled by default for new channel registrations. This command accepts 1 argument, either the word on or off to toggle this setting. To turn this setting off, use the following command:
/msg ChanServ set peace #channel off
This IRC operator only command marks the channel as permanent by services. If the channel is otherwise empty, then services will keep ChanServ or a BotServ bot parked in the channel to keep it open. Which one is used depends on the channel settings. This is identical to channel mode +P and therefore this should be used instead, as this will work without any intervention by services, which would simply use channel mode +P anyway.
This command sets whether or not a channel is private. A private channel in services is not the same thing as channel mode +p which marks a channel as private with the IRC network. These two settings can be used independently of each other (though this is not recommended for reasons which should become clear) as they behave in different ways.
A channel marked as private through channel mode +p will not show up in the list command issued from your IRC client, but it can still show up if you use ChanServ's list command instead. If you use ChanServ to mark your channel as private, then the opposite behavior is true, your channel will be removed from ChanServ list commands not issued by IRC operators, but will still appear in IRC client issued list commands. Setting both at the same time removes your channel from both lists.
This setting accepts 1 argument, either the word on or off to toggle the setting. This is turned off by default, as it is assumed that most users will want most of their channels not to be private. To mark your channel as private in services, use the following command:
/msg ChanServ set private #channel on
This command controls whether or not your channel is a restricted access channel. A restricted access channel cannot be entered unless your account is on the access list and you are logged into services, or you match a host mask on the access list. By default, this setting is turned off. It may be useful to you if you have a channel specifically set aside for channel operators of another channel that you own. This command accepts 1 argument, either the word on or off to toggle this setting. To enable this setting, issue the following command:
/msg ChanServ set restricted #channel on
This command toggles channel security. If this setting is turned on, then nobody will be given half operator status or above unless logged into NickServ, identified to their account with a password, and they are on the channel's access list. If an operator sets a channel mode on this person granting them such access to the channel, the mode will be automatically reversed by ChanServ unless they were previously added to the access list. ChanServ will never grant access to users not meeting the above 3 conditions regardless of which commands are issued to it.
This setting is enabled by default. This command accepts 1 argument, either the word on or off to toggle the setting. It is not recommended that you disable this setting. If you wish to disable this setting however, you can do so with the following command:
/msg ChanServ set secure #channel off
This command controls who has access to drop the channel, change the successor, or transfer foundership of a channel. This setting is enabled by default for new channel registrations. It is strongly not recommended that you change this setting. Network staff are not responsible for the loss of access to channels through the misuse of ChanServ commands by the channel's real founder.
If this setting is turned off, then anyone with founder access can change the above settings. If it is turned on, then only the account whose nickname is listed as the founder's in ChanServ's info command will be able to make such changes. To disable this setting, you can issue the following command:
/msg ChanServ set securefounder #channel off
This setting determines who is permitted to have channel half operator status in a channel or not. This setting is enabled by default for all new channel registrations. If turned on, then only users who are identified to an account on the channel's access list will be allowed to have half operator status and above. Unidentified users will still be allowed to have voice. If this setting is turned off, then anyone is allowed to have any status on the channel. You should therefore only disable this command with care.
This command accepts 1 argument, the word on or off to toggle this setting. To disable this setting for your channel, use the following command:
/msg ChanServ set secureops off
This command determines whose nickname is appended to kicks issued through ChanServ. This can allow users who are kicked to see who kicked them. This setting is disabled by default, meaning users removed from the channel by ChanServ will never see this information.
This setting accepts 1 argument, either the word on, off, or level. This setting can be enabled either with the word on, meaning all kicks are signed, or level, meaning all kicks below a certain access level are signed, while kicks at or above a certain access level are not. By default, kicks issued by super operators (SOP) or access level 10 and above are not signed if the level setting is used. If the default is changed to half operator or 4, then this has a similar (although not identical) effect to turning this setting off.
To turn this setting on so that (by default), automatic operators (AOP) and half operators (HOP) cannot use kick commands without a signature, you can issue the following command:
/msg ChanServ set signkick #channel level
This command sets a successor for the channel. The successor is automatically given founder access to the channel if the following conditions are met:
- The founder's nickname expires
- The founder's nickname is manually dropped, usually by the account owner
- The successor's account has fewer than 10 channels (the maximum number allowed to be registered)
- The channel itself would normally be dropped (because of a lack of use for 30 days)
The successor's nickname must belong to a registered account on the network. If for some reason, foundership cannot be transferred to the successor, then the channel is automatically dropped. This usually happens because no successor is named, one was named in the past but their account was dropped, or because the successor already has the maximum number of channel registrations allowed.
This setting is unset by default for new channel registrations. As the owner of a channel, you and only you get to choose your successor. This command accepts 1 argument, the name of the successor you wish to choose. The nickname must be registered to an account at the time you issue the command. To name nick1 as the successor to your channel, you would issue the following command:
/msg ChanServ set successor #channel nick1
Note that if you lose a channel because it is transferred to your successor in accordance with services and network policies, then the successor is under no obligation to transfer the channel back to you at any point in the future. They now own the channel and they are free to do with it as they please. They are not even obligated to allow you to remain in or use the channel afterwards. You should therefore only pick a successor that you consider trustworthy.
This command sets a URL for the channel. The URL will appear in info commands issued to services about your channel. This is useful if your channel has a specific website that offers channel support. You must choose your URL in accordance with the terms of service. This command accepts 1 argument, the URL to be set. By default, this setting is unset for new channel registrations. To set your URL to https://ravenchat.net you would use the following command:
/msg ChanServ set url #channel https://ravenchat.net