| Irc Op Format | |
|---|---|
| Tweet Topic Started: Aug 19 2013, 03:05 AM (31 Views) | |
| SADFACE | Aug 19 2013, 03:05 AM Post #1 |
|
Administrator
|
1. What it means to be an IRCOp Being an IRCOp is a job, not a status symbol. You have been given this job so you can help the network and it's users. If you are only interested in being an oper so you look cool and can kill people who piss you off, then don't be the least bit surprised when you suddenly can't oper. It's a volunteer job. Looking cool is just a fringe benefit. ![]() While you are opered, you are expected to do several things: Be courteous to the network's patrons. Do everything in your power to keep the network running. Help those who ask for it. If you're not willing to do these at the time, you should not be opered. Set yourself -o until you feel ready to face the challenges and responsibilities of that mode. About the above listed: Be curteous to the network's patrons. What this means is you are expected to be friendly and helpful to the people that use this network. It's like any other job serving the public, if your a complete ass, you get fired. If you're busy when someone asks for help, tell them you're occupied and refer them to someone or somewhere where they can be helped. Do the same if you just don't know the answer to their question. Do everything in your power to keep the network running. This means assist in routing, dealing with clones, working in the help channels, etc.But doing so earns you respect in the eyes of your fellow opers and the network in general, and it is the path to things such as CSOp, SRA, and other positions of power above IRCOp. Help those who ask for it. Just because you don't have mode +h set doesn't mean your not required to help people. If someone sees you, an oper, with a low idle time and not set away, they're going to assume (rightfully so) that you are willing to help them. As stated above, if you're not willing to do this, deoper until you are. If someone asks a question you don't know the answer to, refer them to the proper help channels. You might also be well advised to join them there so that you too can learn the answer. General Rules 1. banning: There is to be NO banning for PERSONAL reasons. Bans can only be made for breaking the rules of the server or the network. Whenever possible, a log showing the offence should be kept on hand and distributed to the Admins and IRCops. Most bans for a first offence will be 24 hours or less. Bans over a 48 hour period may be appealed to the Admins. 3 step process for most bans: 1st offence, up to 24 hours; 2nd under one week; 3rd week or more; 4th permanent. Trolling results in an immediate permanent ban. Harassment can result in such a ban. 2. banning offences- this is a non-exclusive list (see also the rules page) * Harassment of other users. * Running excessive connections to the server (cloning) * Excessive flooding * Cybering in public channels. Cybering, if done at all, should be private. * Running unapproved bots, especially war bots. See an Admin for information. * Use of the defensive and offensive capabilities of War Scripts or bots. * Denial of service attacks (Spinging, nuking, etc.) IRCops are to use their best judgement for situations arising not covered by this list. If an Admin is available and time allows, the Admin can be consulted before taking action. 3. K:Lines Should preferably be set by a Network Admin only, as this applies to the entire network and not a single server. Generally, at least two Admins should should agree before setting the /akill. 4. Appealing of bans Made in writing by the person banned or a friend of the banned person who uses the server. Should contain a valid email, details of the ban, and a short reason as to why the ban should be lifted. Ban appeals will be considered by at least 3 admins, including either the president or copresident. Their decision is final, except the Network Adminstrator can overrule anyone and act independently to ban or unban, provided he gives his reasons for doing so. 5. Special powers and Responsibilities IRCops should not use their added capabilities to avoid a channel ban. Channel bans are beyond the normal interest of the Network Administration. IRCops will interfere in channel affairs only when invited by a channel owner, a majority of channel users, or when channel events significantly impedes the smooth functioning of the network. An IRCop or admin should not op themselves in any channel in which they do not normally hold ops except in the pursuit of their duties. Any IRCop, when oppered, is expected to aid network users to the best of his abilities and training. Every Op and Admin above the level of *local* Op (single-server) should be prepared to spend some non-idle time in #help each week. Everybody will start off as a Helperop and have classes to attend and progross from there |
![]() |
|
| 1 user reading this topic (1 Guest and 0 Anonymous) | |
| « Previous Topic · IRC OP APP · Next Topic » |







9:53 AM Jul 11