Compiling / Configuring a bot that won't demand OPs.

raven · Post by **raven** » Wed Aug 14, 2002 8:35 pm

Heya,

Due to various reasons I'd like to configure / compile an eggy that won't complain if it doesn't have ops on a(ny) channel it's on... Have check through the .conf file but can't find anything, it keep complaining in the partlyline. Do I need to recompile? Where should I look for the code to change?

Thanks in Advance.

ppslim · Post by **ppslim** » Thu Aug 15, 2002 8:12 am

Where is it suposed to be complaining?

What scripts are you running?

What does it say on the partyline?

It sounds line you have removed the lines from the confgi file that will make it complain. That or you have chnaged to a buggy script.

raven · Post by **raven** » Wed Sep 04, 2002 2:17 pm

woah.. forgot that I posted here... we'll now I'm back

ppslim wrote:Where is it suposed to be complaining?[/quite]

I don't want it to complain _anywhere_

ppslim wrote:What scripts are you running?
A bunch...
But it was like this before I installed them too....

ppslim wrote:What does it say on the partyline?
It says the message specified in the .conf file in the "need-op" parameter for the channel. Removing this will make the bot stop working.

ppslim wrote:It sounds line you have removed the lines from the confgi file that will make it complain. That or you have chnaged to a buggy script.
I don't want it to ask for ops... which is what I mean by "complaining"....

ppslim · Post by **ppslim** » Thu Sep 05, 2002 5:13 am

I must read things next time.

Eggdrop was designed for a protection role, allthough, it has many uses these days. Yet it's main area, is based on channel protection.

For this, the eggdrop needs OP's.

While you can disable/blank out the parts that will enable it to get ops via other means (IE neep-op), this will not prevent it from complaining on the partyline.

IE: It's designed to complain. The whole idea behind protection, is having the ops to protect with.

What is the exact message it gives, as I have been unable to find it in the source (normaly I would check other ways, but my bots are designed to be oped)

raven · Post by **raven** » Thu Sep 05, 2002 6:13 am

The message it gives is the one specified with need-op in the conf file. But I guess I cannot fix it very easy then....

Maybe I just missed something, but I cannot find a way to prevent the bot from kicking people who change mode on themselves. On the server I have it there is no services oping ops, instead it looks like the user is doing it themselves. The eggdrop recognizes this as netsplit abuse or something like that and kicks the user. I found one or two settings in the .conf that sounded like something about this, but changing them wouldn't change the fact it kicks people. And there's too many nicks to add them all to the bots protect/friend list and I don't have any plans to make the bot the one who ops and voices people instead of the server itself.

ppslim · Post by **ppslim** » Thu Sep 05, 2002 6:32 am

What is the message it displays on the partyline, regarding needing OP's. I can use this to locate in the code, what needs disabling.

As for the other issues.

See the +nodesynch option info .chaninfo

raven · Post by **raven** » Fri Sep 06, 2002 8:20 pm

ppslim wrote:What is the message it displays on the partyline, regarding needing OP's. I can use this to locate in the code, what needs disabling.

As I've replied all times you've asked before in this thread. It puts the line specified with need-op in the .conf file. That's it, no more, no less. About every 3rd minute or so.

ppslim wrote:As for the other issues.

See the +nodesynch option info .chaninfo

I've tried running with both +nodesynch and -nodesynch and the bot still kicks people when they change modes on themselves. It's not a "real" IRC server we're running on (not an ircd or whatever it's called) but some small company's own version, if this might cause an issue maybe? In mIRC I see the following when someone joins:

*** JohnDoe has joined #channel.
*** JohnDoe sets mode +o JohnDoe

Papillon · Post by **Papillon** » Sat Sep 07, 2002 3:40 am

a very easy way might be to make the bot automatically add the peeps as they join, then set the default-flag to f..... I don't say it's a good solution, or secure...

might be the solution if u've tried everything else

darko`` · Post by **darko``** » Sun Sep 08, 2002 5:59 pm

[darko@blah eggdrop1.6.12]$ grep -ir "is active but has no ops" .
./src/mod/irc.mod/irc.c: putlog(LOG_MISC, "*", "%s is active but has no ops

", chan->dname);

There you go. Comment that line out and recompile.

As for the other issue, +nodesynch *IS* a solution. Just make sure your changes did take effect. (save the channel file)

raven · Post by **raven** » Sun Sep 08, 2002 6:55 pm

Ok... I'm going to look into this further when I got my new box up and running (ETA 1-2 weeks). I only need to solve one of the issues... either I find a way to prevent the bot from kicking people, then it can be opped... Otherwise I find a way to make it stop complaining about not having ops.

As for the codeline, to me it looks like it's what it'll put into the logfiles, which isn't what I'm trying to prevent (even though I find it to be something I might want to prevent too in order to get readable logfiles), but rather prevent it from spamming the partyline.

Oh well, I'll get back to ya when I've fiddled some more with it myself. Thanks!

darko`` · Post by **darko``** » Sun Sep 08, 2002 7:25 pm

It does indeed go to logfiles, but since your console includes (prolly) +o flag, and you don't want to missout on other miscelaneous stuff, it is easier to comment out the code. Else, if you don't care, just .console -o.

darko`` · Post by **darko``** » Mon Sep 09, 2002 7:41 pm

This is a snippet of doc/UPDATE1.6

1.6.7 (7 December 2001)
Found by Fixed by What...
...
...
FeaRx/ Sup show `#channel is active but has no ops

' only if channel
DarkReap1 is set +statuslog.
...
...

I hope this finally answers your question - set it -statuslog