egghelp/eggheads community

bot2: bind bot - "accept" procbot proc procbot {bot command text} { global mychanjoin set nick [lindex [split $text] 0] set jointime [lindex [split $text] 1] set [getchanjoin $nick #channel] jointime } I think the point of this code was to use the var mychanjoin, not [getchanjoin]. So it ...

JOE,

Those lines of code you posted work for me.

Also, to add color to the channel name, you'll have to do like \00304B\00305e\00306l etc.

Could you be a little more vague? When you do .channel, I really hope you don't just see "N". And no, N is not the same as n, and it's not a +m either. Hopefully you see something like this: <stdarg> .channel <martian> [19:36] #stdarg# (#trivia) channel <martian> Channel #trivia, 34 member...

Simple then, the bot doesn't see you, or you don't have +m. Make sure your host is correct, and that you see your handle on .channel output. Make sure the user you're identified as has +m. You'll know it's working when ".av blahblah" makes the bot send you the notice I indicated above.

What about the other test?

When you are in the channel, and on the partyline you type .channel, does the bot see you as the right user? Do you have +m?

When you type ".av dragon" does the bot send you a notice that says "Usage: .avjoin on|off" ??

Try \ instead of /

Hard to tell if it will work with the horrible formatting, and I didn't test it... bind pub * !start join:story proc join:story {nick uhost hand chan rest} { global story_timers set story "story.txt" if {![info exists story_timers($story)]} { slowmsg $story } else { puthelp "privmsg $...

Does it happen when the bot rejoins the channel?

That's the problem then -- you are running it wrong. It expects arguments and you are giving it none. Try:

.tcl identify_notc somenick uhost hand text dest

When do you get the error? Where do you see the error?

You also have to make sure that the files are closed. If there's a return statement before the close, like inside an if or a loop, the file won't be closed. Same goes with sockets, which can be more problematic because they may be asynchronous, so tracking down the closing bit and making sure it's a...

You'd be better off using tclsh to do the testing. Not all regular expression parsers are the same.

Depends if you're using { } or " " to enclose the regular expression. If { }, then \\ is right. Otherwise, you actually need \\\\.

Yup. Try a different text editor. Looks like you used wordpad or word or something.