Difference between revisions of "Channel Management 101"

Latest revision as of 02:43, 29 September 2021

Ownermode and Protectmode

If you want owner (~), enable ownermode: /msg ChanServ SET #channel OWNERMODE ON
If you want protect/admin (&), enable protectmode: /msg ChanServ SET #channel PROTECTMODE ON

After those commands, rejoin the channel or say /msg ChanServ SYNC #channel

Managing Channel Access

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

By default, channels use xOP since it is the simplest, so the other two aren't relevant unless you want more control.

xOP

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

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

VOP corresponds to a voice: +
HOP corresponds to a halfop: %
AOP corresponds to an op: @
SOP corresponds to a protectop: &

Important: Every level can add or delete people to levels below them. (E.g., a SOP can add VOPs, HOPs and AOPs; a HOP can only add VOPs). The founder can change all levels.

Viewing xOPs

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

/msg ChanServ ACCESS #channel LIST

Adding and Removing xOPs

	VOP	HOP	AOP	SOP
Add xOP	`/msg ChanServ VOP #channel ADD nick`	`/msg ChanServ HOP #channel ADD nick`	`/msg ChanServ AOP #channel ADD nick`	`/msg ChanServ SOP #channel ADD nick`
Remove xOP	`/msg ChanServ VOP #channel DEL nick`	`/msg ChanServ HOP #channel DEL nick`	`/msg ChanServ AOP #channel DEL nick`	`/msg ChanServ SOP #channel DEL 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`).	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.	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.	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 a channel owner (`~`). SOPs can also modify the AKICK list (`/msg ChanServ HELP AKICK`).

ACCESS

The numerical level system, ACCESS, gives you more flexibility.

Each user is assigned a number (from 1 to 9999) and has dominance over users with a lower numbers. You then can specify what each number has the power to do; e.g., level 3 and up can KICK.

If you want to auto-voice everyone who joins the channel, you must use ACCESS.

FLAGS

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

Each user is assigned a list of flags which allow them to do specific things in the channel; e.g., use KICK, use TOPIC, … etc.

BotServ

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

A BotServ bot allows you to use ChanServ commands by talking in the channel, like saying .kick Joe would be the same as /msg ChanServ KICK #channel Joe

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

For information regarding the addition of Trivia, Quotes, LimitServ, Internets, e-Sim, or eRepublik bots in your channel, read about the available FunServ bots and their features, or /msg FunServ HELP which covers everything in this document and more.

Channel Management 102

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

@@ Line 1: / Line 1: @@
-==Starting off...==
+==Ownermode and Protectmode==
-So you managed to register a channel, but didn't get the results you were expecting?
+* If you want owner (<code>~</code>), enable ownermode: <code>/msg ChanServ SET <em>#channel</em> OWNERMODE ON</code>
-* Where's my <code>~</code> mark?
+* If you want protect/admin (<code>&</code>), enable protectmode: <code>/msg ChanServ SET <em>#channel</em> PROTECTMODE ON</code>
-* 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!
-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.
+After those commands, rejoin the channel or say <code>/msg ChanServ SYNC <em>#channel</em></code>
+==Managing Channel Access==
-===Ownermode and Protectmode===
-* If you want <code>~</code>, enable ownermode: <code>/msg ChanServ SET <em>#channel</em> OWNERMODE ON</code>
-* If you want <code>&</code>, enable protectmode: <code>/msg ChanServ SET <em>#channel</em> PROTECTMODE ON</code>
-==Managing Access==
 There are three different types of systems to manage who has access on your channel:
