Un article de Wikipédia, l'encyclopédie libre.

ChanServ gives normal users the ability to maintain control of a channel, without the need of a bot. Channel takeovers are virtually impossible when a channel is registered with ChanServ. Registration is a quick and painless process. Once registered, the founder can maintain complete and total control over the channel. Please note that channels will expire after 45 days of inactivity, or if there are no eligible channel successors. Activity is defined as a user added to the access list being on the channel. Successors are primarily those who have the +R flag set on their account in the channel, although other people may be chosen depending on their access level and activity.

Whenever you see < > in the FAQ below, this will indicate you need to change that text when you type the command yourself. Whenever you see brackets [ ], this will indicate optional parameters. You do not need to include either of these when actually typing the command.

To send commands to ChanServ, you may use any of the following:
/msg ChanServ
/ChanServ
/CS

ChanServ FAQ

How do I register a channel?

To register a channel, you must have a NickServ account, and be identified (/NS IDENTIFY <nick> <password>). If you do not have a NickServ account, click here to learn how to do so.

Once you have identified to NickServ, simply type /CS REGISTER #channel, and the channel will be yours. Note that you must actually be in the channel, and that you must be an Op as well.

How do I add users to my channel?

There are two ways to add users to a channel. One is by the default xOP system (VOP, HOP, AOP, SOP), and the other is by adding specific Flags. While the first method is easier to use, the second allows for more specific access levels. Let's look at both:

xOP (Easy)

The xOP commands allow you to maintain channel access lists, which can contain registered nicks or hostmasks (nick!user@host).

xOP is basically just a general term for VOP, HOP, AOP, and SOP. What do these mean?

xOP	Explanation	Flags

SOP	SuperOP (admin)	+voOtsrifhA

AOP	AutoOp	+voOtrihA

HOP	HalfOP	+vVthHA

VOP	VOiced People	+VA

So as you can see, VOP, HOP, AOP, and SOP, are simply shortcuts (or Templates) for a specific set of flags (see below for a listing of flags and what each one does). Instead of memorizing what each Flag does, you simply use the xOP templates.

Syntax: VOP|HOP|AOP|SOP <#channel> ADD|DEL|LIST <nickname|hostmask>

Examples:
/msg ChanServ VOP #wikipedia-fr ADD Martin
/msg ChanServ VOP #wikipedia-fr ADD Martin!*@gmail.com
/msg ChanServ AOP #wikipedia-fr DEL Martin
/msg ChanServ SOP #wikipedia-fr LIST

Flags (Advanced)

The FLAGS command allows for channel privilege granting/removal on a more specific, non-generalized level. It supports both nicknames and hostmasks as targets.

When given only the channel argument, a listing of permissions granted to users will be displayed.
Syntax: FLAGS <#channel>

Otherwise, an access entry is modified. A modification may be specified by a template name (changes the access to the template) or a flags change (starts with + or -). See the TEMPLATE help entry for more information about templates.

If you are not the founder, you may only manipulate flags you have yourself, and may not edit users that have flags you don't have. For this purpose, +v grants +V, +h grants +H, +o grants +O and +r grants +b.

If you do not have +f you may still remove your own access with -*.

Permissions:



+v		- Enables use of the voice/devoice commands.
+V		- Enables automatic voice.
+h		- Enables use of the halfop/dehalfop commands.
+H		- Enables automatic halfop.
+o		- Enables use of the op/deop commands.
+O		- Enables automatic op.
+s		- Enables use of the set command.
+i		- Enables use of the invite command.
+r		- Enables use of the kick, ban, and kickban commands.
+R		- Enables use of the recover and clear commands.
+f		- Enables modification of channel access lists.
+t		- Enables use of the topic and topicappend commands.
+A		- Enables viewing of channel access lists.
+b		- Enables automatic kickban.

The special permission +* adds all permissions except +b.
The special permission -* removes all permissions including +b.

Syntax: FLAGS <#channel> [nickname|hostmask template]
Syntax: FLAGS <#channel> [nickname|hostmask flag_changes]

