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.
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.
problems with eggdrop 1.6.7 on bahamut-compilant server
-
oopenglx
Move to a network with RFC complient who replies.
This is not an issue with eggdrop, and never has been.
Eggdrops developers have maintaind RFC complient code, and allways will (fingers crossed). They will doubtfully create a workaround for the problems bahamut caused, as they have to deal with issues they either they have caused, or work on the improved version of eggdrop (which will also, doubtfully have a working around for the fault bahamut IRCD.).
This is not an issue with eggdrop, and never has been.
Eggdrops developers have maintaind RFC complient code, and allways will (fingers crossed). They will doubtfully create a workaround for the problems bahamut caused, as they have to deal with issues they either they have caused, or work on the improved version of eggdrop (which will also, doubtfully have a working around for the fault bahamut IRCD.).
-
aascension
>Going from a 1.4.2 bot to 1.6.7, I've >noticed on a large DALnet chan it's in >that .kickban only kicks the users, >and .+ban won't add the ban in the channel, >just in the bot and the banee gets kicked >over and over if they have an auto-join on >their script. I've kept the same channel >settings in the new 1.6.7 I compiled. net >type is set to 3, etc etc.. What am I >missing that's causing it to not set bans? >Thanks!
Eggdrop 1.6.X won't place bans, if the user is in the ban list, but only kick them
This 'error' or whatever you want to call it
occurs only on DALnet as far as I know, your bots would work fine on efnet though
I've tested out my botnets on efnet and dalnet, and yeah for some reason they f**k up on dal
>Check the config file for the maximum
>number of bans that can be set on a channel >and increase the number from about 20 to >about 50 and see if it helps.
The dal.net ircd, globally (all server links) should allow 100 max bans (MAXBANS=100)
>These connections, allow the user/bot to be >oped, but they can only kick, change the >topic and a few other bits. It also >prevents the user from opping others. I am >unsure, but this may prevent them from >setting modes.
The bots set modes fine, like enforcing certain modes (mode restriction), and banning users that trigger eggdrops default flood protection, I've just had trouble with the .+ban nick!user@host, it will just kick them repeatedly w/o banning, there is definately some bug that prevents them from setting the ban, the only thing that would prevent the bot from setting bans is a full ban list, and yeah my ban lists were empty..
>Thanks for the suggestions/ideas. I set >bans way up to 100. There's only usually 20->30 in the chan, though. DALnet allows 60.
60?
>1.6.7 doesn't seem in my case to want to >talk to chanserv to set or unset bans when >they time out. I did notice in eggdrop.h >the handle length was only 9 and I changed >it to 32, and re-compiled, but that didn't >fix it. Any other ideas would be welcome!
chanserv can't assume how to "set" or "unset"
bans unless you have a tcl which can do so,
but if you meant when bans expire the bot doesn't remove the bans, this has happened to me as well :/ what would changing the handle length do to make the bot set bans?
Hopefully, someone can figure out what's wrong an release a patch/fix for those of us running bots on dal.net (bahamut)
.ascension.
Eggdrop 1.6.X won't place bans, if the user is in the ban list, but only kick them
This 'error' or whatever you want to call it
occurs only on DALnet as far as I know, your bots would work fine on efnet though
I've tested out my botnets on efnet and dalnet, and yeah for some reason they f**k up on dal>Check the config file for the maximum
>number of bans that can be set on a channel >and increase the number from about 20 to >about 50 and see if it helps.
The dal.net ircd, globally (all server links) should allow 100 max bans (MAXBANS=100)
>These connections, allow the user/bot to be >oped, but they can only kick, change the >topic and a few other bits. It also >prevents the user from opping others. I am >unsure, but this may prevent them from >setting modes.
The bots set modes fine, like enforcing certain modes (mode restriction), and banning users that trigger eggdrops default flood protection, I've just had trouble with the .+ban nick!user@host, it will just kick them repeatedly w/o banning, there is definately some bug that prevents them from setting the ban, the only thing that would prevent the bot from setting bans is a full ban list, and yeah my ban lists were empty..
>Thanks for the suggestions/ideas. I set >bans way up to 100. There's only usually 20->30 in the chan, though. DALnet allows 60.
60?
>1.6.7 doesn't seem in my case to want to >talk to chanserv to set or unset bans when >they time out. I did notice in eggdrop.h >the handle length was only 9 and I changed >it to 32, and re-compiled, but that didn't >fix it. Any other ideas would be welcome!
chanserv can't assume how to "set" or "unset"
bans unless you have a tcl which can do so,
but if you meant when bans expire the bot doesn't remove the bans, this has happened to me as well :/ what would changing the handle length do to make the bot set bans?
Hopefully, someone can figure out what's wrong an release a patch/fix for those of us running bots on dal.net (bahamut)
.ascension.