Eggdrop Bitch Mode

blood_x · Post by **blood_x** » Thu Dec 12, 2002 6:46 am

Dear All,

First of all, I would like to wish a Happy Eidfitri and Merry Christmas! Where's my present..

Here I would like to know on how bitch mode setting in eggdrop can be more effective. For example, I have set +bitch in my channel using eggdrop 1.6.13, but when someone request op through X bot (Undernet Bot), and the op isn't in my eggdrop userlist, he/she can be +o and be idle over my channel except when he/she change nickname, then my eggdrop will automatically deop him/her because bitch mode detection.

It should work like this;
a). When someuser request op through other bot, my eggdrop will rescan the op status, which mean @op is in userlist.
b). Otherwise, my eggdrop will -deop to someuser who isn't in my eggdrop userlist automatically and periodically till the op get @op in my eggdrop.

Thanks.

Photon · Post by **Photon** » Thu Dec 12, 2002 7:12 pm

Not entirely sure what you want ... but read the docs on bitch mode - if this does not provide enough cover for you (as you no doubt have to auth with X to get ops) then you might like to look up slennox's netbots as it contains a component called superbith .. also there is an ultrabitch.tcl in the tcl library (search for bitch)

HTH

blood_x · Post by **blood_x** » Sun Dec 15, 2002 10:31 am

Photon wrote:Not entirely sure what you want ... but read the docs on bitch mode - if this does not provide enough cover for you (as you no doubt have to auth with X to get ops) then you might like to look up slennox's netbots as it contains a component called superbith .. also there is an ultrabitch.tcl in the tcl library (search for bitch)

HTH

Dear Photon,

I already load superbitch.tcl but it doesn't work. What I requested here is, someone get deop automatically if he/she doesn't have any flags in bot. For example, if user A which has +p|+gov #channel flags, do op user B which isn't in userlist (flags -|-), and my bot detect that user B isn't in userlist and automatically deop him. In other word, my bot always monitor who get +o in my channel and deop him/her automatically if he/she doesn't has a valid flags for that channel.

For now, I have loaded superbitch.tcl and set my channel +bitch, but when someone op anyone who isn't is my bot userlist using X bot, my bot doesn't deop him/her unless he/she changing nickname, then my bot detect and deop the user. If he/she doesn't changing nickname, my bot permit he/she to get OP mode in the channel.

Thanks.

Post by **slennox** » Sun Dec 15, 2002 6:46 pm

Eggdrop's bitch mode alone should deop the opped nick in your example case. superbitch.tcl would add to this by also deopping the user who opped the nick. It sounds like you want just standard bitch mode, and don't require the supetbitch script, so you might want to remove it to help reduce the variables when figuring out what's going on with the standard bitch mode.

ppslim · Post by **ppslim** » Sun Dec 15, 2002 8:13 pm

There are several reasons why this may be failing to work correctly.

1: You may have a user-record that is clashing with that user, and eggdrop matches that person till there nickname changes.

2: You are on a non-RFC following network, where eggdrop is getting a non-standard /who reply. This will cause eggdrop to think it is not properly on channel, and cause issue simalar to this.

blood_x · Post by **blood_x** » Mon Dec 16, 2002 7:00 am

So, any solution for me? I connect my eggdrop on Undernet IRC server..

ppslim · Post by **ppslim** » Mon Dec 16, 2002 7:27 am

I don't possibly see any solution, unless we know the problem.

Until this is found, it's plain impossible.

First off, check .status, make sure the bot thinks it's in the channel (IE, it's not pending).

Second, route through your user-records, and find out about clashing records.

Photon · Post by **Photon** » Mon Dec 16, 2002 7:29 am

as pointed out .. this could possibly be because you are using too loose hostmasks ...

The bot should deop in bitch mode ANYONE it doesnt recognise (and it does normally - on quakenet anyway) and do this immediately.

If you could isolate a person that this happens with, then look at their host (/whois), and see if that could be matched by any user's hostmask. If so, then you have your problem. Tighten the hostmask and it should go away.

However, doesnt undernet do something wierd with people's hosts when they are identified with X? What I'm saying is I'm not sure whether its your hostmasks or the network you are on tbh - someone with a bot on undernet would probably be of more use.

More investigation is definately required.

blood_x · Post by **blood_x** » Mon Dec 16, 2002 5:44 pm

ppslim wrote:I don't possibly see any solution, unless we know the problem.

Until this is found, it's plain impossible.

First off, check .status, make sure the bot thinks it's in the channel (IE, it's not pending).

Second, route through your user-records, and find out about clashing records.

Dear ppslim,

I load eggdrop version 1.6.13 with stats.mod v1.3.3dev1 (http://www.visions-of-fantasy.de/stats.mod/) and superbitch.tcl (slennox's tcl script). I have configured my eggdrop properly, and my eggdrop is in the channel.

Here, im afraid if that stats.mod are confusing my entire userlist, because I saw that the stats know person via nickname, not by their hostname. Is it possible?

Then, I adding user by fixed/secured Undernet hostname which is *!*@username.users.undernet.org. For example, user A hostname is
A!ident@ykznet.users.undernet.org. User A only has +p|+gov flags #mychannel in my eggdrop. Then user B which is B!regular@somehostname.com and doesn't have access in my eggdrop. To test +bitch mode function, i asked user A to op user B using X bot (Undernet Service). X has +bof|+fmo flags #mychannel. After that, X set mode +o B and my eggdrop doesn't detect that user B isn't in userlist and permit him to be op. After user B change his nickname to C, then my eggdrop detect he doesn't have a valid flags and deop him. If he doesn't change his nickname, my eggdrop permit him to be op in the channel eventhough i have set my channel to +bitch and load superbitch.tcl.

And now, I wonder how this things can happen, so I discuss here..

Thanks for your commitments.

ppslim · Post by **ppslim** » Mon Dec 16, 2002 5:54 pm

Yes, this is prbably the problem.

Just as with web-hosting, where e-mail, web, database and firewall systems should be seperate, eggdrop should be the same.

CHannel protection functions are not suited for a bot dealing with heavey memory loads from a statistics function.

This is applied for any task. IE, one bot for onjoin, and heavy message output liek seen information, and channel protection should allways remain seperate.

blood_x · Post by **blood_x** » Mon Dec 16, 2002 6:16 pm

Aha, I have to order new unix shell hosting.. then load for one statistic eggdrop

Now, I used risingnet.net for my unix shell account with domain. You can view my stats at http://www.ykznet.com. Hum, if that stats make eggdrop bitch mode not functioning, I should remove it.. or there's any way to solve this thing? IE load additional bitch_mode.tcl..

ppslim · Post by **ppslim** » Mon Dec 16, 2002 7:10 pm

There is no way to load an aditional script to do this.

The bitch script, realy on the userfile, and user-records, to tell apart real and non-real users.

Again, the stats mofule does the same thing.

Thus they start clashing.