-* '''XOP'''
+* [[xOP|XOP]]
-* ACCESS
+* [[ACCESS]]
-* FLAGS
+* [[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 <code>+</code>
+'''By default, channels use xOP since it is the simplest''', so the other two aren't relevant unless you want more control.
-* HOP corresponds to a <code>%</code>
-* AOP corresponds to a <code>@</code>
-* SOP corresponds to a <code>&</code>
-The XOP system only sets 4 fixed levels and makes for simple channel management. For more advanced channel management, see [[#ACCESS|ACECSS]] below.
-====Viewing the XOP list====
+===xOP===
-To look through the XOP list to see which user has what level, type:
-<code>/msg ChanServ ACCESS <em>#channel</em> LIST</code>
+The xOP system is the default form of access on Rizon.
-====Adding a VOP====
+Each user is assigned a certain level, which automatically grants them a status on the channel:
-<code>/msg ChanServ VOP <em>#channel</em> ADD <em>nick</em></code>
+* VOP corresponds to a voice: <code>+</code>
+* HOP corresponds to a halfop: <code>%</code>
+* AOP corresponds to an op: <code>@</code>
+* SOP corresponds to a protectop: <code>&</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>).
+'' '''Important''': Every level can add or delete people to levels below them. (E.g., a SOP can add VOPs, HOPs and AOPs; a HOP can only add VOPs). The founder can change all levels.''
-====Adding a HOP====
+====Viewing xOPs====
+To look through the xOP list to see which user has what level, type:
-<code>/msg ChanServ HOP <em>#channel</em> ADD <em>nick</em></code>
+:<code>/msg ChanServ ACCESS <em>#channel</em> LIST</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.
+====Adding and Removing xOPs====
-====Adding a AOP====
+{| class="wikitable" style="border: none; background: none;"
+|- valign="top"
+| style="border: none; background: none;"|
+! width="24%" | VOP
+! width="24%" | HOP
+! width="24%" | AOP
+! width="24%" | SOP
+|- valign="top"
+! Add xOP
+| <code>/msg ChanServ VOP <em>#channel</em> {{xt|ADD}} <em>nick</em></code>
+|<code>/msg ChanServ HOP <em>#channel</em> {{xt|ADD}} <em>nick</em></code>
+|<code>/msg ChanServ AOP <em>#channel</em> {{xt|ADD}} <em>nick</em></code>
+|<code>/msg ChanServ SOP <em>#channel</em> {{xt|ADD}} <em>nick</em></code>
+|- valign="top"
+! Remove xOP
+| <code>/msg ChanServ VOP <em>#channel</em> {{!xt|DEL}} <em>nick</em></code>
+|<code>/msg ChanServ HOP <em>#channel</em> {{!xt|DEL}} <em>nick</em></code>
+|<code>/msg ChanServ AOP <em>#channel</em> {{!xt|DEL}} <em>nick</em></code>
+|<code>/msg ChanServ SOP <em>#channel</em> {{!xt|DEL}} <em>nick</em></code>
+|- valign="top"
+| style="border: none; background: none;"|
+|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>).
-<code>/msg ChanServ AOP <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 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.
-====To add a user as a SOP====
+|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.
-<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.
-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.''
+Additionally, protectops cannot be kicked from the channel, unless the kick is from a channel owner (<code>~</code>). SOPs can also modify the AKICK list (<code>/msg ChanServ HELP AKICK</code>).
+|}
 ===ACCESS===
-The numerical level system, or ACCESS, gives more flexibility to the access list.
+The numerical level system, [[ACCESS]], gives you more flexibility.
-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.
+Each user is assigned a number (from 1 to 9999) and has dominance over users with a lower numbers. You then can specify what each number has the power to do; e.g., level 3 and up can KICK.
-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 want to auto-voice everyone who joins the channel, you must use ACCESS.
-<code>/msg ChanServ SET <em>#channel</em> ACCESSTYPE ACCESS</code>
+===FLAGS===
-====Adding user to ACCESS====
-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=====
+[[FLAGS]] is the most powerful of all the systems, but also the most complex.
-voice = 3 (+)
+Each user is assigned a list of flags which allow them to do specific things in the channel; e.g., use KICK, use TOPIC, … etc.
-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: <code>/msg ChanServ HELP LEVELS DESC</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 <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 <em>#channel</em> DISABLE <em>type</em></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 <em>#channel</em> SET AUTOVOICE 0</code>
-===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.
+A [[Services_Commands#BotServ_Commands|BotServ]] bot allows you to use [[Services_Commands#ChanServ_Commands|ChanServ commands]] by talking in the channel, like saying <code>.kick {{xt|Joe}}</code> would be the same as <code>/msg ChanServ KICK <em>#channel</em> {{xt|Joe}}</code>
 Start by looking through the botlist for any specific bot you want assigned: <code>/msg BotServ BOTLIST</code>
@@ Line 130: / Line 95: @@
 ==Wrapping Up==
-There are many other channel modes you can set, feel free to take a look at [[Channel Modes]].
+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
-<code>/msg ChanServ HELP</code>
-which covers everything in this document and more.
+There are all sorts of neat and useful things that can be done with ChanServ. To learn more, type:
-Regarding the addition of Trivia/Quotes/LimitServ/Stats in your channel, take a look at [[Rizon Games]].
+:<code>/msg ChanServ HELP</code>
-Regarding the addition of Syntax in your channel, take a look at [[Syntax]].
+For information regarding the addition of Trivia, Quotes, LimitServ, Internets, e-Sim, or eRepublik bots in your channel, read about the available [[Services_Commands#FunServ_Commands|FunServ bots and their features]], or <code>/msg FunServ HELP</code> which covers everything in this document and more.