Difference between revisions of "Channel Management 101"

From Rizon Wiki
Jump to navigation Jump to search
m
Line 2: Line 2:


So you managed to register a channel, but didn't get the results you were expecting?
So you managed to register a channel, but didn't get the results you were expecting?
* Where's my ~ mark?
* Where's my <code>~</code> mark?
* Why can't I give the & prefix to my trusted users?
* Why can't I give the <code>&</code> prefix to my trusted users?
* And most of all... what is this crazy XOP business, anyway? I can't add users with numerical access levels anymore!
* And most of all... what is this crazy XOP business, anyway? I can't add users with numerical access levels anymore!


Line 11: Line 11:
===Ownermode and Protectmode===
===Ownermode and Protectmode===


To get these modes (owner = <code>~</code> / protect = <code>&</code>) enabled on your channel:
* If you want <code>~</code>, enable ownermode: <code>/msg ChanServ SET <em>#channel</em> OWNERMODE ON</code>


* To enable ownermode: <code>/msg ChanServ set #channel ownermode ON</code>
* If you want <code>&</code>, enable protectmode: <code>/msg ChanServ SET <em>#channel</em> PROTECTMODE ON</code>
 
* To enable protectmode: <code>/msg ChanServ set #channel protectmode ON</code>




Line 44: Line 42:
To look through the XOP list to see which user has what level, type:
To look through the XOP list to see which user has what level, type:


<code>/msg ChanServ ACCESS #channel LIST</code>
<code>/msg ChanServ ACCESS <em>#channel</em> LIST</code>


====Adding a VOP====
====Adding a VOP====


<code>/msg ChanServ VOP #channel ADD nick</code>
<code>/msg ChanServ VOP <em>#channel</em> ADD <em>nick</em></code>


All VOPs get a voice (<code>+</code>) in the channel upon entering it, and as a result will be able to chat in the channel even while the channel is moderated (channel mode <code>+m</code>).
All VOPs get a voice (<code>+</code>) in the channel upon entering it, and as a result will be able to chat in the channel even while the channel is moderated (channel mode <code>+m</code>).
Line 54: Line 52:
====Adding a HOP====
====Adding a HOP====


<code>/msg ChanServ HOP #channel ADD nick</code>
<code>/msg ChanServ HOP <em>#channel</em> ADD <em>nick</em></code>


All HOPs get a halfop (<code>%</code>) in the channel upon entering it, and will be allowed to kick/ban all users that have halfop status or below. They will also be able to give voice (<code>+</code>) and halfop (<code>%</code>) to other users, as well as taking it away. However, if the channel is set to paranoia (channel mode <code>+p</code>), they will not be able to kick other halfops, or fiddle around with <code>+h</code>/<code>-h</code>. They also have the power to set the channel topic, even if channel mode <code>+t</code> (topic lock) is set.
All HOPs get a halfop (<code>%</code>) in the channel upon entering it, and will be allowed to kick/ban all users that have halfop status or below. They will also be able to give voice (<code>+</code>) and halfop (<code>%</code>) to other users, as well as taking it away. However, if the channel is set to paranoia (channel mode <code>+p</code>), they will not be able to kick other halfops, or fiddle around with <code>+h</code>/<code>-h</code>. They also have the power to set the channel topic, even if channel mode <code>+t</code> (topic lock) is set.
Line 60: Line 58:
====Adding a AOP====
====Adding a AOP====


<code>/msg ChanServ AOP #channel ADD nick</code>
<code>/msg ChanServ AOP <em>#channel</em> ADD <em>nick</em></code>


All AOPs get op (<code>@</code>) status in the channel upon entering it, and will be allowed to kick/ban all users that have op status or below. They will also be able to give voice (<code>+</code>), halfop (<code>%</code>), as well as op (<code>@</code>) to other users, and also have the power to take the mode away.
All AOPs get op (<code>@</code>) status in the channel upon entering it, and will be allowed to kick/ban all users that have op status or below. They will also be able to give voice (<code>+</code>), halfop (<code>%</code>), as well as op (<code>@</code>) to other users, and also have the power to take the mode away.
Line 66: Line 64:
====To add a user as a SOP====
====To add a user as a SOP====


<code>/msg ChanServ SOP #channel ADD nick</code>
<code>/msg ChanServ SOP <em>#channel</em> ADD <em>nick</em></code>


