Protecting IRCop Channel

[Orbixx]

Hey there, I've racked my brains for a while now trying to think of a logical solution to only allow IRCops to join the channel. Does anyone know of a way to do this?

Also, on a side-note, what would be the best way to set up a trivia bot? Eggdrop? Or something else?

Thanks in advance guys.

[Jobe]

Are you being serious? (No offence intended)

Look for channel mode +O (Tip type /helpop for a nice handy help system)

Another way would be to use a "deny channel" block which IRCop's are exempt from anyway. But the mode option is far easier since thats network wide, whereas youd need deny channel blocks on ALL servers.

This section lists all of the possible channel modes that may be used with /MODE

==------------------------------oOo----------------------------==
v <nickname> = Gives Voice to the user (May talk if chan is +m)
h <nickname> = Gives HalfOp status to the user (Limited op access)
o <nickname> = Gives Operator status to the user
a <nickname> = Gives Channel Admin to the user
q <nickname> = Gives Owner status to the user

b <nick!ident@host> = Bans the nick!ident@host from the channel [h]
c = Block messages containing mIRC color codes [o]
e <nick!ident@host> = Overrides a ban for matching users [h]
I <nick!ident@host> = Overrides +i for matching users [h]
f <floodparams> = Flood protection (for more info see /HELPOP CHMODEF) [o]
i = A user must be invited to join the channel [h]
j <joins:sec> = Throttle joins per-user to 'joins' per 'sec' seconds [o]
k <key> = Users must specify <key> to join [h]
l <number of max users> = Channel may hold at most <number> of users [o]
m = Moderated channel (only +vhoaq users may speak) [h]
n = Users outside the channel can not send PRIVMSGs to the channel [h]
p = Private channel [o]
r = The channel is registered (settable by services only)
s = Secret channel [o]
t = Only +hoaq may change the topic [h]
z = Only Clients on a Secure Connection (SSL) can join [o]
A = Server/Net Admin only channel (settable by Admins)
C = No CTCPs allowed in the channel [o]
G = Filters out all Bad words in messages with <censored> [o]
M = Must be using a registered nick (+r), or have voice access to talk [o]
K = /KNOCK is not allowed [o]
L <chan2> = Channel link (If +l is full, the next user will auto-join <chan2>) [q]
N = No Nickname changes are permitted in the channel [o]
O = IRC Operator only channel (settable by IRCops)
Q = No kicks allowed [o]
R = Only registered (+r) users may join the channel [o]
S = Strips mIRC color codes [o]
T = No NOTICEs allowed in the channel [o]
V = /INVITE is not allowed [o]
u = Auditorium mode (/names and /who #channel only show channel ops) [q]

[h] requires at least halfop, [o] requires at least chanop, [q] requires owner
==------------------------------oOo----------------------------==

[Jason]

To be fair, the advantage of a deny channel block is that it will protect an empty channel too, and will use your custom reason.

[Jobe]

Jason is correct. Personally i use a combination of 3 ways to protect it on my net.

1. deny channel block
2. channel mode +O
3. set the ChanServ restricted mode on which means only opers or users on the access list for the channel are allowed to stay, the rest are kick-banned.

[Orbixx]

Thanks for the feedback, I didn't realise it was as simple as a channel mode. It's unusual that I initially think past the obvious.

As for Bots, specifically a trivia one, I ask from your experience, what is the best way to have one set up?