This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

unleaflike behavoir?

General support and discussion of Eggdrop bots.
Post Reply
n
nicks0r

unleaflike behavoir?

Post by nicks0r »

*** Disconnected from: slacker. unleaflike behavior (lost 1 bot and 0 users)

keep getting this error, all the flags are set correctly, any ideas?
n
nicks0r

Post by nicks0r »

also to go along with this problem i have leafs rejecting eachother?

[23:47] <slack3r0> [09:52] slacker rejected maiden
W
Wcc
Master
Posts: 278
Joined: Sun Oct 28, 2001 8:00 pm
Location: USA
Contact:

Post by Wcc »

See the release notes for 1.6.17. If you're sharing userfiles, and you upgrade any of the leafs, all the hubs need to be upgraded too. It's best toupdate the whole net.
n
nicks0r

Post by nicks0r »

but all i upgraded was the hub
User avatar
Alchera
Revered One
Posts: 3344
Joined: Mon Aug 11, 2003 12:42 pm
Location: Ballarat Victoria, Australia
Contact:

Post by Alchera »

It's best toupdate the whole net.
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM
e
evildude
Voice
Posts: 24
Joined: Tue Feb 03, 2004 9:13 pm

Post by evildude »

Aww crap, I still have 2 bots using 1.6.15 for ipv6

:( :x :(
W
Wcc
Master
Posts: 278
Joined: Sun Oct 28, 2001 8:00 pm
Location: USA
Contact:

Post by Wcc »

Alot of people seem to be having problems with this. I'll write a patch today for 1.6.17 and post it here.
e
evildude
Voice
Posts: 24
Joined: Tue Feb 03, 2004 9:13 pm

Post by evildude »

You rock dude! I'll be waiting patiently so that I can relink my ipv6 bots.
Thanks a lot.
:P
n
nicks0r

Post by nicks0r »

well i downgraded to 1.6.16 and same problems
any idea where the madness stops?
W
Wcc
Master
Posts: 278
Joined: Sun Oct 28, 2001 8:00 pm
Location: USA
Contact:

Post by Wcc »

Actually, I guess the best solution, if you don't want to/ cant upgrade your whole net, then ive bots +o for the CHANNELS they need to be opped on; not global +o.

The problem is that .17 forces a +o flag to automatically imply the +l user flag (halfop) as well. This uncovered a hidden bug that had been present for a long time, where part of the code see's no difference between botflag +l and userflag +l. It was fixed in 1.6.17, but, the +l being forced for +o bots makes this bug show up on all of the older bots.

Here's what I would do:

chattr all your bots -o and -l
do a .save
set private-globals "l" in your config (that's l as in L, not a one)
give your bots +o for the channel's they need it on

That should fix the problem.
e
evildude
Voice
Posts: 24
Joined: Tue Feb 03, 2004 9:13 pm

Post by evildude »

Umm... :-?
A
AWS
Voice
Posts: 9
Joined: Fri Dec 30, 2005 2:44 pm

Post by AWS »

thanx helped
h
helix
Voice
Posts: 1
Joined: Wed Jan 10, 2007 1:24 pm

Post by helix »

nicks0r wrote:well i downgraded to 1.6.16 and same problems
any idea where the madness stops?
If You downgraded to 1.6.16
remove the l flag from the hub, then the madness stops.
Z
ZubaZ
Voice
Posts: 2
Joined: Thu Oct 25, 2007 7:17 am

Post by ZubaZ »

Yes, removing flags lo from hub solve the issue.
Post Reply