Difference between revisions of "User:Kizeren/irc"
m |
m |
||
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | <div style="background-color: #f2f7da; font-size: 100%; font-family: 'Verdana'; padding:10px; border: 1px solid #38440f;"> | ||
==IRC Setup== | ==IRC Setup== | ||
Line 9: | Line 10: | ||
Once you have control of the channel type the following | Once you have control of the channel type the following | ||
− | + | <pre> | |
− | /msg | + | /msg ChanServ REGISTER <channel> <password> |
− | + | </pre> | |
+ | So here is an example. | ||
+ | <pre> | ||
+ | /msg ChanServ REGISTER #test temp123 | ||
+ | </pre> | ||
+ | You will now have founder status of that channel. No one besides you will be able to make changes to this channel. | ||
+ | |||
+ | ===Step 2=== | ||
+ | Adding AOP. Normally you would want this only for the masters of your guild. | ||
+ | |||
+ | <pre> | ||
+ | /msg ChanServ AOP <channel> ADD <user> | ||
+ | </pre> | ||
+ | Should end up like this. | ||
+ | <pre> | ||
+ | /msg ChanServ AOP #test ADD kizeren | ||
+ | </pre> | ||
+ | You will want to do this for each master of your guild. | ||
+ | |||
+ | ===Step 3=== | ||
+ | Adding HOP. HOP has the same power as AOP but cannot kick AOP | ||
+ | HOP will have "%" symbol next to thier name. | ||
+ | <pre> | ||
+ | /msg ChanServ HOP <channel> ADD <user> | ||
+ | </pre> | ||
+ | Should end up like this. | ||
+ | <pre> | ||
+ | /msg ChanServ HOP #test ADD kizeren> | ||
+ | </pre> | ||
+ | |||
+ | ===Step 4=== | ||
+ | Adding VOP users. No really power for this one. I will explain further in the later part of this setup. | ||
+ | <pre> | ||
+ | /msg ChanServ VOP <channel> ADD <user> | ||
+ | </pre> | ||
+ | Should look like this. | ||
+ | <pre> | ||
+ | /msg ChanServ VOP #test ADD kizeren | ||
+ | </pre> | ||
+ | |||
+ | ===Step 5=== | ||
+ | Once all users are setup, we will lockdown the channel so no strangers can enter it. | ||
+ | <pre> | ||
+ | /msg ChanServ SET <channel> RESTRICTED on | ||
+ | </pre> | ||
+ | Should look like this. | ||
+ | <pre> | ||
+ | /msg ChanServ SET #test RESTRICTED on | ||
+ | </pre> | ||
+ | |||
+ | ===Step 6=== | ||
+ | This is optional. Will bring Grimnismal to channel. | ||
+ | Only the founder or AOP's can use this command. | ||
+ | <pre> | ||
+ | /msg BotServ ASSIGN <channel> Grimnismal | ||
+ | </pre> | ||
+ | Should look like this. | ||
+ | <pre> | ||
+ | /msg BotServ ASSIGN #test Grimnismal | ||
+ | </pre> | ||
+ | It will be Grimnismal kicking people. | ||
+ | |||
+ | ==Pros and Cons== | ||
+ | Just a list of things that could go wrong and things that are good. | ||
+ | |||
+ | ===Pros=== | ||
+ | Very simple to set up. Takes matter of minutes to do. | ||
+ | No one can sieze your channel. | ||
+ | You can quickly change users access levels. | ||
+ | |||
+ | ===Cons=== | ||
+ | Once someone is kicked they are permentaly banned from that channel. | ||
+ | Not easy to unban. | ||
+ | Don't lose your password. Cannot be retrieved without buggin the admin. | ||
+ | Don't share your password. That person can really screw up your channel. But they can't claim it. Pain to start over. | ||
+ | Anyone not in the AOP, HOP and VOP groups will be the ones kicked and permently banned. | ||
+ | ALWAYS add the new member before accepting him in to your guild. Other wise they might get banned. |
Latest revision as of 10:04, 22 October 2010
Contents
IRC Setup
In this entry I hope to further show how to setup a IRC the easiest way I can think of.
Step 1
The most important step. We will first need to register a channel. Enter the channel you wish to register. You must be AOP (have the @ symbol) Once you have control of the channel type the following
/msg ChanServ REGISTER <channel> <password>
So here is an example.
/msg ChanServ REGISTER #test temp123
You will now have founder status of that channel. No one besides you will be able to make changes to this channel.
Step 2
Adding AOP. Normally you would want this only for the masters of your guild.
/msg ChanServ AOP <channel> ADD <user>
Should end up like this.
/msg ChanServ AOP #test ADD kizeren
You will want to do this for each master of your guild.
Step 3
Adding HOP. HOP has the same power as AOP but cannot kick AOP HOP will have "%" symbol next to thier name.
/msg ChanServ HOP <channel> ADD <user>
Should end up like this.
/msg ChanServ HOP #test ADD kizeren>
Step 4
Adding VOP users. No really power for this one. I will explain further in the later part of this setup.
/msg ChanServ VOP <channel> ADD <user>
Should look like this.
/msg ChanServ VOP #test ADD kizeren
Step 5
Once all users are setup, we will lockdown the channel so no strangers can enter it.
/msg ChanServ SET <channel> RESTRICTED on
Should look like this.
/msg ChanServ SET #test RESTRICTED on
Step 6
This is optional. Will bring Grimnismal to channel. Only the founder or AOP's can use this command.
/msg BotServ ASSIGN <channel> Grimnismal
Should look like this.
/msg BotServ ASSIGN #test Grimnismal
It will be Grimnismal kicking people.
Pros and Cons
Just a list of things that could go wrong and things that are good.
Pros
Very simple to set up. Takes matter of minutes to do. No one can sieze your channel. You can quickly change users access levels.
Cons
Once someone is kicked they are permentaly banned from that channel. Not easy to unban. Don't lose your password. Cannot be retrieved without buggin the admin. Don't share your password. That person can really screw up your channel. But they can't claim it. Pain to start over. Anyone not in the AOP, HOP and VOP groups will be the ones kicked and permently banned.
ALWAYS add the new member before accepting him in to your guild. Other wise they might get banned.