SET

Usage: SET #<room> <command> [<value>]

This command allows you to change settings for a room. You need MGR access or higher in the room (the founder always has it) to change these settings, and you must be identified to your nickname.

AGEGATE - Web chat: friendly card (CARD) or removal (KICK) for people under the age limit.

AGERESTRICT - Only let in people whose age (/age) is set, or high enough.

AUTOVOP - Give everyone VOP status on join if they do not already have a higher access level.

DESC - Change the description for a room.

EMAIL - Set an email for the room.

ENTRYMSG - A private notice every person who joins the room receives.

FOUNDER - Change the room's founder.

IDENT - Require ops to identify for their nicks before being opped/voiced by services.

KEEPTOPIC - Have services remember the topic when the room empties and reset it when someone next joins.

LEAVEOPS - Stop services from deopping people.

MEMOLEVEL - Set who may send a room memo.

MLOCK - Lock which modes can be set in the room.

OPGUARD - Allow only AOPs and higher to be opped.

PASSWD - Change the room's password.

RESTRICT - Allow only UOPs and higher to remain in the room.

TOPICLOCK - Restrict who may change the topic.

URL - Set or change the room's URL.

For more information on a setting:

/msg chanserv help <setting>

Example:

/msg chanserv help

Usage: SET #<room> AGEGATE [CARD|KICK]

Chooses what the web chat does with people who do not meet the room's age limit (ChanServ SET AGERESTRICT). CARD, the default, shows them a friendly card with the reason, a box to set their age and a button to try again, and they are not let in until they qualify. KICK lets them in and then shows them out with a notice, like the IRC programs. Either way, IRC programs always get the notice and the removal. The founder, IRC operators and services are never checked.

Examples:

/msg chanserv set #mature agegate kick
/msg chanserv set #mature agegate card

Usage: SET #<room> AGERESTRICT [ON|OFF|<minimum age>]

An age-restricted room only lets in people who are registered and have set their age. ON means an age must be set (every age is 18 or older). A number from 18 to 99 means the age must be at least that. Everybody else is sent a notice that explains what to do and is shown out of the room. The founder, IRC operators and services are not checked. In an Auditorium Rows event the master's restriction applies to the sub-rooms. People set their age with /age <years> (you must be 18 or older).

Examples:

/msg chanserv set #mature agerestrict on
/msg chanserv set #mature agerestrict 21
/msg chanserv set #mature agerestrict off

Privilege: SOP

Usage: SET #<room> AUTOVOP [on|off]

This command will set all users+v when they enter the room unless they are already being opped. Because the VOP list cannot accept open hostmasks like *@* you would use this command to give voice to all users. They will be voiced in the room and able to look at the room lists, but they will not be able to invite themselves into the room. 
If you ban them, they can revoice themselves and still talk, but if you kick them out then they cannot rejoin.

Example:

/msg chanserv set #downtown autovop on

This command is generally not useful. It will require anyone who causes problems to be banned and kicked, since they will be able to revoice themselves and speak through bans. It also makes your UOP/VOP/AOP/SOP/AKICK lists public to everyone on the network. However, if you want your lists to be public, or have a reason to voice everyone, this will let you.

Usage: SET #<room> DESC <description>

Used to change the description of your room; it will be displayed to users when they request the room information with the info command.

Example:

/msg chanserv set #downtown desc the dragon room

Like the topic, some people may use the description to decide whether they wish to join the room. However, the description can only be set by the founder, and is generally changed less often than the topic. Most people expect the description to give some information about the purpose of the room.

Usage: SET #<room> EMAIL <email address>

Used to set an email address attached to a room. The email will show in the room's info.

Example:

/msg chanserv set #downtown rich@confrooms.org

This is a good way to give people a contact for any problems or questions related to your room. However, it also gives people an email address that they can send to for any reason, and you might not want to make one public.

Usage: SET #<room> ENTRYMSG [<text>]

Everybody who joins the room gets this private notice from ChanServ. %n is replaced by their nickname and %c by the room name. Without text the message is removed. SOPs and the founder can set it. In an Auditorium Rows event it is shown in every sub-room.

Example:

/msg chanserv set #support entrymsg Welcome %n! Ask your question and someone will help.

Usage: SET #<room> FOUNDER

Used to change the founder of a room to the nick of the person sending the command. The new founder must be using a registered nick. You must identify with the room's password before trying to set the founder.

Example:

/msg chanserv set #conferencerooms founder

If you change the nickname that you use, you should set all of your rooms to the new nick, because the room will drop if the founder's nick expires. The set founder command can also be used if you no longer want the room and wish to give it to someone else. Just give the person the password and he/she can identify and set founder it.

Usage: SET #<room> IDENT [on|off]

If you set ident on then everyone will have to identify to nickserv with their nick's password before they will get any status in the room. No one will be opped, not even the founder, without first identifying. If you enter the room and then identify, services will +u, voice, or op you as appropriate after the identify command goes through.

Example:

/msg chanserv set #downtown ident on

Ident is a good security precaution because it requires every person to use a password before being recognized. This prevents anyone from being opped simply because they match someone's access list. Access lists may be set loosely.

Usage: SET #<room> KEEPTOPIC [on|off]

Use this to have services remember the current topic and reset it if the room empties and then is reformed. It does not provide any security with regards to whom may set the topic, see mode +t or topiclock to restrict who may set the topic. Keeptopic can only be turned on if topiclock is first turned off since topiclock includes the functionality of keeptopic and also provides topic security.

Example:

