Azander: Created page with "{{Language|2.0/Modules/cs_xop}} {{Syntax|cs_xop|ChanServ|Anope}} ==
Description
== Maintains the xOP list for a channel. Alternative method..."

2014-05-06T21:14:20Z

Created page with "{{Language|2.0/Modules/cs_xop}} {{Syntax|cs_xop|ChanServ|Anope}} == <div class="moduleheader">Description</div> == Maintains the xOP list for a channel. Alternative method..."

New page

{{Language|2.0/Modules/cs_xop}}
{{Syntax|cs_xop|ChanServ|Anope}}

== <div class="moduleheader">Description</div> ==
Maintains the xOP list for a channel.

Alternative methods of modifying channel access lists are available. See /msg ChanServ HELP FLAGS for more information about the access list.

The higher xOP inherits all the lower xOP's privileges. These are listed in Highest to lowest order.

Where xOP is one of:

===== QOP =====
:Maintains the QOP (Quintessential OP, usually called Owner) list for a channel. The QOP commands are limited to founders (unless SECUREOPS is off). However, any user on the VOP list or above may use the QOP LIST command.
:
:Users who match an access entry on the AOP list receive the following privileges:
::ASSIGN, AUTOOWNER, FOUNDER, INFO, MODE, OWNER, OWNERME, PROTECT, SET, SIGNKICK

===== SOP =====
:Maintains the SOP (Super OP, sometimes called admin) list for a channel. The SOP commands are limited to founders (unless SECUREOPS is off). However, any user on the VOP list or above may use the SOP LIST command.
:
:Users who match an access entry on the SOP list receive the following privileges:
::ACCESS_CHANGE, AKICK, AUTOPROTECT, BADWORDS, MEMO, OP

===== AOP =====
:Maintains the AOP (Auto OP) list for a channel. The AOP commands are limited to founders (unless SECUREOPS is off). However, any user on the VOP list or above may use the AOP LIST command.
:
:Users who match an access entry on the AOP list receive the following privileges:
::GREET, AUTOOP, GETKEY, HALFOP, INVITE, OPME, PROTECTME, SAY, TOPIC

===== HOP =====
:Maintains the HOP (Half-OP) list for a channel. The HOP commands are limited to founders (unless SECUREOPS is off). However, any user on the VOP list or above may use the HOP LIST command.
:
:Users who match an access entry on the HOP list receive the following privileges:
::AUTOHALFOP, BAN, HALFOPME, KICK, UNBAN, VOICE

===== VOP =====
:Maintains the VOP (Voice) list for a channel. The VOP commands are limited to founders (unless SECUREOPS is off). However, any user on the VOP list or above may use the VOP LIST command.
:
:Users who match an access entry on the VOP list receive the following privileges:
::ACCESS_LIST, AUTOVOICE, FANTASIA, NOKICK, VOICEME

== <div class="moduleheader">Commands</div> ==
;QOP channel ADD mask
:The QOP ADD command adds the given nickname to the QOP list.
;QOP channel DEL {mask | entry-num | list}
:The QOP DEL command removes the given nick from the QOP list. If a list of entry numbers is given, those entries are deleted. (See the example for LIST below.)
;QOP channel LIST [mask | list]
:The QOP LIST command displays the QOP list. If a wildcard mask is given, only those entries matching the mask are displayed. If a list of entry numbers is given, only those entries are shown.
;QOP channel CLEAR
:The QOP CLEAR command clears all entries of the QOP list.

;SOP channel ADD mask
:The SOP ADD command adds the given nickname to the SOP list.
;SOP channel DEL {mask | entry-num | list}
:The SOP DEL command removes the given nick from the SOP list. If a list of entry numbers is given, those entries are deleted. (See the example for LIST below.)
;SOP channel LIST [mask | list]
:The SOP LIST command displays the SOP list. If a wildcard mask is given, only those entries matching the mask are displayed. If a list of entry numbers is given, only those entries are shown.
;SOP channel CLEAR
:The SOP CLEAR command clears all entries of the SOP list.

;AOP channel ADD mask
:The AOP ADD command adds the given nickname to the AOP list.
;AOP channel DEL {mask | entry-num | list}
:The AOP DEL command removes the given nick from the AOP list. If a list of entry numbers is given, those entries are deleted. (See the example for LIST below.)
;AOP channel LIST [mask | list]
:The AOP LIST command displays the AOP list. If a wildcard mask is given, only those entries matching the mask are displayed. If a list of entry numbers is given, only those entries are shown.
;AOP channel CLEAR
:The AOP CLEAR command clears all entries of the AOP list.

;HOP channel ADD mask
:The HOP ADD command adds the given nickname to the HOP list.
;HOP channel DEL {mask | entry-num | list}
:The HOP DEL command removes the given nick from the HOP list. If a list of entry numbers is given, those entries are deleted. (See the example for LIST below.)
;HOP channel LIST [mask | list]
:The HOP LIST command displays the HOP list. If a wildcard mask is given, only those entries matching the mask are displayed. If a list of entry numbers is given, only those entries are shown.
;HOP channel CLEAR
:The HOP CLEAR command clears all entries of the HOP list.

;VOP channel ADD mask
:The VOP ADD command adds the given nickname to the VOP list.
;VOP channel DEL {mask | entry-num | list}
:The VOP DEL command removes the given nick from the VOP list. If a list of entry numbers is given, those entries are deleted. (See the example for LIST below.)
;VOP channel LIST [mask | list]
:The VOP LIST command displays the VOP list. If a wildcard mask is given, only those entries matching the mask are displayed. If a list of entry numbers is given, only those entries are shown.
;VOP channel CLEAR
:The VOP CLEAR command clears all entries of the VOP list.

== <div class="moduleheader">Examples</div> ==
/msg ChanServ VOP #myChannel ADD Barney@*.example.com

/msg ChanServ HOP #myChannel DEL 3

/msg ChanServ AOP #myChannel LIST

/msg ChanServ SOP #myChannel CLEAR

== <div class="moduleheader">Default Configuration</div> ==

<div class="code">
<syntaxhighlight lang="cpp">
/*
* cs_xop
*
* Provides the command chanserv/xop.
* Provides the access system "XOP".
*
* Used for giving users access in channels. Many commands may be linked to chanserv/xop, but the
* privileges given by each is determined by the privilege:xop settings above. These commands should
* be ordered from highest to lowest, as each command inherits the privileges of the commands below
* it.
*
* The "LIST" subcommand of chanserv/xop will show only XOP access entries of the given XOP type. You
* can not view the entire access list at once, and instead should use another access system to do that.
*/
module { name = "cs_xop" }
command { service = "ChanServ"; name = "QOP"; command = "chanserv/xop"; group = "chanserv/access"; }
command { service = "ChanServ"; name = "SOP"; command = "chanserv/xop"; group = "chanserv/access"; }
command { service = "ChanServ"; name = "AOP"; command = "chanserv/xop"; group = "chanserv/access"; }
command { service = "ChanServ"; name = "HOP"; command = "chanserv/xop"; group = "chanserv/access"; }
command { service = "ChanServ"; name = "VOP"; command = "chanserv/xop"; group = "chanserv/access"; }
</syntaxhighlight></div>

2.0/Modules/cs xop - Revision history

Azander: Created page with "{{Language|2.0/Modules/cs_xop}} {{Syntax|cs_xop|ChanServ|Anope}} == Description == Maintains the xOP list for a channel. Alternative method..."

Azander: Created page with "{{Language|2.0/Modules/cs_xop}} {{Syntax|cs_xop|ChanServ|Anope}} ==
Description
== Maintains the xOP list for a channel. Alternative method..."