Welcome to Fel's guide to IRC! This is the ChanServ section of our tutorial. In this guide you will find everything you need to take ChanServ, the channel service bot for NewNet, and wrap him around your pretty little finger.

Also available for your pleasure are tutorial documents for NickServ, MemoServ, and Channels and Channel Op Status. You can get copies of these documents from the channels #NewNetHelp and #Services on NewNet, and from Fel himself.

This tutorial is written for people who don't have alot of experience dealing with ChanServ. The commands are explained to you in some detail. The explanations will tell you WHY you are doing what you're doing, WHAT the command is, and HOW ChanServ uses it to do what you want it to do. I learned long ago that if you understand the WHY of something, it is much easier to remember than just a stupid string of commands.

Because I'm a very linear person, I'm assuming that you've either read the NickServ tutorial, or you have a passing familiarity with our glorious nickname bot. You're going to see a few references to him in the tutorial below. But don't worry. Even if you have no idea who NickServ is, you'll be able to follow what I'm talking about.

So, let us begin!

ChanServ is probably the most complex service bot we employ here on NewNet. ChanServ is the channel service bot. His job is to keep track of who owns a channel, who's allowed in that channel, who gets ops in that channel, and many, many other things. And he does it for every single registered channel. ChanServ is a very busy bot, but he does his job with a quiet efficiency that's really pretty remarkable, considering the fact that he's not much smarter than NickServ. Chanserv is like your channel big brother and watchdog, all rolled in to one (hey, some of us who have brothers who look like dogs, so this may not be a big thing). He watches over the channel, kicking out anyone you tell him isn't welcome. He'll greet people who enter the channel, tell them about the channel's web page, and even give channel ops or voice to your channel friends and compatriots. He can even take ops away from people who used chicanery or a dirty trick to try to get ops in your channel, and you can tell him not to EVER let some REALLY big jerk have ops, that came in last week and was a total grease baby. He does alot of other things too...he knows alot of tricks, and if you know about them, you can make them work for you. You can even make him dress in drag and do the hula, if you've got skill. ;)

Chanserv likes a set format, one that is very similar to NickServ's (if you're familiar with NickServ. If you aren't, fear not, I'll show you this format later on). But one thing extra you should know is that any time you use ChanServ, you have to tell him what channel your command is going to be used for. He doesn't know this, even if you're only on that channel. And a # is the beginning of every channel name. You have to include it in the channel name, or ChanServ will laugh at you. Below, you'll see the term <your channel> in the command descriptions. When you see this, just use the name of your channel there, without the brackets ---> < > , and with the # at the beginning. Such as #I_Rule or #chatfriends, for example.

I want a channel!

No problem. Chanserv is pretty easy going, but he does have a couple of requirements you have to meet before he'll register your very own channel.

The first is that the channel you want to register isn't already registered. If you see ChanServ in a channel, it's registered. He doesn't hang out in channels that aren't registered, because he can't see them.

The second is that you have channel ops in the channel you want to register. This means that you have the @ beside your nick on the channel's name list.

The third, and most important, is that you already have to have your nickname registered through NickServ. ChanServ won't talk to strangers, and you're a stranger if your nick isn't registered.

If everything looks cool, then you're ready to give it a shot. The first thing you need is a password. Just like NickServ, the password has to be at least 5 characters long, but no more than 10, and it can have letters, numbers, and capital letters in it. It also can't have any spaces in it anywhere. I suggest at least a 6 character password, with all three types of characters; numbers, capital letters, and lower case letters.

Make sure you write it down!!!!!

Another thing you'll need is a channel description. It's just a short little bit of info that describes the channel. Although it's not vital, you do need to have on in your register command, else ChanServ will have a tizzy and make you do it again.

The command to register a channel is alot like the command you use to register your nickname. It just needs a bit more information in there...cause ChanServ is a bit more sophisticated than NickServ:

/msg chanserv register <your channel name> <your password> <a very short description of the channel>

One other thing you'll see him do is set the channel modes to +nt. I'll explain exactly what that is in a bit, but don't worry. He did that for a reason, and it was supposed to happen.

There will be times when you'll want to make changes to your channel. Most of the time, ChanServ is going to want some proof that you have the right to do that. Just like NickServ, any time you want to make changes, you'll need to identify yourself to ChanServ as the channel's owner, with your password. The command is almost exactly like NickServ's, all you need extra is to tell ChanServ which channel you're claiming is yours:

