egghelp/eggheads community

Eggdrop deops itself to +voice status upon joining chan

2010-09-03T17:25:53-04:00

I personely have set all the flags the same as owner

turn xop of /msg chanserv SET #spf XOP off
then do /msg chanserv levels #spf list
the two that you need are these
-ChanServ- PROTECT 10
-ChanServ- PROTECTME 10

they need to be set to ten preferably if not use
/msg chanserv LEVELS #spf SET protect 10
/msg chanserv LEVELS #spf SET protectme 10

if you do not have access to do this you will need to get a server admin to do it for you

Statistics: Posted by blake — Fri Sep 03, 2010 5:25 pm

Eggdrop deops itself to +voice status upon joining chan

2010-09-03T13:56:18-04:00

Its a possibility that the chanserv access isn`t functioning how you need to run your bot on the channel giving the privaledges it needs

Also add chanserv as a user on the bot i had to do this to stop my bot fighting with services

in the mean time do the following /msg chanserv levels #spf list and copy the results to here if you have access to this command this will show what has been set and has not been set if the protect is disabled then your bot wont beable to set mode +a on itself

Code:

[10:54] -ChanServ- Levels are not available as xOP is enabled on this channel.

Thats the message I got when I typed in what you asked me to.

Also, should there be specifi flags I assign to chanserv in the userlist of the bot? By default the flags that are set are fh.

Thanks again to all who have helped so far.

Statistics: Posted by marvz — Fri Sep 03, 2010 1:56 pm

Eggdrop deops itself to +voice status upon joining chan

2010-09-03T10:24:15-04:00

Its a possibility that the chanserv access isn`t functioning how you need to run your bot on the channel giving the privaledges it needs

Also add chanserv as a user on the bot i had to do this to stop my bot fighting with services

in the mean time do the following /msg chanserv levels #spf list and copy the results to here if you have access to this command this will show what has been set and has not been set if the protect is disabled then your bot wont beable to set mode +a on itself

Statistics: Posted by blake — Fri Sep 03, 2010 10:24 am

Eggdrop deops itself to +voice status upon joining chan

2010-09-02T16:53:45-04:00

Ok, I've been using the script for a few weeks now and have seen some stuff happen.

For one, the setting of -nodesynch is in place. Yet, if the bot is opped for whatever reason it will start doing the same thing. It fights with chanserv over halfop/op the user in the chan if they haven't identified with nickserv. I removed the ay flags on the users but it is still doing it anytime that the user comes on without identifying.

Second, when the bot joins the chan it executes the script perfectly, but it doesn't add the +a flag to itself in order to protect itself from other op/sop users from "messing" with it (see example).

Code:

[13:30] * beersnob was kicked by marvz (marvz)[13:30] * beersnob (beersnob@look-random-characters-E150081B.com) has joined #spf[13:30] * ChanServ sets mode: +ao beersnob beersnob[13:30] * beersnob sets mode: -a beersnob[13:30] * beersnob sets mode: -o beersnob[13:30] * ChanServ sets mode: +v beersnob[13:30] * marvz sets mode: +o beersnob[13:30] * marvz sets mode: -o beersnob[13:31] * marvz sets mode: -v beersnob[13:31] * marvz sets mode: +v beersnob[13:31] * marvz sets mode: +o beersnob[13:31] * marvz sets mode: -o beersnob

I have SOP access on the chan but if the a mode would be set on the bot even I wouldn't be able to do anything to it but let it sit there in whatever it has set itself in (+v in this case).

So what do you guys make of this?

Statistics: Posted by marvz — Thu Sep 02, 2010 4:53 pm

Eggdrop deops itself to +voice status upon joining chan

2010-08-11T00:34:17-04:00

If your bot is fighting with services on the channel telnet to your bot and type

.chanset #channelname -nodesynch

if your bot has aop/sop on the channel use a set option for it to identify to chanserv on joining the channel
then maybe a small script that will voice it first then deop it chances are that some of the basic access levels are disabled like deopme op deop

willyw if you would like access on a server that will allow you full access i have a test server that i run inbox me if you would like to use it

I will have to wait for a split or someone that is on the aop/sop lists to do the same mistake again to test that out. I don't have a way to test it without that happening. thanks for the info/suggestion and I'll keep it in mind should this occur again.

Statistics: Posted by marvz — Wed Aug 11, 2010 12:34 am

Eggdrop deops itself to +voice status upon joining chan

