I have done an update to v1.6.15 and the eggdrop is now kicking everybody with the same IP on the channel on "newchanban"
In previous versions it was so that only the one person was kicked after that IP was banned.
Also it's kicking channel ops.
I have the channel modes "-enforcebans +dynamicbans +userbans +dontkickops"
The "-enforcebans +dynamicbans +userbans +dontkickops" modes applies only when dealing with it's own punishments like flud or revenge. You should edit that script and make it not ban people you don't want. You have made it place bans on *!*@host so it's kinda doing what you have put it to do. Make an ident@host ban or something similar if you don't want all people with the same IP to be banned and kicked off the channel. Also, instead of doing two "string tolower"'s just do that "string match" with -nocase.
Once the game is over, the king and the pawn go back in the same box.
changing the banmask isn't a solution because banning on ident/nick isn't effectiv enough for my efforts.
And as I said the same script didn't has any problems with an older eggdrop version.
The eggdrop is doing exactly what you put it to do and it dosen't have AI to decide by itself what actions should be taken in case of whatever so here the TCL scripts jump in. In case of something a tcl script is telling eggdrop what to do. You say you don't want it to ban all people that match the same IP but you want it to place bans on *!*@host this matching all people with the same mask/ip.. decide already.
Once the game is over, the king and the pawn go back in the same box.
caesar, I never said that I don't want to ban all people with the same *!*@host but I said that in case of banning "*!*@host" the eggdrop shouldn't kick all people that are currently in the channel with *!*@host.
It should kick only the one who used the bad word by banning that IP at once.
I can only repeat myself that earlier version of eggdrop handled it as I'm saying.
The conf files are the same and downgrading is nearly impossible because of gcc versions.
I asked here because I thought that anybody is knowing more about changes done in the new eggdrop version or maybe someone could has any experience in this matter.
the .newchanban with an ip is not so correctly to use because for the eggdrop all the person that match that will be banned. You have to use a more specific flag.
One of my bots actually monitors a channel for certain offensive words (done because I have a number of Muslim visitors). I have a lot of users that also use cyber cafes; matching IP's. The script uses $nick!$uhost to set a ban for the user that committed the offence without affecting any others.
With *!*@host the bot is doing exactly as requested, banning all matching hosts.
One could also add his AOps/SOps as users in the bot and have the script ignore those with the appropriate matching flag(s):
if {[matchattr $hand flag]} { return 0 }
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM