Icarus IRCd oper flags:

Before with Unreal certain things are assumed, that is it's assumed that NetAdmin has at least server admin access so NA's can rehash, restart the 
ircd at will, even if it isn't theirs. We believe that only the server admin can choose who can or can not rehash their server as well as many 
other assumptions made by the ircd. can_override, can_setw .. etc were all assumed for NetAdmin.

This is not the case with Icarus. The NetAdmin flag only gets you the umode +N and the fancy SWHOIS title, that's all. All oper flags are 
explicitly assigned with a few exceptions. Local IRCops can use /helpops, /globops and /wallops as well as get umode +O. *ALL* other flags, 
including /kill *MUST* be added as a seperate flag or the oper can not use it!!

Additionaly, this is also true for ServerAdmins as well. They can obviously die, rehash, route and restart their server .. after all it *IS* their 
server. However, no one else can without the appropriate flags being assigned! That means CO-Admins need the can_rehash flag or they are SOL when 
it comes to rehashing the ircd.

Why would we do this? Glad you asked! Greater control over whom can do what on your network. You no longer have to allow everyone the ability to 
perform tasks you don't want them to be able to do. In Unreal you had no choice .. NA's can do anything to your server, in Icarus they can't unless 
you allow them by adding the correct flag to their oper block! NA's can't even /kill unless the hosting server for their O:Line allows it.

Warm Regards,

The Icarus Coding Team