Examples:
/msg ChanServ FLAGS #wikipedia-fr
/msg ChanServ FLAGS #wikipedia-fr foo!*@bar.com VOP
/msg ChanServ FLAGS #wikipedia-fr foo!*@bar.com -V+oO
/msg ChanServ FLAGS #wikipedia-fr foo!*@bar.com -*
/msg ChanServ FLAGS #wikipedia-fr foo +oOtsi
/msg ChanServ FLAGS #wikipedia-fr BadUser!*@*.troubleisp.net +b

Templates

Just as VOP, HOP, AOP, and SOP are the default Templates for specific sets of flags, you can create your own set of templates for specific access levels.

When given only the channel argument, a listing of templates for the channel will be displayed.

Syntax: TEMPLATE <#channel>

Otherwise, a template is modified. A modification may be specified by a template name (copies the template) or a flags change (starts with + or -). Templates cannot be the empty set (making a template empty deletes it).

Template modifications do not affect existing access entries in any way. There is a limit on the length of all templates on a channel.

If you are not the founder, similar restrictions apply as in FLAGS (see above).

Syntax: TEMPLATE <#channel> [template oldtemplate]
Syntax: TEMPLATE <#channel> [template flag_changes]

Examples:
/msg ChanServ TEMPLATE #wikipedia-fr
/msg ChanServ TEMPLATE #wikipedia-fr regular VOP
/msg ChanServ TEMPLATE #wikipedia-fr user +A
/msg ChanServ TEMPLATE #wikipedia-fr co-founder +*-OH
/msg ChanServ TEMPLATE #wikipedia-fr op -*+vVhoti
/msg ChanServ TEMPLATE #wikipedia-fr obsoletetemplate -*

(The words in bold represent the template names.)

Once you have created a Template, you can add users with it by typing:
/msg ChanServ FLAGS <#channel> <nick> <template name>

Example:
/msg ChanServ FLAGS #wikipedia-fr Martin co-founder

How do I see who has access in a channel?

There's two ways to view who has access in a channel.

You can either view ALL accesses in the form of Flags:
Syntax: FLAGS <#channel>

Or you can view specific accesses by type:
Syntax: VOP|HOP|AOP|SOP <#channel> LIST

Examples:
/msg ChanServ FLAGS #wikipedia-fr
/msg ChanServ AOP #wikipedia-fr LIST
/msg Chanserv VOP #wikipedia-fr LIST

What settings are available through ChanServ?

The following options can be changed with the SET command:

Founder

SET FOUNDER allows you to set a new founder of the channel. The new founder has to execute the same command to confirm the transfer.

Syntax: SET <#channel> FOUNDER <newnick>

If the new founder has not yet confirmed the transfer, you can cancel it by specifying your own nick as the new founder.

Syntax: SET <#channel> FOUNDER <yournick>

Example:
/msg ChanServ SET #wikipedia-fr FOUNDER Teckna

Mlock

MLOCK (or "mode lock") allows you to enforce a set of modes on a channel. This can prevent abuse in cases such as +kl. It can also make it harder to fight evil bots, be careful.

Syntax: SET <#channel> MLOCK <modes>

Examples:
/msg ChanServ SET #wikipedia-fr MLOCK +nt-ilpksm
/msg ChanServ SET #wikipedia-fr MLOCK +nt
/msg ChanServ SET #wikipedia-fr MLOCK -kl
/msg ChanServ SET #wikipedia-fr MLOCK OFF

Secure

SET SECURE prevents anyone that's not on the channel's access lists from gaining operator or halfop status on the channel. This is useful if you're paranoid.

Syntax: SET <#channel> SECURE ON|OFF

Example:
/msg ChanServ SET #wikipedia-fr SECURE ON

Verbose

SET VERBOSE ON sends a notice to the channel when someone makes changes to the access lists.

SET VERBOSE OPS sends a notice to the channel operators when someone makes changes to the access lists.

Syntax: SET <#channel> VERBOSE ON|OPS|OFF

Example:
/msg ChanServ SET #wikipedia-fr VERBOSE ON

URL

SET URL allows you to change or set the URL associated with a channel. This is shown to all users joining the channel. Specify an <url> of NONE to clear the URL.

Syntax: SET <#channel> URL <url>

Example:
/msg ChanServ SET #wikipedia-fr URL http://ircwiki.barafranca.com

Email

