diff options
| author | Adam <Adam@anope.org> | 2013-04-11 15:58:59 -0500 |
|---|---|---|
| committer | Adam <Adam@anope.org> | 2013-04-11 15:58:59 -0500 |
| commit | 416eaa1e667186e0f935b3d08e98090753114d34 (patch) | |
| tree | be0fc59020fa74b926352cca75d91b7764649ee0 /data | |
| parent | ac19a5c24bb11af3ef55292946ab25cc250aaeea (diff) | |
Explain how privileges associate themselves with modes
Diffstat (limited to 'data')
| -rw-r--r-- | data/chanserv.example.conf | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/data/chanserv.example.conf b/data/chanserv.example.conf index 30d61a7c1..08954eaa6 100644 --- a/data/chanserv.example.conf +++ b/data/chanserv.example.conf @@ -230,6 +230,11 @@ chanserv * * If you loaded cs_xop, you may define a xop command to associate the privilege with. * + * The name of privileges are uesd to associate them with channel modes. If you are using an IRCd that allows you to define additional + * channel status modes, such as InspIRCd, you can associate privileges (and thus access levels, flags, xop) with the mode by naming + * the privileges appropriately. For example, if you had a channel mode called admin, you could create AUTOADMIN, ADMIN, and ADMINME + * privileges which would automatically be associated with that channel mode. + * * Defining new privileges here is not useful unless you have a module (eg, a third party one) made to check for * the specific level you are defining. * |