Video Tutorial: Creating a Channel for Your Community

WyldRyde makes it dead-simple for your to create a chat-room for your community or group.  This step-by-step guide will show you how to go about registering a channel, adding a BotServ bot to it, and giving selected users voice and operator status.

What is required to register a channel?

In order to register your channel, you will need a registered nick on WyldRyde.  In short, the command to register your nick is “/ns register password email”, and you would replace “password” and “email” with your desired password and email address, respectively.  For a more in-depth guide to registering your nick, please reference my previous tutorial.

How do I go about registering a channel?

Once you are connected, registered, and identified, registering a channel is a simple two-step process.  First, you will want to use the /join command (“/join”  followed by a space and your desired channel name) to join the channel you with to register.  Remember that all channel names are prefixed with the pound sign (“#”), so your channel name should be in the form of “#ChannelName”.

Upon joining your channel, you should be the channel operator.  In clients such as mIRC and Textual, your channel operator status will be represented with the “@” symbol.  Other client such as XChat represent channel operator status with a green emblem.  Once you have assured that you have operator status, you can go about registering the channel with ChanServ.

The actual ChanServ registration process is rather straight-forward.  The command that you will want to enter is:

/cs register #channel password description

For the “#channel” variable, you will want to use the name of the channel that you joined and hold channel operator status in.  The “password” variable is simply a secure password as chosen by you.  This password can later be shared with a designated channel co-owner in order to allow another user to have the same level of channel access that is typically limited to the person who registered the channel.  Lastly, “description” needs to be replaced with a simple description (spaces allowed of the channel).  Below is a sample registration command:

Once you have submitted the command, ChanServ should send you a notice stating that the channel has been successfully registered to your name.  Additionally, ChanServ will apply mode “+r” to the channel to signify that it has been registered and  will give you mode “+q” in the channel to identify you as the channel’s owner.

Note: Even though you are the owner of a channel, you will not have the “~” or “&” symbols that are sometimes uses by other networks to symbolize a user’s owner or admin status in a channel.  WyldRyde uses the “@” symbol for all channel owners (+q), admins (+a), and operators (+o).  Despite the fact that you do not have the “~” or “&” symbols you are still the channel owner because you have the “+q” mode.

How do I add a services bot to my channel?

Adding a services bot allows you to use the commands available for BotServ in order to maintain your channel in a more simplistic fashion.

To add a bot to your channel, you will first need to select a bot name from the list of available bots (114 available as of the time of writing).  This list can be seen by typing “/bs botlist” in the text area within your client.

Once you enter this command, you should receive a list of bot names.  This list will have not only the names of the bots, but their idents and virtual hosts as well.  The list will be similar to the one shown below:

After you have selected a name from the list, assigning the bot is as simple as entering the following command:

/bs assign #channel bot

Be sure to replace “#channel” with the channel you wish to assign the bot to (it must be a channel that you own) and “bot” with the name you selected from the list.

Note: If you are interested in getting a custom bot name, please join the #help channel (“/join #help”) and ask to speak with a Services or Network Administrator about acquiring one.

Upon sending this command, you should receive confirmation from BotServ that the bot was successfully assigned.  Additionally, you will know that you executed the command correctly when you see that the bot you requested as joined your channel.

One thing that I typically do is enable “fantasy” commands within BotServ.  This allows your channel ops to take advantage of in-channel command such as “!kick” in order to simplify the channel maintenance experience.  To enable this, use the command “/bs set #channel fantasy on”, ensuring that you replace “#channel” with the name of your channel.

How do I assign access levels to other users?

One of the great things about ChanServ is that it allows you to give registered users access levels within the channel, and allows for these access levels to be associated with the user’s identity.  This means that you do not have to worry about re-voicing or re-oping a user whenever he or she enters your channel, as you can have services do it automatically.

The basic command for assigning an access level to a user is: “/cs LVL #channel add nick”.  In this command, you must replace “#channel” with your channel name and “nick” with the user who you are assigning an access level to.  Additionally, you must replace “LVL” with a three-digit code from below to tell ChanServ exactly what level of access that you want said user to have.  The following table shows the three-digit code, the modes that it will give the user, and an idea of what the user will be able to do with the given level of access.

Code Modes Description
VOP +v Voice: This will allow the user to speak in the channel when it is moderated (+m).
HOP +h Half-Operator: This will allow the user to “moderate” the channel. Some of the things a half-operator can do include voicing and de-voicing users, kicking users, and adding and removing bans. This access level allows you to allow a trusted user to moderate a channel without giving them too much power or control.
AOP +o Channel Operator: This mode will allow a user to do everything that a half-operator can (voicing, kicks, bans) in addition to setting more “advanced” modes such as flood control language filters, etc. An operator is able to give and take voice, half-operator, and operator status from users in the channel.
SOP +ao Channel Administrator (Super Operator): This access level is the highest that a user can obtain without becoming co-owner of a channel. A channel admin has all of the abilities as a channel operator in adition to the ability to kick/ban channel operators and the ability to manipulate certain parts of the ChanServ access list.

Once you submit the command, you will receive confirmation from ChanServ that everything went through successfully.

If you wish to give someone co-owner status in your channel, you must give them the password that you set during the channel registration process.  Then, they will need to use the command “/cs identify #channel password”, replacing “#channel” with the channel name and “password” with the password you set.

Note, however, that you should only give the founder’s password to people that you really trust, as a co-owner has full control over the channel’s settings and can even go as far as removing your owner status, regardless of the fact that you originally created the channel.

What if I have more questions?

As always, you are encouraged to join the #help channel (“/join #help”, or visit using the web-chat) if you have any questions.  A staff member or helper will be more than willing to help!

Filed Under: FAQHow To

Tags: , , , , , , ,

  • Pingback: WyldRyde IRC Network - How To: Block and Censor Words In Your Channel

  • gego zone

    heeelp me 
    when i enter:
    /cs register #mychannel password discription
    it’s show:
    Sorry, channel registration must be authorised by a -ChanServ- network staff member. Please join the networks’ support -ChanServ- channel to have your channel registered. -ChanServ- More information can be found using: /MOTD
    help me
    thnx

  • http://www.besttechie.net besttechie

    We disabled channel registration, please read this post for more info: http://www.wyldryde.org/2011/11/future-of-wyldryde/