Deop on idle

[simo]

Greetings,

I'm using a deop on idle tcl on dalnet wich works fine except
If the op has higher access than the eggbot
He gets opped again by chanserv right after he gets
Deopped on idle i was looking for a way (without having to keep adding each exempted nick in the tcl) to not deop
Such admins to prevent constant -o +o of same admins who have higher access

Thanks,

[CrazyCat]

I don't think you have any other solution than creating a list of excluded users.
Peharps can you fill it automatically by adding the nick of the user if he's re-opped by chanserv after your script deop him.

Or give the eggdrop a higher access than everyone

[simo]

thanks for your reply CrazyCat , i was thinking of adding a flag right after the OP gets Re-Opped again by chanserv to not deop again checking if that flag has been set on that OP except im not sure how to achieve that or if thats doable.

[CrazyCat]

If you add a flag, it means you have the user in eggdrop's users base.
So why don't you just add the flag by the hand (like +O) and modify your script to exempt +O users from being deopped ?

But if you want to have a kind of automation for that (very bad idea imho), it's possible to temporaly store the nick and if he is reopped by ChanServ in a reasonnable delay, add him the good flag.

BTW, as I already said, automating this kind of privileges is a really bad idea.

[simo]

im facing another issue as op status is protected in channel meaning if someone is not on the access list and is opped manually by someone chanserv will deop them, wich could be conflicting with what im trying to do. im not sure if what i want to achieve is doable would you have an example of how it could be done CrazyCat as im clueless how to aproach this.
The reason i want to automate this is to constantly add and delete manually as nicks are added and removed from the access list over time.

thanks in advance.

[CrazyCat]

The reason i want to automate this is to constantly add and delete manually as nicks are added and removed from the access list over time.

So peharps you must change the way your channel is working and use the eggdrop as maintainer of the access: a command allow admins to add/remove @ in eggdrop list then the eggdrop send chanserv the ADD/DEL op to the chan.

I can't figure why the list of ops in a channel can change so frequently

[simo]

thanks for your reply CrazyCat, i rather use chanserv for that to be honest as its more effiecient to deal with channel access list regardless of IP and such.

[simo]

so far this is what i can came up with if its proper, except i dont know how to calculate the time between nick was deoped for idle and then opped again again by chanserv before 1 or 2 seconds past to determine it was cause of a higher status than the eggbot Re-Op.

Code: Select all

bind mode - "#% -o" Check-Higher-Status 

proc Check-Higher-Status {nick uhost handle chan mode target} {
            if {[string match -nocase {ChanServ} "$nick"]} {  
              chattr $target -|+O $chan
 }
}