Tcl error

z_one · Post by **z_one** » Fri Jul 25, 2003 4:38 pm

Hi,

I restarted my bot and here's what I got:

Tcl error [sl_nkflood]: illegal channel: *

The bot is running normally though (I am using netbots v4.05).

Post by **Sir_Fz** » Fri Jul 25, 2003 5:39 pm

the error describes itself. u probably set some variable to "*" while it shouldn't be that way.

z_one · Post by **z_one** » Thu Jul 31, 2003 2:31 pm

Yes maybe, but I didn't set that variable.
It's a netbots variable.
Perhaps Slennox can help.

Post by **slennox** » Thu Jul 31, 2003 5:26 pm

It looks like eggdrop might be calling sl_nkflood with the chan argument set to "*". I did a basic search of sentinel.tcl, and it doesn't call this proc itself, so it has to be the bind.

Assuming that's the problem, we'd need to find out why your bot is triggering the nick bind with the chan argument given as "*".

What version of eggdrop is it?

z_one · Post by **z_one** » Thu Aug 07, 2003 1:54 pm

Hi and sorry for the late reply.
I am using eggdrop 1.6.15

Post by **slennox** » Thu Aug 07, 2003 5:31 pm

Can you reproduce it? If so then we might be able modify the proc to catch whatever's causing it.

z_one · Post by **z_one** » Fri Aug 08, 2003 10:22 am

Ok, I'll try to ... I'll get back to you as soon as I have more details.
I'll be basically checking for errors when a nick change occurs on the channel.

Post by **user** » Fri Aug 08, 2003 11:04 am

doc/UPDATES1.6 (since 1.6.14):

bind NICK now gets triggered even if the nickname isn't found in any channels (i.e. when the bot's nickname changes before it joins channels)

z_one · Post by **z_one** » Sun Aug 10, 2003 11:49 am

Hi,

I assume you're talking about the eggdrop's own nick being changed.
But the error occurs even when the bot has been sitting on the channel for days (and it hasn't changed its own nick).

Post by **user** » Mon Aug 11, 2003 3:29 am

z_one wrote:I assume you're talking about the eggdrop's own nick being changed.
But the error occurs even when the bot has been sitting on the channel for days (and it hasn't changed its own nick).

Some ircds get a little confused some times and display the quits of people that have been to a channel you're on, even if they're not there at the time they're quitting. I think I've seen this happen with nick changes too.

z_one · Post by **z_one** » Mon Aug 11, 2003 4:02 am

I couldn't agree more.
I was always puzzled to see the message nick has quit even when that nick was not on any channel I was on at the time of the message.
Thanks for clarifying that point.

Post by **Sir_Fz** » Tue Aug 12, 2003 7:21 am

Edit:never mind.

Post by **slennox** » Tue Aug 12, 2003 8:58 pm

I'm a bit preoccupied at the moment (switching to a new OS) so I don't have time to release a new version, but here's a temporary fix:

Code: Select all

proc sl_nkflood {nick uhost hand chan newnick} {
  global botnet-nick botnick sl_ban sl_banmax sl_flooded sl_globalban sl_locked sl_nickkick sl_nkbanhost sl_nkflood sl_nkflooding sl_nkqueue
  if {![validchan $chan]} {return 0}
  set chan [string tolower $chan]

The third line (the validchan check) is the one you need to add. This is based on 4.09 but I'm pretty sure it should be fine for 4.05 and the standalone 2.70 as well.

Remember that you don't need my permission to fix it (I'll replace my poor excuse for a software licence with the GPL to make this more obvious)