/msg chanserv identify <your channel> <your password>

The channel's Access list is something like your access list for Nickserv. What you're doing is giving ChanServ a list of people that it should recognize when they enter the channel. What he does for, or to, those people depends on what LEVEL you set for them on the list. Some levels give that person ops. Some levels give a channel op more powers than other channel ops. One setting actually tells ChanServ not to let that little creep have ops in your channel, EVER.

Your Access List: what all those little ! and @ and whatnots mean

ChanServ is DUMB. Keep that in mind. When you add to your access list, you're going to be adding people by a very specific format, and you'll be giving ChanServ a good deal of information about yourself. It's important that you keep that format straight, else ChanServ is only going to give you dumb looks. Let's see about how this works.

There are two ways to add to your channel access list. By the hostmask, or by a nick. When you add by nick, you just use the nick of the person you want to add....BUT, that person needs to be registered with NickServ, else ChanServ won't have the slightest idea who it is.

So, an access add by nick would just have that nick in there. That's all. I'll show the exact way you use this command in a bit.

NOTE:  If you already know what a hostmask is, you may want to skip down to the next section. What we have here is an introduction to the hostmask. Since you had to register your nick to work with ChanServ, you should already have a good idea of hostmasks.

A hostmask is kinda like an address. It's where you're connecting to the internet from. Usually, this is your Service Provider. You'll notice, if you look at your hostmask, that your provider's name is probably in it somewhere. This is the one thing that you really can't change about yourself. Oh, a number or two inside it will change, but the majority of it is going to stay the same. That is why NickServ recognizes people by their hostmask.

There are two types of hostmasks. There are the name masks, and then there are the number masks. This is a name mask, for example. This is my own:

fel@ppp12.gatormail.com

The other type of mask is called an IP mask. It looks like this:

fel@206.104.52.12

Some providers don't give out their names, and when a server can't find it out, it gives that person an IP hostmask. This number represents the numerical address of my service provider. To let you know, both of these masks are exactly the same. They are both me. One is just the NAME of the provider, sometimes called a DOMAIN, and the other is the mail-style adress you would use to talk to it.

The reason we're talking about these masks is because this is how ChanServ sees you. When you registered your name, it told you that you registered under an account. Well, that account would have looked one of two ways:

<your user name>@*<the domain name of your provider>

fel@*.gatormail.com

<your user name>@208.16.39.*

Can you say "DUH!"? I hope so, cause NickServ is DUMB. Remember that, and you'll do fine.

Now that you have an idea of what a hostmask is, let's see how ChanServ uses this.

A Hostmask is a little different for ChanServ than it was for NickServ. NickServ ALREADY knew what nick you were talking about, so you didn't have to tell him about that. ChanServ, however, doesn't have this advantage...so you have to add another piece to your hostmask in order to make ChanServ understand who you're talking about.

With Nickserv, you used a username@hostname format. Well, you'll be using that again, just with a nickname part stuck in the front. Just as the @ separates the username from the hostname, you're going to need a symbol to tell ChanServ where the nick ends, and the username begins. For ChanServ, we use an exclamation point: !

So a Chanserv access add by hostmask will look like this:

nick!username@hostname

Fel!fel@*.gatormail.com

*!fel@*.gatormail.com

Alright, now that you know exactly how the hostmasks and access adds work, let's add one. But to do that, first you need to understand the ACCESS LEVELS that exist in the channel. These are numbers that represent your rank in the channel, more or less. The levels go from -9999 all the way to 9999. 9999 is the highest access level, and as the founder and owner of the channel, this should be the access level that you give to yourself. You ARE the top dog, after all. ;)

There are a few other level types you should understand. I'll list them below:

any number less than 0: This guy NEVER gets ops in the channel. ChanServ will let him come in, but he doesn't ever get ops.

0: A regular user. These guys have no extra privilges.