SET EMAIL allows you to change or set the Email address associated with a channel.

Syntax: SET <#channel> EMAIL <email>

Example:
/msg ChanServ SET #wikipedia-fr Email feds@barafranca.com

Entrymsg

SET ENTRYMSG allows you to change or set the Entrymsg associated with a channel. This is shown to all users joining the channel.

Syntax: SET <#channel> ENTRYMSG <text|OFF>

Examples:
/msg ChanServ SET #wikipedia-fr ENTRYMSG Welcome to #wikipedia-fr! /msg ChanServ SET #wikipedia-fr ENTRYMSG OFF

Keeptopic

SET KEEPTOPIC enables restoration of the old topic after the channel has become empty. In some cases, it may revert topic changes after netsplits or services outages, so it is not recommended to turn this on if your channel tends to never empty.

Syntax: SET <#channel> KEEPTOPIC <on/off>

Example:
/msg ChanServ SET #wikipedia-fr KEEPTOPIC ON

Property

SET PROPERTY manipulates metadata associated with a channel.

To delete a metadata entry, specify the name and leave the value blank.

Syntax: SET <channel> PROPERTY <name> [value]

Example:
/msg ChanServ SET #atheme PROPERTY URL http://www.atheme.org/
/msg ChanServ SET #meat PROPERTY VEGETABLES

Auto Kick

The AKICK command allows you to maintain channel ban lists. Users on the AKICK list will be automatically kickbanned when they join the channel, removing any matching ban exceptions first.

Syntax: AKICK <#channel> ADD|DEL|LIST <nickname|hostmask>

Example:
/msg ChanServ AKICK #foo ADD Doncabelero
/msg ChanServ AKICK #foo ADD mowcow!*@blabla.com
/msg ChanServ AKICK #foo DEL Doncabelero
/msg ChanServ AKICK #foo LIST

What do I do if someone takes over my channel?

In the event of a takover, Chanserv's RECOVER command will allow you to regain control of your channel. To use the RECOVER command, you must either be the founder of a channel, or hold the +R flag in the access list.

Once the RECOVER command has been used, everyone will be deopped, limit and key will be cleared, all bans matching you are removed, a ban exception matching you is added (in case of bans the services can't see), the channel is set invite-only and moderated, and you are invited.

If you are on channel, you will be opped and no ban exception will be added.

Example:

/msg ChanServ RECOVER #channel

How do I ban people through chanserv?

You can ban people in your channel with either the BAN command or the KICKBAN command. The KICKBAN command will also remove the offending user(s) from the channel, and any matching ban exceptions will be removed. However, while the BAN command takes nicks as well as hosts, KICKBAN only works with nicks.

Syntax: BAN <#channel> <nick|hostmask> [reason] Syntax: KICKBAN <#channel> <nick> [reason]

Examples:
/msg ChanServ BAN #wikipedia-fr *!*@bad.guys
/msg ChanServ KICKBAN #wikipedia-fr BadGuy go away

How can I invite myself into a channel?

INVITE requests services to invite you to the specified channel. This is useful if you use the +i channel mode.

Syntax: INVITE <#channel>

Examples:
/msg ChanServ INVITE #wikipedia-fr

Note that by default, only AOPs and higher can invite themselves into a channel. However, all you need to invite yourself is the +i user flag (see Flags info). So in theory, even HOPs and VOPs could invite themselves, as long as you gave them the +i user flag.

Clear

The CLEAR command allows clearing or all users or all bans from a channel.

The following uses are available:

Clear all users:
/msg ChanServ CLEAR #wikipedia-fr USERS

Clear all bans (optionally also ban exceptions, etc):
/msg ChanServ CLEAR #wikipedia-fr BANS
/msg ChanServ CLEAR #wikipedia-fr BANS beI

How do I unregister a channel?

DROP allows you to "unregister" a registered channel. Once you DROP a channel all of the data associated with it (access lists, etc) are removed and cannot be restored.

Syntax: DROP <#channel>

Example:
/msg ChanServ DROP #wikipedia-fr

How do I transfer a channel?

In some cases, you might want to transfer the channel to someone else instead of directly deleting the channel. SET FOUNDER allows you to set a new founder of the channel. The new founder has to execute the same command to confirm the transfer.