2010-08-11T00:31:55-04:00

willyw:
...
I removed the a flag on the users and left them with the o flag and the bot still did the same thing. I thought it might've been something that would need a restart or something but, even though I restarted it, the bot kept doing it. Is there a certain time frame that the bot needs in order for it to implement the changes?
I believe the change is immediate.

Perhaps these users have(had) two +a flags - one global, and for the channel?
Do a .whois on a few of them, and have a look at both global flags, and channel flags.

Something is causing it - we just need to find it.....

I'll try the script tonight and report back and let you know how it worked out. Thanks again for the help.
You're welcome.

I couldn't do the .whois because I just deleted the users and added them all with the fh flags for the time being while I figured this out.

I used the script and its working like a charm! Thanks a lot! This will do unless there is a fix without the use of a tcl script.

Statistics: Posted by marvz — Wed Aug 11, 2010 12:31 am

Eggdrop deops itself to +voice status upon joining chan

2010-08-09T22:50:21-04:00

If your bot is fighting with services on the channel telnet to your bot and type

.chanset #channelname -nodesynch

if your bot has aop/sop on the channel use a set option for it to identify to chanserv on joining the channel
then maybe a small script that will voice it first then deop it chances are that some of the basic access levels are disabled like deopme op deop

willyw if you would like access on a server that will allow you full access i have a test server that i run inbox me if you would like to use it

Statistics: Posted by blake — Mon Aug 09, 2010 10:50 pm

Eggdrop deops itself to +voice status upon joining chan

2010-08-09T09:58:24-04:00

willyw:
...
I removed the a flag on the users and left them with the o flag and the bot still did the same thing. I thought it might've been something that would need a restart or something but, even though I restarted it, the bot kept doing it. Is there a certain time frame that the bot needs in order for it to implement the changes?

I believe the change is immediate.

Perhaps these users have(had) two +a flags - one global, and for the channel?
Do a .whois on a few of them, and have a look at both global flags, and channel flags.

Something is causing it - we just need to find it.....

I'll try the script tonight and report back and let you know how it worked out. Thanks again for the help.

You're welcome.

Statistics: Posted by willyw — Mon Aug 09, 2010 9:58 am

Eggdrop deops itself to +voice status upon joining chan

2010-08-08T23:22:35-04:00

willyw:

The chan has secureops on it and that's why the issue arose. The owner chose to do it that way and well, its his chan and its his call.

I removed the a flag on the users and left them with the o flag and the bot still did the same thing. I thought it might've been something that would need a restart or something but, even though I restarted it, the bot kept doing it. Is there a certain time frame that the bot needs in order for it to implement the changes?

I'll try the script tonight and report back and let you know how it worked out. Thanks again for the help.

Statistics: Posted by marvz — Sun Aug 08, 2010 11:22 pm

Eggdrop deops itself to +voice status upon joining chan

2010-08-07T11:39:49-04:00

marvz:

Your network uses Unreal ircd, and probably Anope for services.
This is what I'm used to.

I suspect that the owner of your channel has set Secureops.
You can read about it a bit, with:

Code:

/msg chanserv help set secureops

If that is what the channel owner really intends, then all well and good. That's what he wants....

But, it could be unnecessary or unintentional. If you are not sure, could it hurt to ask the owner if he cares to remove it?
If that Secureops setting is removed, I think the problem that you described would be gone.

If he wants to keep it, then I think your best option is to remove the +a flag from your ops in the bots internal user list, and let the ops op themselves via /msg, as described above. This is secure.

But, in the interest of your original post ( and again, I feel this is a work-around, and not the best solution), here is something for you to try:

Code:

# Upon joining, bot will remove its own SOP, then remove the remaining OP.# Bot will then VOICE itself# There are two commands available (for +o users of the bot) - both are via /msg to the bot. ## /msg  !resop# will cause the bot to regain its SOP status## /msg  !desop# will cause the bot to remove its own SOP, then remove OP, and voice itself.  (Same as when it joined)#####  Config# Set the channelset desop_chan "#spf"# Set the mask of the bot.  You may need to use wildcards.# format is:    nick!user@hostset botmask "beersnob!beersnob@*.dsl.irvnca.pacbell.net"### End Config###   scriptbind join - "$desop_chan $botmask" bot_desop_itselfbind msg o "!resop" resopbind msg o "!desop" msg:bot_desop_itselfproc bot_desop_itself {nick uhost handle chan} { global botnickputserv "mode $chan -a $botnick"putserv "mode $chan -o $botnick"putserv "privmsg chanserv :voice $chan $botnick"}proc resop {nick uhost handle text} {set chan [lindex [split $text] 0]putserv "privmsg nickserv :logout"putserv "privmsg nickserv :identify rowbot"}proc msg:bot_desop_itself {nick uhost handle text} {global desop_chanbot_desop_itself $nick $uhost $handle $desop_chan}