1-4: These levels only matter if you have the SECUREOPS mode turned on (look below, and you'll see what that is). When SECUREOPS are on, ChanServ will allow people with these levels to be opped.

5-9: These levels are what you'd call the basic channel op. ChanServ ops them when they come in, but that's it. They can only do what any channel op can do. The specific things they can do is kick people off the channel, ban them off the channel, set it so other people are channel ops or voiced temporarily, and ask Chanserv to invite them into the channel when the channel is set to invite-only (see below to see what this is).

10-1000: alright, now we're getting into the power. These guys have three extra powers over normal ops. First, they can make changes to the access list themselves. But they can't add, remove, or change anything that's an access level that's higher than their own, so don't worry about a level 10 coming in behind you and taking out your 9999. He just doesn't have the pull, and ChanServ will laugh at him for trying. Another thing that they can do is make changes to a channel's AKICK list. (see below to find out what this is). The last thing they can do is ask ChanServ to op them if they're not opped, using this command:

/msg chanserv op <the channel name>

1001-9999: These are the BIG guys in the channel. They have all the abilities as a 10+ person, plus they have the power to ask ChanServ to part and rejoin a channel, using this command:

/msg chanserv <either part or join> <the channel's name>

What parting or joining does for ChanServ is kinda obscure. I'll explain why this is handy a bit later.

Now that you understand what all the parts of the access command mean, we'll try one. Do a /whois on yourself and check out your hostmask. Make the little changes you need tomake to wildcard out those changing numbers. Then set things up so that they fit into the ChanServ style of hostmasks, with the nickname in the front with a ! after it. Once you have that ready, then type this command:

/msg chanserv access <your channel> add <your nick!user@host mask> <your access level--9999>

If I registered the channel #blah, and wanted to add myself to the access list so ChanServ recognized me no matter what nickname I use, I would do it this way:

/msg chanserv access #blah add *!fel@*.gatormail.com 9999

/msg chanserv access #blah add Fel 9999

Now that you have something in your access list, you may want to take a look at it and make sure you have it the way you want. Type this command to take a look at it:

/msg chanserv access <your channel> list

If someone's being a major jerk, you may want to take them off your access list. The way to do this is rather simple.

First, make a list of the access list, and see which listing is the one that you want to remove. The listings will have numbers just in front of the added masks, numbering them off. Find that number, then type this command:

/msg chanserv access <your channel> del <that access list number>

/msg chanserv access <your channel> del <that access hostmask>

Just make sure you type it in EXACTLY the same way it appears. If you don't, ChanServ will think you've lost a couple of marbles, and ignore you.

Channel Modes are, well, modes that you can turn on and off in a channel. There are several of them, and each of them does a specific thing, in order to help you make your channel the way you want it. The easiest way to explain them is, well, to explain them.

The Modes

There are 8 channel modes that you can turn on and off, and each one does a different thing. Below is a listing of them, their letter representation, and what they do. It's a general understanding that if a mode is +, it is on, and if a mode is -, it is off. When you registered your channel, ChanServ set the modes +nt. In other words, it turned on modes n and t. Those modes, and the others, are listed below.

A note: channel modes are not a function of ChanServ. They're an integral part of the network, and it is to the network that you're giving these commands to. When you tell ChanServ to turn on or off a mode, Chanserv does this job for you, telling the network what modes belong on that channel.

n -- this mode tells the network not to allow anyone to send messages to the channel unless they're ON that channel.

t -- this mode allows ONLY a channel operator to change the channel's topic.

i -- this mode is called INVITE. What it does is restricts people from joining the channel. When Invite is turned on, only channel ops and people who are invited into a channel may join it. The command to invite someone to a channel is:

/invite <that nick> <your channel>

p -- This is Private Channel Mode. It's a kinda obscure channel mode, because you can't really see what it does. But what it does is this: your channel won't show up on a /list command used by people to see what channels are here.

s -- This is Private's big brother, Secret. It does everything Private does, PLUS it hides your channel's name from anyone who does a /whois on you, for a /whois shows someone what channels you are on at that moment. You can't have both s and p on at the same time. It has to be one or the other.

l -- this is Limit. When you use this mode, and tell it what the limit is, it will ONLY allow that many people on the channel. If the channel reaches the limit, nobody else can join it until someone else leaves.

m -- this is Moderated mode, and is probably the least used available mode. What it does is Moderates the channel. When a channel is moderated, only channel ops and people given Voice (the + by their nicks) can send messages to the channel. That's all it does.
By the way, that is ALL that voice does, and all it was ever meant to do. Many people use voice as a special symbol, a symbol that the user is a friend of the channel.

k -- Ah, the Mother of all modes. This is Key mode, and it tends to cause the most problems. What this does is fixes it so you have to type a password, a key, in order to get into a channel. This is NOT the channel's ChanServ password!!!!!!! You get into a channel set with a key by typing /join . Usually, the key appears at the top of the screen, near the topic, visible to everyone who is on the channel. Just to let you know, you can make it invisible, if you want, with the ChanServ SECURE feature. I'll explain this a bit later.

Chanserv can set things so a channel mode is always on, or it is always off, or it leaves it up to you. The way you use the command tells it how to set things up.

Telling ChanServ to set a channel mode on, what it calls MLOCK, is to tell it to go +that mode. To turn it off, you go -that mode. You can use both in the mlock command at the same time, shown below.

The command is as follows:

/msg chanserv set <your channel> mlock <how you want it set>

/msg chanserv set #blah mlock +nt-klim

In this example, modes n and t are turned on all the time, and ChanServ won't allow modes k, l, i, or m to be turned on. The modes not mentioned here, s and p, those can be turned on or off by the channel ops as they see fit. Not having Chanserv turn them on or off is the same as leaving it up to the ops in the channel.

How DID he get ops in your channel? Well, there are a couple of ways. Some are simple, some aren't.

One way is that he joined the channel when it was empty. The first person in a channel always gets ops. If you don't have SECUREOPS turned on, when Chanserv joins the channel itself (it always does this; it doesn't sit in empty registered channels until someone else joins it first), it won't do anything about the intruder.