All SOPs get protectop (<code>&</code>) status in the channel upon entering it, and will be allowed to kick/ban all users that have op status or below. They will also be able to give voice (<code>+</code>), halfop (<code>%</code>), as well as op (<code>@</code>) to other users, and also have the power to take the mode away.
All SOPs get protectop (<code>&</code>) status in the channel upon entering it, and will be allowed to kick/ban all users that have op status or below. They will also be able to give voice (<code>+</code>), halfop (<code>%</code>), as well as op (<code>@</code>) to other users, and also have the power to take the mode away.


Additionally, protectops cannot be kicked from the channel, unless the kick is from the channel owner. SOPs can also modify the akick list (<code>/msg chanserv HELP AKICK</code>).
Additionally, protectops cannot be kicked from the channel, unless the kick is from the channel owner. SOPs can also modify the akick list (<code>/msg ChanServ HELP AKICK</code>).


'' '''Important''': Every level can add or delete people to levels below them, so a SOP can add VOP, HOP and AOPs, while a HOP can only add VOPs. The founder can change all levels.''
'' '''Important''': Every level can add or delete people to levels below them, so a SOP can add VOP, HOP and AOPs, while a HOP can only add VOPs. The founder can change all levels.''
Line 83: Line 81:
If you'd like to get rid of the XOP system in your channel altogether and change to the ACCESS system, all you must do is enter:
If you'd like to get rid of the XOP system in your channel altogether and change to the ACCESS system, all you must do is enter:


<code>/msg ChanServ SET #channel ACCESSTYPE ACCESS</code>
<code>/msg ChanServ SET <em>#channel</em> ACCESSTYPE ACCESS</code>


====Adding user to ACCESS====
====Adding user to ACCESS====


To add a user to the access list: <code>/msg ChanServ ACCESS #channel ADD nick level</code>
To add a user to the access list: <code>/msg ChanServ ACCESS <em>#channel</em> ADD <em>nick</em> <em>level</em></code>


=====Default Levels=====
=====Default Levels=====
Line 105: Line 103:
To view a list of features: <code>/msg ChanServ HELP LEVELS DESC</code>
To view a list of features: <code>/msg ChanServ HELP LEVELS DESC</code>


To view the current levels list: <code>/msg ChanServ LEVELS #channel LIST</code>
To view the current levels list: <code>/msg ChanServ LEVELS <em>#channel</em> LIST</code>


Changing required access level for a feature: <code>/msg ChanServ LEVELS #channel SET feature level</code>
Changing required access level for a feature: <code>/msg ChanServ LEVELS <em>#channel</em> SET <em>feature</em> <em>level</em></code>


Disabling a feature (so only the founder can use it): <code>/msg ChanServ LEVELS #channel DISABLE type</code>
Disabling a feature (so only the founder can use it): <code>/msg ChanServ LEVELS <em>#channel</em> DISABLE <em>type</em></code>


Resetting default levels: <code>/msg ChanServ LEVELS #channel REST</code>
Resetting default levels: <code>/msg ChanServ LEVELS <em>#channel</em> RESET</code>


Give auto-voice to all users joining the channel (''XOP must be disabled for this to work'') : <code>/msg ChanServ LEVELS #channel SET autovoice 0</code>
Give auto-voice to all users joining the channel (''XOP must be disabled for this to work'') : <code>/msg ChanServ LEVELS <em>#channel</em> SET AUTOVOICE 0</code>




Line 128: Line 126:
Start by looking through the botlist for any specific bot you want assigned: <code>/msg BotServ BOTLIST</code>
Start by looking through the botlist for any specific bot you want assigned: <code>/msg BotServ BOTLIST</code>


Once you find one that you like, assign it with: <code>/msg BotServ ASSIGN #channel BotNickHere</code>
Once you find one that you like, assign it with: <code>/msg BotServ ASSIGN <em>#channel</em> <em>bot</em></code>


==Wrapping Up==
==Wrapping Up==
Line 136: Line 134:
There are all sorts of neat and useful things that can be done with ChanServ. To learn more, type  
There are all sorts of neat and useful things that can be done with ChanServ. To learn more, type  


<code>/msg ChanServ help</code>
<code>/msg ChanServ HELP</code>


which covers everything in this document and more.
which covers everything in this document and more.
Line 148: Line 146:


For further reading on Channel Management, please read [[Channel Management 102]]
For further reading on Channel Management, please read [[Channel Management 102]]
Contributed by [[kokizzzle]]

Revision as of 17:16, 25 September 2011

Starting off...

So you managed to register a channel, but didn't get the results you were expecting?

  • Where's my ~ mark?
  • Why can't I give the & prefix to my trusted users?
  • And most of all... what is this crazy XOP business, anyway? I can't add users with numerical access levels anymore!

These seem to be the most common questions among our users who have registered a channel for their first time, so this post is here to guide you through the process to get what you were expecting.


