Well, it was set up before that IRCops were immune to being akicked or banned via ChanServ...which helped IRCops do their jobs when it came to affairs that come up often. However, the admin had to restart services from the ground because of a shell breach, and now all IRCops, including those who are services roots, are affected by these (even with +q set, although that doesn't matter anyway). Is there a config option that was overlooked?