Paradise IRC Network Operator Guide/Server Admin Rules/Regulations
By: Paul 'paulmer2003' Merlin
NOTE: A good preface to this guide would be http://www.irchelp.org/irchelp/ircd/ircopguide.html. Sure its designed for EFnet operators and most of the technical stuff will go over your head, the parts about dealing what channels and abusive users and in general irc operator politics is good. Do read.
NOTE2: Yeah yeah..Some of you will disagree with major parts of this..Please dont flip out and go mega-pms on me kthx.
--MOTD--
Your servers MOTD (Message Of The Day) should be short and snappy. No need to include your fucking life story in it. Simply add the rules for your server, and keep ASCII art to a minimum please. Also, please include something about using /STATS p to recieve a list of staff members. Make sure the entirity of your MOTD can fit on one screen. Also, you may not use the same rules as WinBeta/BetasIRC/R-Type. They all have ripped off the rules from each other, and it looks majorly moronic.
--Server Names--
Sure, you have the 'right' to use what server M:Line (Server name and description) you want, but if you name the server after your self, it looks extreamly unprofessional and lame. Make server names dictionary words (That you can lookup) and only one word long.
--Use of KILL/GLINE/KLINE/DLINE/RESV--
Simply put, channel matters are channel matters. Dont like someone? Well thats too bad, suck it up. Dont be a abusive fucker and be like 'I HATE YOU *GLINE*'. That makes us ALL look like a bunch of jerkoff morons. If someone is channel evading, simply add another +b. Only time when a *line is deserved is when a (ab)user is threating network security.
--A:Line (/admin)--
Your A:Line should look like this (Use real information please).
* Administrative info about Hub.Paradise.Net
* Paul 'paulmer2003' Merlin
* Primary Hub Server
* Paul@OpenHacker.com
You should have your name, nick, email and server info there.
--SANICK/SVSNICK/SVSJOIN/SVSPART/FORCEJOIN/FORCEPART--
I really despise these commands, for I have been abused on lame ass unreal networks way too many times to see operators on my network abuse such commands. If you are seen abusing such commands, expect a reprimand.
--Services Access--
512, Trainer4 and myself will have Services Root.
All server owners will have Services Admin.
All others whom have O:Lines will have Services Operator.
--Server Staff--
If you are a server operator, you are the only one allowed with a admin =yes; in O:Line.
--Cluseter Use--
A nice feature that Hybrid/Plexus/Ratbox has is called clustering. Basically what it does is allows you to share klines/glines/resv and other such things with other servers. Do NOT change the clusters that are in your ircd.conf server owners.
--vHosts--
If you are going to have a vHost, please make it end a proper TLD. I plan on talking to a coding from of mine and get him to make us a mod on hs_request so people can only have vHosts that end in proper TLD's (Or ccTLD's).
--Channel Modes aq--
Yes, our ircd does support aq. However, we will not be using it. If you are stupid, and compile your server with it you will be delinked untell your server is properly configured.
--zlib--
Our IRCd supports zlib (compressed) server links. It is expected that you link your server via zlib.
If it sounds like Im (Or we) are being facist bastards, we arent. We are simply trying to run a network that will best z