Deop user that was op'ed by op

cache · Post by **cache** » Thu Aug 17, 2006 11:48 am

I tried with no luck looking in archives..

I'm trying to get a script that will make the bot deop the user who was giving ops.

Sample:
RoomOP: sets mode +o Nick2
Bot: sets mode -o Nick2
Bot: RoomOP, don't make me fire you :/

Thanks.

Post by **nml375** » Thu Aug 17, 2006 11:57 am

Setting the channel +bitch should do this, atleast the de-opping (won't nag the one opping tho).

There's also a few scripts with names similar to "bitch" that behaves in a similar fashion (some kick, some do ther stuffs), might be worth checking..

cache · Post by **cache** » Thu Aug 17, 2006 11:32 pm

Yeah but if I use +bitch don't that mean I have to give all ops a +o flag via the bot? Our chat network allows all ops to join channels automatically op'ed by the server so you come in like:

[8:00pm] * Joins: Nick (Nick@Nick)
[8:00pm] * Nick sets mode: +o Nick

Thanks

Alchera · Post by **Alchera** » Fri Aug 18, 2006 3:42 am

eggdrop.conf:

#
# bitch
# Only let users with +o flag be opped on the channel?
#

'stopnethack-mode' is also affected if not turned off.

Some networks have a 'SecureOps' setting the forbids anyone not in the access list getting opped.

-ChanServ- Syntax: SET channel SECUREOPS {ON | OFF}
-ChanServ-
-ChanServ- Enables or disables the secure ops option for a channel.
-ChanServ- When secure ops is set, users who are not on the userlist
-ChanServ- will not be allowed chanop status.

cache · Post by **cache** » Sat Aug 19, 2006 1:56 am

I tried +bitch and the bot didn't deop anyone or do a thing when ops gave others temp ops??

I then tried superbitch.tcl in scripts archive that was no go, same for a few other scripts, those deop scripts look like old coding so im guessing their out of date?

While im still learning tcl, I still don't know how to make the bot grab the 2nd nick.. 1stNick: sets mode +o 2ndNick then deop it.

Thanks

Alchera · Post by **Alchera** » Sat Aug 19, 2006 2:39 am

The Network you reside on has no services? If they do, then simply save yourself a headache and do as I suggested in my post; that is unless this is a "project" you have undertaken to see how many headaches can be gained in one day.

MODE #channel +o Nick
nick!username@domain.com MODE #channel +o Nick

The above is the notice sent when a user ops another.

Just use your RAW log window in mIRC to view various events.

Post by **nml375** » Sat Aug 19, 2006 8:22 am

If your bot does'nt deop ppl being opped, it's due to one of these reasons:

User opping is identified as Master (+m) or Owner (+n)
User being opped is identified as an Op (+o)
Channel was not successfully set +bitch

Also, having your eggdrop stopping ppl from opping other can be abit daunting, as you'd still have to keep a list of who's allowed to op, possibly who's allowed to get ops, etc..

I'd either try something like suggested by Alchera, or let the eggie handle all opping, except using services to keep bots opped at all times..

Trying to keep eggdrop userlists and channel service permissions in sync is just a... well, ****** mess.

As for the mode binding, try something like this:

Code: Select all

bind mode - * check_deop
proc check_deop {nick host hand chan mode target} {
 if {$mode == "+o" && ![isbotnick $nick] && ![isbotnick $target]} {
  pushmode $chan "-o" $target
 }
}

Should'nt allow anyone to op other than your bot.. prolly have to tweak it to handle service-op properly...

cache · Post by **cache** » Sat Aug 19, 2006 1:16 pm

Nope it don't have secureop services thats why I am looking for a simple script to force bot to deop temp oppers, the bots op levels are stronger then the regular ops levels...

cache · Post by **cache** » Sat Aug 19, 2006 1:50 pm

Code: Select all

bind mode - * check_deop 
proc check_deop {nick host hand chan mode target} { 
 if {$mode == "+o" && ![isbotnick $nick] && ![isbotnick $target]} { 
  pushmode $chan "-o" $target 
 } 
}

This did the trick thanks