Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ben]

wow 2 in a row, my ideas are all coming out at once

i noticed a problem
lets say you have #Log and of course the opers are away like always so there not in the room or something stupid like that
then some guy joins #Log, of course mlock activates and sets +O or whatever, but thats after he joins

os if you have /Cs set channel modeonjoin [on|off]
then when he joins it kicks him out (Mode +O affects your join)

restrict is annoying
i thought about akick or suspend but locol opers are affected by that

[katsklaw]

Unfortunately there is little that services can do about this because Anope doesn't find out about the user joining until after the fact. Mode locks can not exist on channels that do not exist.

Please dont confuse a registered channel with an existing channel .. they are definately not the same.

It is possible that a module could check to see if the user that joined is an oper and kick them, but nothing can stop them from re-joining the channel again, over and over creating a sort of join/part flood.

the best solution is to have an opered client bot idle in the channel to hold the channel modes in place or if you have an ircd that has the ability to deny the use of specifiy channels such as Unreal's deny::channel block.

[SNU]

What about: /cs set restricted on ?