/msg chanserv set #services keeptopic on

This is a good command to use if you do not intend to use topiclock. While a topic may not be essential for your room, there is rarely a reason to not keep one in memory. It is a nice aesthetic touch, and if you set useful topics, it can be helpful.

USAGE - SET #<room> LEAVEOPS [on|off]

This command will leave the first user who joins the channel opped in the channel. This command will not be active if OPGUARD is set on the channel. OPGUARD and IDENT take precedence over this command.

Example:

/msg ChanServ set #downtown leaveops on

/msg ChanServ set #downtown leaveops off

Usage: SET #<room> MEMOLEVEL [UOP|VOP|AOP|SOP|FOUNDER]

This setting has a default of UOP when you register a room. You can however change the memolevel. A room memo is a memo sent to every registered nick in any of the room's lists or to everyone in a specified list such as AOP. This command lets you restrict who can send them to the people of your room. 

Example:
 memolevel aop

Memos are useful for announcing policies or information everyone in the room might need. For example, if you do not add AOPs often, you could send a memo to the entire room informing them of a new AOP. UOPs and such might memo information about someone who has been causing problems in the room. 
If the people generally will not mind getting memos from the room, you should set the access level low, but if you want to make sure that memos are only sent when they are actually important, you might want to set it higher and only use it rarely. See the memoserv commands send and sendto.

Usage: SET #<room> MLOCK <modes>

The founder of a room can lock the modes of the room by using the mlock command. When a room is registered a default mlock of +rtn-k is set. See the room modes list or use /hs cmodes to see what each mode does. The modes that are mlocked on, with the + sign, will be set by services after the room empties when the first person rejoins. Services will also prevent anyone, regardless of their 
status in the room, from turning those modes off. If the founder wishes to change them he/she must first change the mlock. Services will remove any mode set for the room that is mlocked off, which is symbolized with the - sign. Some modes can only be set by network operators (such as M) and some modes cannot be locked on (k and l). If you try to lock a mode that cannot be mlocked the mlock 
will be set without those modes in it.

Example:

/msg chanserv set #conferencerooms mlock +stn-kl

Mlocks are useful for defining what kind of room you are running. If you're not sure whether some modes might be needed for management, do not mlock them positively or negatively. If you know that you never want your room to be secret or private, then you can mlock it to include -sp. 
Similarly, you can mlock modes you never want off, such as n (no outside messages) which almost all rooms will want to keep. Mlocks allow you to set up your room once and then not have to worry about it, since services will maintain it the way you want it.

Usage: SET #<room> OPGUARD [on|off]

If you set opguard on, only your AOp/SOps can be opped in your room. Anyone else that is opped will automatically be deopped by services. People can still be voiced. Network operators can be opped in rooms with opguard on. This way if problems do come up, opers can be invited in to help out and be opped in the room.

Example:

/msg chanserv set #downtown opguard on

This can be a useful security measure. Most rooms will not have a problem with allowing their AOPs to op whomever they trust, that is to mode them +o in the room. But use this if you are having problems with people opping inappropriately or want to strictly control who has ops. 
This also affects the SOPs and founder, but they could always add someone to the AOP list at any time they wanted to op the person. The downside to opguard is that if the room runs into problems or runs low on ops, then the current ops cannot op more people to help them out, although they can still have network operators assist them.

Usage: SET #<room> PASSWD <password>

This is used to change the password for your room. You must identify with the old password before you can set a new one.

Example:

/msg chanserv set #downtown passwd newp4ss

Use this if you are having trouble remembering your old password and want to change it to something better for you. You should always change the password immediately if it accidentally gets revealed, for example by missending the identify command.

Usage: SET #<room> RESTRICT [on|off]

Used to allow only those in the room lists to join the room. Everyone else will be kick/banned as they join.

Example:

/msg chanserv set #support restrict on

A good command to keep a room completely private and control who enters. The downside is that you must add an entry for everyone whom you want to allow to join. You cannot just invite someone in when you want to, you must first at least give them UOP access. Which also means that everyone allowed into the room can look at lists and see whom else is allowed in.

Usage: SET #<room> TOPICLOCK [OFF|AOP|SOP|FOUNDER]

This setting will allow only the ops at or above the level you set to change your topic. Anyone who is not authorized to change the topic who tries to change it will have the topic reset back to what it was. The only time when someone of lower status than you set the topiclock to can change the topic is if no topic has been set in the room. 
As soon as there is a topic for services to set it back to, the topiclock will be enforced. Services will also set the topic back after the room empties when someone rejoins. Topiclock in any position other than off includes the functionality of keeptopic, and if set on, keeptopic will automatically be removed if it was on.

Example:

/msg chanserv set #support topiclock aop

Topiclock is a good way to control what topic is showing for your room. Since the topic is one of the first things people see about your room, you want it to represent you well. What level you want to restrict topic changes to will depend upon how you choose to give people AOPs and such, and how important the topic is to your room. 
If your room is a place just for you to hang out with your friends you might prefer to leave it unlocked and watch as people set amusing topics and change it often.

Usage: SET #<room> URL <url>

Used to change the url for your room. The URL of your room will be available to any user that requests info on your room. Rooms do not need attached URLs.

Example:

/msg chanserv set #ConferenceRooms url http://www.conferencerooms.org

Setting an URL can be very useful if it contains rules that relate to the room or frequently asked questions. You can set the URL to anything, but people will generally expect the URL to relate to the room in some way. More social rooms sometimes have web sites that give information about the people who regularly chat there.