ChanServ

Many of the OperServ commands are listed in the OperServ help files however they are issued with different services agents such as NickServ or ChanServ, the reason why they are listed under OperServ is because you need OperServ access to issue these commands. OperServ access levels are Services Administrator also referred to as SA, ChanServ Super Op aka CSop, and root administrator.

Example:

/os help chanserv close

CLOSE 

Format: /cs close #room

This command allows you to "close" a room. When a room is closed, no one can enter it and the founder cannot identify to it. The room will expire normally, but its registration information is retained in memory in case you reopen the room before it expires. The network operator or CSop must have the appropriate flag 'CCLOSE' in order to use this command. Also see the reopen command.

Example:

/cs close #webchat

The close command should be used to remove rooms that have been breaking network rules. It can be used either temporarily, as a warning, or permanently. It has the advantage over dropping the room immediately in that it forces people to wait to reregister the room, and gives people warning that the room will become available again. It also allows the decision to be easily reversed before it expires if there is any question as to whether the room should have been closed.

DROP 

Format: /cs drop #room

This command will drop the room without you having to identify as the founder. You cannot drop a room while it is closed.

Example:

/cs drop #support

This will quickly and easily remove a room that you do not want on your network. This is useful for room names that get registered, but are not acceptable. You can also use this if you want to start a room over, just drop it and then register it.

FTRANSFER 

Format: /cs ftransfer #room nick

This command will transfer foundership of a room to another user. You do not need to identify with the password to do so. Services will set the password to a randomly generated string, and the recipient will receive a memo with it.

Example:

/cs ftransfer #spiderslair Web

This is a very easy way to transfer ownership of a room. The recipient does not need to identify or set founder, as soon as the command is given, services makes that person the new founder.

GETPASS 

Format: /cs getpass #room

This will get the password for a room. Sometimes founders forget the password which is necessary for setting certain options in the room. .

Example:

/cs getpass #ConferenceRoom

If you are getpassing a room for a user, you will probably want to email the password to the address set in the founder's nick info. This is more secure than just telling the password over chat, because it may be possible to impersonate the founder.

INFO 

Format: /cs info #room

This will show you a room's info including any fields that are only visible to opers, such as marks.

Example:

/cs info #spiderslair

Whenever you do an info command while opered it will show you the additional information only available to opers. It is generally good to info a room if you are dealing with it in almost any way. While usually there won't be much interesting, you might notice something that you will find helpful.

LIST 

Format: /cs list param hits

You can list rooms matching a value you have selected. You can list from 2 to 250 rooms. If you do not specify the number of hits it will show you everything it finds up to the limit of 250.

Examples:

/cs list *web*

/cs list *teen* 10

This can be useful if you need a particular type of room but aren't sure what it might be called. For example, you could try to find a help room about Windows by doing a search on *windows*, but this might miss #win95. A search done on *win* might turn up unrelated things like #winners. Another way to use this is to try to find rooms to be investigated for violating your network's rules. For example, you might not allow rooms about illegal file sharing, commonly called "warez". So you could do a search on *warez*, however, you should remember that if you try to find rooms this way, then people will start disguising their room names and making them look more innocent. The downside to that is that people may stumble into a room containing things they did not want to see.

MARK 

Format: /cs mark #room on|off reason

The mark command allows you to prevent other CSops from doing a GETPASS or a SETPASS to a room. It can be used to indicate that you are dealing or dealt with a room. Note: Root users can override the mark command.

Example:

/cs mark #spiderslair password was emailed to founder

The mark is a versatile command in that you can come up with your own uses for mark. The mark will show up in the chanserv info to all CSops, so it can be used to signal anything. It was designed to allow CSops to investigate a room without having anyone else tampering with it, and to mark rooms that have been investigated so that other CSops do not waste time on them. Sometimes users will keep going to different CSops to try to get a password, and the mark helps to deal with this.

REGISTER 

Format: /cs register #room password description

CSops or operators with the appropriate flag (CFORCEREG) can register a room without having op status in the room. Note: Root admins can register a room without being in it at the time.

Example:

/cs register #webnet WebPass General Chat

This is another command to allow you to take control of a room. It is rarely needed, but if an unregistered room is causing problems, you can register it and take control.

REOPEN 

Format: /cs reopen #room

This command allows you to "OPEN" a room that had previously been closed. The registration information reverts to what it was before the room was closed. Operators with the 'CCLOSE' flag may REOPEN rooms.

Example:

/cs reopen #webchat

This is useful if closing the room was only a temporary measure to punish the founder, or if closing the room turned out to be a mistake.

SETPASS 

Format: /cs setpass #room password

This command allows you to set the password for a room, without using the room in question and without being identified to it.

Example:

/cs setpass #webchat webPass

This is useful for similar reasons as ftransfer. Often you may want to make sure a particular person has the password for the room, but if you are not certain that they set the last password, you should not tell them what it was. Since many people reuse passwords, being given a password used on a chat network may allow you to access other things for which they need a password. While recycling passwords is not a safe thing to do, it is good to help prevent people from being hurt by their own mistakes.

UNIDENTIFY 

Format: /cs unidentify #room

ChanServ maintains a list of rooms that you have identified to. The unidentify command allows you to remove an entry from that list, effectively making ChanServ unaware of the fact that you have identified to a specified room.

Example:

/cs unidentify #support

If you needed to identify to take care of something, but do not normally have founder access, you may wish to unidentify. You also might want to unidentify if you want to enter the room without being given operator status automatically in the room.

WIPE 

Format: /cs sop|aop|vop|uop|akick #room wipe

This command lets you remove all of the entries for any list, including the AKICK list for a room

Examples:

/cs sop #ConferenceRoom wipe

/cs akick #spiderslair wipe

/cs vop #webchat wipe

If a list is very poorly set up, sometimes wiping it and re-adding the entries that you actually want is the easiest way to fix it. Otherwise you would have to delete every entry that you did not want manually.