Back when I used egg1.4.4 and netbots 3.(?), I used wingate2.tcl with an added kick command, inserted after each of the newchanban lines:
newchanban $chan *!*@$host $botnick "Proxied connections not permitted." $wingate(ban)
putserv "kick $chan $nick :kick message"
This meant I could keep my bots set at
-enforcebans.
Worked great.
But when I recently tried that same modified tcl in my egg1.6.6/netbots4.05, the results were not so great. When a proxy enters a listed channel, there is a flurry of bans and kicks, including ban removals by the linked netbots.
Part of the prob is that I could not get the ban to go to the channel before the kick. Putting a utimer in front of the kick command didn't work. But I also have not been able to figure out why the linked bots were immediately removing the ban. If remove the kick lines, everything is fine. If I use .+ban or .tcl putserv "mode etc" from the partyline, everything is fine. If I unlink the bot with the wingate2.tcl, then the tcl works fine.
For now, I have removed the newbanchan lines and replaced them with:
putserv "mode $chan +b *!*@$host"
putserv "kick $chan $nick :kick message."
This bans then kicks 1080/wingate proxies and allows the bot to still be linked and share files (its a leaf bot). The other bots do not immediately remove the ban.
Anyone got any ideas as to why the other linked bots were removing the ban?
Thanks