Another way he got ops was that maybe someone else opped him. You'll find that alot of people ask for ops in channels. Use your good judgement on who to give this privilege to.

The involved way is that, perhaps he fooled ChanServ into thinking he was SUPPOSED to be opped in that channel. It can be done, but it isn't easy. ChanServ is a busy bot, and every once in a while, something sneaks through.

What is a channel takeover? Well, it's when some real jerk comes in, manages to get ops, and then deops or kicks out everyone else. But don't worry, as the founder of your channel you have all the tools you need to deal with this guy. Prepare to kick his butt!

Getting him out of your channel

You have a very, very powerful tool to really kick that guy in the--well, some place that's really going to hurt. ChanServ has a command there at your fingertips to deal with just such an emergency. It's called the CLEAR command, and it will get that lame grease baby good.

Before you can use the CLEAR command, however, you have to identify to ChanServ as the founder.

Once you do this, you're ready to clear the channel. There are several ways to do this. All of them use the same basic command:

/msg chanserv clear <your channel> <what you want cleared>

ChanServ can clear the ops, which deops everyone. It can clear all bans set by people, which lets you get back into the channel. It can clear all channel modes, which will turn off all modes except those that ChanServ keeps MLOCKed on. It can clear all voices, removing the + from everyone. It can even totally clear the channel, kicking EVERYONE out.

These are the command you would use:

/msg chanserv clear <your channel> <what you want it to clear>

OPS: deops everyone
BANS: removes all the bans set in the channel
MODES: resets the channel modes
VOICES: everyone with a + loses it
USERS: sweeps the channel clean! ChanServ kicks EVERYONE!

/msg chanserv unban <the channel>

If some guy just decides that his mission in life is to aggravate you, and he somehow manages to get in and take over your channel more than once, then you need some heavy duty help. That's an IRCop's job. An IRCop will help you smite these irritating repeat offenders, and will help you get him out of your channel for good.

When someone is a major pain in the rear,and you want them out of your channel for good, well, you have just such a tool available. It's call the AKICK (Auto-KICK) list, and what it is is a list of people you give to ChanServ. When ChanServ sees one of those people join your channel, he picks up the nearest available weapon and thrashes that person senseless. Actually, what he really does is instantly bans that person, and then kicks them off the channel. The kick message will be what you tell him to say to that person when he gives him the steel-toed boot.

The big thing you need to know about the Akick list is that you enter things almost exactly the same as you do for the channel's access list. The only thing you'll be doing differently is replacing the access level with a kick message. And using a different command, of course. Everything else is almost exactly the same. If you can manage an access list, then you'll have no problem at all working with your Akick list.

Say you have someone that you decide is just too much aggravation, and you want him akicked. Well, the first thing you'll need to do is find out who that person is. /whois him and get his user hostmask ready, by putting those wildcards into those places where the numbers are that change. Once you've settled on the way you want to add in the mask, think up a kick message, like "how do you manage to survive with only one brain cell?" or something suitable. :)

Remember that since you're dealing with ChanServ here, you have to use the large type of hostmask, with the nick, user name, and hostmask. Just so: nick!user@hostmask. Just like the channel access list.

Now you're ready to add it. Type this command:

/msg chanserv akick <your channel> add <the hostmask> <the kick message>

/msg chanserv akick #chatworld add *!fel@*.gatormail.com you are such a LOSER!!!

/msg chanserv akick <your channel> list

/msg chanserv akick <your channel> del <that person's entry>

A channel topic is a rather important thing. It tells people all about your channel. And, unfortunately, it often becomes a playtoy for a channel op. If you don't want people messing with your topic, then ChanServ has just the set of commands for you.

There are two things you can do to your topic to make it secure. One, you can set it so it CAN be changed, but ChanServ will always change it back to what you tell it to any time he leaves the channel and comes back. The other thing you can do is fix it so ChanServ won't let ANYONE change the topic without using a special command. And only you and people you allow will have access to that command.

Either way you go, you have to tell ChanServ what that topic is going to be. You need a command to do that, and this is what it is:

/msg chanserv set <your channel> topic <the topic>

If you just want ChanServ to set the topic to the topic when he comes in, use this command:

/msg chanserv set <your channel> keeptopic <either on or off, as you want>

/msg chanserv set <your channel> topiclock <either on or off>

There's a special mode you can have ChanServ run in. It's called Secure mode, and it is the ultimate in channel security.

What it does is simple. Anyone on your channel access list has to identify to NickServ as the owner of the nick before ChanServ will let them do ANYTHING. He won't op or voice people on your access list until NickServ assures him that they're really who they seem to be.

The down side of this mode is that, if you have it turned on, ONLY people who have registered nicknames can be on your access list, and you can add to the access list ONLY by nickname.

/msg chanserv set <your channel> secure <either on or off, as you see fit>

If you want a new password, no problem. It's easy to do. Just keep in mind that you have to have the old one before you can tell ChanServ the new one.

First, identify as the channel's owner. Once ChanServ bows to your might, use this command:

/msg chanserv set <your channel> password <your new password>

Chanserv will send you a message with your new password, letting you see what it thinks is the new password. And that's that.

MAKE SURE YOU WRITE YOUR PASSWORD DOWN!!!!!

ChanServ has quite a few little perk things set up for it, to help you customize your channel exactly the way that you want it. He can do quite a bit for you. Below, I've listed these additional commands, and how you use them.

The Channel URL
If you have a webpage, and this webpage is an official site of the channel, you can tell ChanServ what it is, and he'll add it to a listing any time someone asks him for information about your channel.

This is the command you will use:

/msg chanserv set <your channel> url <your webpage address>

There's no way to turn this off, so if you want to remove this, you need to type the command again, and put a single space in the place where you'd put the webpage address.

The Channel's Greeting
Remember that channel description you had to set with ChanServ when you registered the channel? Didn't seem like much of anything, did it?

Well, guess what? Here's where you can USE it. You can tell ChanServ to send a message to everyone who joins, and that message will be your channel description. It's called a channel greet.

This is the command you use to activate it:

/msg chanserv set <your channel> greet <either on or off, as you like>

If you don't like your channel description, that's easy enough to change. Just use this command:

/msg chanserv set <your channel> desc <the new description>

Say you're going on a extended trip to Oregon, or maybe you're just tired of your channel and a friend of yours wants it. Well, you can give it to him without messing up everything you have set in the channel. It's called changing founders. And once you do it, the other guy will be the new owner of the channel.

Make VERY sure you want to do this before you do it. When you change the founder of your channel, then you don't own it anymore. It'll be the other guy's, and you can get it back ONLY if he gives it to you.

If this really is what you want to do, first you have to keep in mind that ChanServ will demand that other guy meets the same requirement you did. He has to have his nickname registered with NickServ. If he does, this isn't a problem. If not, he'll have to do it before ChanServ will allow you to give him the channel.

Once everything's set up, this is the command you will use:

/msg chanserv set <your channel> founder <the nick of the new owner>

Say you want to get rid of the channel. It's gotten dull, or boring, or you just don't have time anymore. Well, you can tell ChanServ that you don't want it anymore, and he'll cancel your registration.

The command for this is is this:

/msg chanserv drop <your channel>

Why customize?

Why? Well, that's a very personal question..and there's no real set-in-stone answer. Some people will like the 0-5-10-1001 format which is the default just fine. But this is pretty generic, and it restricts channel ops from certain commands. For example, only the founder can use the various SET functions when you use the default setup. Say your best friend is your co-founder. The only way to give him or her the same access is to tell him or her the password...and, trust me, it is NEVER good to tell ANYONE your password. Even your best friend.