Ownermode and Protectmode

  • If you want ~, enable ownermode: /msg ChanServ SET #channel OWNERMODE ON
  • If you want &, enable protectmode: /msg ChanServ SET #channel PROTECTMODE ON


Managing Access

There are three different types of systems to manage who has access on your channel:

  • XOP
  • ACCESS
  • FLAGS

By default, your channel uses XOP since it is the simplest, so the other two aren't relevant unless you want more control.


Using the XOP system

The XOP system is the default form of access on Rizon.

Each user is listed under a certain level, which automatically grants them a status on the channel:

  • VOP corresponds to a +
  • HOP corresponds to a %
  • AOP corresponds to a @
  • SOP corresponds to a &

The XOP system only sets 4 fixed levels and makes for simple channel management. For more advanced channel management, see ACECSS below.

Viewing the XOP list

To look through the XOP list to see which user has what level, type:

/msg ChanServ ACCESS #channel LIST

Adding a VOP

/msg ChanServ VOP #channel ADD nick

All VOPs get a voice (+) in the channel upon entering it, and as a result will be able to chat in the channel even while the channel is moderated (channel mode +m).

Adding a HOP

/msg ChanServ HOP #channel ADD nick

All HOPs get a halfop (%) in the channel upon entering it, and will be allowed to kick/ban all users that have halfop status or below. They will also be able to give voice (+) and halfop (%) to other users, as well as taking it away. However, if the channel is set to paranoia (channel mode +p), they will not be able to kick other halfops, or fiddle around with +h/-h. They also have the power to set the channel topic, even if channel mode +t (topic lock) is set.

Adding a AOP

/msg ChanServ AOP #channel ADD nick

All AOPs get op (@) status in the channel upon entering it, and will be allowed to kick/ban all users that have op status or below. They will also be able to give voice (+), halfop (%), as well as op (@) to other users, and also have the power to take the mode away.

To add a user as a SOP

/msg ChanServ SOP #channel ADD nick

All SOPs get protectop (&) status in the channel upon entering it, and will be allowed to kick/ban all users that have op status or below. They will also be able to give voice (+), halfop (%), as well as op (@) to other users, and also have the power to take the mode away.

Additionally, protectops cannot be kicked from the channel, unless the kick is from the channel owner. SOPs can also modify the akick list (/msg ChanServ HELP AKICK).

Important: Every level can add or delete people to levels below them, so a SOP can add VOP, HOP and AOPs, while a HOP can only add VOPs. The founder can change all levels.


ACCESS

The numerical level system, or ACCESS, gives more flexibility to the access list.

Each user is assigned a number (from 1 to 9999) and has dominance over another user with a lower number with complete disregard for the XOP level.

If you'd like to get rid of the XOP system in your channel altogether and change to the ACCESS system, all you must do is enter:

/msg ChanServ SET #channel ACCESSTYPE ACCESS

Adding user to ACCESS

To add a user to the access list: /msg ChanServ ACCESS #channel ADD nick level

Default Levels

voice = 3 (+)

halfop = 4 (%)

op = 5-9 (@)

protect / s(uper)op / admin = 10-9999 (&)

Changing Level Meaning

The powerful thing about the ACCESS system is that you can change what number is required to use a specific feature.

To view a list of features: /msg ChanServ HELP LEVELS DESC

To view the current levels list: /msg ChanServ LEVELS #channel LIST

Changing required access level for a feature: /msg ChanServ LEVELS #channel SET feature level

Disabling a feature (so only the founder can use it): /msg ChanServ LEVELS #channel DISABLE type

Resetting default levels: /msg ChanServ LEVELS #channel RESET

Give auto-voice to all users joining the channel (XOP must be disabled for this to work) : /msg ChanServ LEVELS #channel SET AUTOVOICE 0


FLAGS

This is the most powerful of all the systems, but also the most complex.

See FLAGS.

BotServ

When you own a channel, you are able to bring in a Rizon-provided bot.

Start by looking through the botlist for any specific bot you want assigned: /msg BotServ BOTLIST

Once you find one that you like, assign it with: /msg BotServ ASSIGN #channel bot

Wrapping Up

There are many other channel modes you can set, feel free to take a look at Channel Modes.

There are all sorts of neat and useful things that can be done with ChanServ. To learn more, type

/msg ChanServ HELP

which covers everything in this document and more.

Regarding the addition of Trivia/Quotes/LimitServ/Stats in your channel, take a look at Rizon Games.

Regarding the addition of Syntax in your channel, take a look at Syntax.


Channel Management 102

For further reading on Channel Management, please read Channel Management 102