Sorry but I'm not prepared to upload my complete bot, not that it would necessarily do you any good anyway. I very much doubt if this issue has anything to do with your bot version. If you still believe this to be the case simply compile/install the current version.
I just thought of a possibility. Are you using an IRC client that throws in a spurious space character after typing in part of an onchan nick and using a predefined key (usually tab) for autocompletion? This used to occur with XChat, though I don't know if current versions still do that.
However, it is possible that the script author has included the following otherwise seemingly improper code segment to get rid of any such character :-
Code: Select all
proc pub_dotalkz {nick uhost hand chan rest} {
set str [lrange $rest 0 end]
The variable 'rest' is not a list and shouldn't normally be treated as one. Even if it was a list, [lrange $rest 0 end] would return all of it, which sort makes it strange that there would be a need to additionally define 'str'.
There are other parts of the script that I think look rather ugly. For example :-
Code: Select all
if {$nick == $botnick} {
return 0
}
if {$str == ""} {
putchan $chan "$nick: What? ×åãî íàäî ?"
return 0
}
Would look rather better as :-
Code: Select all
if {[isbotnick $nick]} {
return 0
}
if {[string length $str] == 0} {
putchan $chan "$nick: What? ×åãî íàäî ?"
return 0
}
Not that this would excuse the cross-over of string and list manipulation functions, which I have maintained by using 'string length' on the list variable 'str' as returned from the 'lrange' statement.
I'm not saying these corrections and several others in the script would resolve your problem but I am saying that I wouldn't use this script.