Customizing your levels lets you decide just who in your channel can have access to what commands. You can give a certain level as many or as few access privileges as you want.

I highly suggest you check out ChanServ's help on the levels command:

/msg chanserv help levels

Customizing: the neurotic's approach.

This may sound silly, but being neurotic when you set up your own access list is an advantage. The key here is ORGANIZATION! Decide how you want to do it before you start changing things around. I suggest getting a piece of paper and deciding what levels there will be, and what privileges an op will get at that level. Believe me, this will save you some headache when you start the customizing procedure.

Let's say that I've decided to customize my access list. I want the founder to have access to everything, and my co-founder to have the same access as me. I want four levels under that. The uppermost will have access to everything except the SET command. The next level below that will have access to the akick lists, and will also have access to the CLEAR and UNBAN commands. The level below that will have access to the INVITE command and OP feature through ChanServ. The last level will be a standard channel op, EXCEPT it will not have access to the INVITE command. I also want certain people to have voice when they join the channel.

Alright, from this list, I see 5 access levels. I'll assign them numbers that more or less coincide with the defaults, just to save myself some work. My Founder/Co-founder will be 9000. My Master Op will be a 1000. My Intermediate Op will be a 10, and my Basic Op will be a 5. Since I want a voice level added, I need to define a new access level. I'll make that a 3. Now, what that means is that these are the LOWEST levels you need to get that power. I could put someone in as a 1423, and he'll have all the powers of a 1000, but not a 9000.

That's the key of it. You assign a function to the LOWEST level you want to have that power, because everyone above it will automatically gain those powers.

Alright, I know who's going to get what. Now I have to start typing commands.

We'll do the 9000 first. He's already got all those powers in the default, except for the power to SET. I'll do that now.

/msg chanserv levels #mychannel set SET 9000

Next, I see, is the Master Op. He has one power over and above the other ops below him, and that's access to the access list. Let me change that level now, since that's a level default at 10.

/msg chanserv levels #mychan set ACCESS 1000

Next is my Intermediate Op. I want him to be a 10, and have access to the akick, clear, and unban options. Access was changed to 1000, and akick is already defined at level 10, so I only have to define CLEAR and UNBAN. Let's do that now.

/msg chanserv levels #mychan set CLEAR 10
/msg chanserv levels #mychan set UNBAN 10

Wait, I'm taking the INVITE option away from the level 5 op. I have to redefine that. Let's take care of it now.

/msg chanserv levels #mychan set INVITE 10

My basic op is unchanged, except for losing the INVITE privilege. So I don't have to make any changes for him.

I have a new level, one for voice. Time to add that in.

/msg chanserv levels #mychan set AUTOVOICE 3

/msg chanserv levels #mychan list

ChanServ: ChanServ: ChanServ: ChanServ: ChanServ: ChanServ: ChanServ: ChanServ: ChanServ: ChanServ: ChanServ:

AUTOOP AUTOVOICE AUTODEOP NOJOIN INVITE AKICK SET CLEAR UNBAN OPDEOP ACCESS

5 3 -1 -1 10 10 9000 10 10 5 1000

That's it. If you want to learn a great deal more about it, study the help available through ChanServ. Because that is exactly how I learned this.

And if I can learn it like that, then ANYONE can.

Unfortunately, things can go wrong. It IS real life, you know, and nothing's ever perfect.

The best thing to remember is not to panic when something is acting flaky. Just try again. If it's obvious that something is WRONG, like ChanServ decides that the password you've used for the last 2 months is suddenly wrong, then you're going to need a bit more help. This is where your friendly neighborhood IRCop comes into the picture. They've got some tricks up their sleeves to help you deal with these problems.

That's about all, so far as ChanServ goes. I'm certain that some of you will notice that I may have left a little thing out here and there. It may have been on purpose...or maybe it wasn't. But if you noticed it, then you can call yourself a grizzled NewNet veteran for having such a sharp eye.

Remember that any time you need help, and you can't find it or you don't know what to do, an IRCop will always be there for you.

Author:  Fel, IRCop on irc.intergate.bc.ca
Co-Author:  the late Phoenix, who was an IRCop on irc.klis.com
HTML Conversion by:  elek

Special thanks to Mooooooo, our universally adored Oper Cow, who was the technical advisor and general brain behind this text.