Channel Management 101

From Rizon Wiki
Jump to: navigation, search

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 xOPs

VOP HOP AOP SOP
/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).

/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.

/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.

/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 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 specific 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/eRepublik in your channel, /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