trouble Anope and mode +a

[Icarus]

Hi, I use services Anope 1.7.21 and last eggdrop 1.6.19.

I have this problem:
I have Bot in ChanServ's ACCESLIST of my channel. He has level 10 (default flags like AUTOPROTECT, MEMO etc.). When bot joins to the channel, everything looks fine (Bot has mode +a, it is protected), but bot doesn't give OPs to anybody.

At firt, I think I have bad config.. Toady I know when ChanServ sets mode +a Bot and after this ChanServ gives channel operator status to Bot, then Bot thinks, that it can't give OPs.. (I tryed - console: .op <user>) and it says:

"I can't help you now because I'm not a chan op or halfop on #atreides, or halfops cannot set +o modes."

And when I "turn off" AUTOPROTECT (move to higher level), so ChanServ give just OP to Bot and it gives everybody, who I set up.

Thank you very much for information!!!

PS: I know, OPs, HOPs - I can set everything in ChanServ's access list, but this problem is weard and I want to know solution

[speechles]

All you gave it was protection (+a) this contains no mode enhancement. Hence, when it comes to operator abilities, it cannot perform those so gives you the message it does. You need to protect it via chanserv (+a) as well as give it operator (+o) status to work. Then edit eggdrop.conf adding what is below in the appropriate place:

Code: Select all

proc evnt:init_server {type} {
  global botnick
  putquick "MODE $botnick +i-ws"
  putquick "NS identify password"
}

change the "ns identify password"' to whatever the equivalent is for it to identify itself properly to nickserv to claim rights to it's nickname and all channel privileges attached. I guess you want the bot to protect the channel but not issue auto-ops to others, in the bots own "eggdrop" records remove any auto-flags (+a) and it won't race chanserv to op others (.chattr handle -a #chan).

You might also just need to change the operator variable within eggdrop.conf to add the complete list of symbols used to signify the bot has operator status.

[Icarus]

Hmm, I don't know exactly, I have explained very good..

ChanServ gives +a mode AND +o (or OP) to my BOT now. And Bot doesn't work. He doesn't give OP to anybody.

When I give +a mode AND +o to my BOT, so Bot gives OP to everybody, who I set up via console.


I'm going to try "change the operator variable..." but I don't know how. I can't look for it in documentation.

[blake]

you need to add each user seperate using
.adduser usersnick
this will allocate them a handle and assign their hostmask handle can be recognised as [nick] normaly 9 charecters

then do
.chattr handle +o this will give them op flags on the bot

you then need to set them a password
.chpass handle newpass

They are then able to op them selves by doing
/msg botsnick op password #channame

just make sure you tell them the password

[TCL_no_TK]

eggdrop should have not problem with +a since its detected as a channel mode. If eggdrop isn't detecting its op'd after getting op'd via ChanServ, sounds like it could be desync'd.
I would also check the channel operators prefix settings in eggdrop config file, as you have mentioned them. just to make sure they are correct.

Code: Select all

set opchars "@"
#set opchars "@&~"

Some IRC servers are using some non-standard op-like channel prefixes/modes. Define them here so the bot can recognize them. Just "@" should be fine for most networks. Un-comment the second line for some UnrealIRCds.

Unless you use the & and/or ~ prefix for ops, i would leave them out.