I have not registered nicks, etc. on your network, to test this on your network. On another network, that uses Unreal and Anope, where I do have nicks for a test bot, I have tested it. It worked there.

Above, in the little Config area, the info for the #channel and bot's mask could already be correct for you. You should double check that though.

Statistics: Posted by willyw — Sat Aug 07, 2010 11:39 am

Eggdrop deops itself to +voice status upon joining chan

2010-08-07T10:33:09-04:00

A large problem is, that afaik, eggdrop does not see a few modes as being "valid irc modes". I had this discussion with one of the developers not that long ago. So if you try to pushmode mode a or q, it won't work, although this is rumored to be fixed... sometime.

Also, I at one point tried to get my bot to do something similar. I tried a regex to catch the "botnick has joined #chan" message and make my bot send a mode- it wouldn't. It almost seems like we need a new "onchanjoin" bind to do this. We have the server evnt for when we first join a server and id, but afaik, there isn't a way to do so on channel join.

Statistics: Posted by Luminous — Sat Aug 07, 2010 10:33 am

Eggdrop deops itself to +voice status upon joining chan

2010-08-07T09:49:08-04:00

This is what would happen since the user was not identified with nickserv:
23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
...
That's what I meant by the bot fighting with chanserv.

ooohhh...
uuuuuuugly.

Since the user is not identified with nickserv chanserv doesn't allow the user to be oppped even though they're on the AOP/SOP list.

The network that I hang on mostly, doesn't do that. You can be op'd with no problems.
Thanks for explaining.

Would it be feasible, in your case, to not give your operators the a flag?
Give them just the o flag.
Then, your bot would not try to automatically op them upon joining.
Instead, they would have to send:

Code:

/msg botnick op  [channel]

and then the bot would op them.

This way has the additional benefit of being much more secure too, as each op'ing would be password protected, unlike auto-op'ing.

Statistics: Posted by willyw — Sat Aug 07, 2010 9:49 am

Eggdrop deops itself to +voice status upon joining chan

2010-08-06T23:19:48-04:00

This is what would happen since the user was not identified with nickserv:

23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com
[23:00] #spf: mode change '+o ddog' by beersnob!beersnob@look-random-characters-D3DDEC9A.dsl.irvnca.pacbell.net
[23:00] #spf: mode change '-o ddog' by ChanServ!services@irc4lyf.com

That's what I meant by the bot fighting with chanserv. Since the user is not identified with nickserv chanserv doesn't allow the user to be oppped even though they're on the AOP/SOP list.

the network is irc.irc4lyf.com[/code]

Statistics: Posted by marvz — Fri Aug 06, 2010 11:19 pm

Eggdrop deops itself to +voice status upon joining chan

2010-08-06T21:00:16-04:00

I looked into having chanserv or nickserv doing it
...

What network?

Statistics: Posted by willyw — Fri Aug 06, 2010 9:00 pm

Eggdrop deops itself to +voice status upon joining chan

2010-08-06T20:54:15-04:00

...
I'm looking to have the bot perform this automatically because if one of the other admins isn't around the bot would sit in the chan as a SOP. I want to avoid this beause we had a split the other day and when users joined the chat that had the aol (no pun intended) flags it kept trying to op them even though the hadn't identified through nickserv so it was basically a war between the bot and chanserv.

SO at this point I'm drawing a blank as to how to get the bot to autimatically perform these actions to avoid that happening.

If this is what you really want, then this is what should be addressed.
Not a work-around.
We might even figure out something that is better.

If a user has +a in the bot, then the bot will try to op them, when they join.

a - autoop (user is opped automatically upon joining the channel)

do .help whois to get a list of all the flags.

Thus, whether or not they have identified with Nickserv has no bearing.

What do you mean by a war between the bot and Chanserv though?
What exactly was happening?

It would seem like the bot would have op'd them, and that would be the end of it.

Sorry ... I'm not getting the whole picture.

Statistics: Posted by willyw — Fri Aug 06, 2010 8:54 pm