egghelp/eggheads community

bind/proc sections per channel?

2003-05-02T10:42:26-04:00

My question is: Is this valid? Can I do this?

Not unless you do the channel check inside the procs like ppslim told you to.
Checking a global variable at compile time (like you did in your code example) won't do you any good.

Statistics: Posted by user — Fri May 02, 2003 10:42 am

bind/proc sections per channel?

2003-05-02T10:32:09-04:00

That is exactly what I want. I want to set up different triggers (or maybe even the same triggers) on different channels.

My question is: Is this valid? Can I do this?

Statistics: Posted by Guest — Fri May 02, 2003 10:32 am

bind/proc sections per channel?

2003-05-01T17:58:31-04:00

Your above example creates two seperate triggers.

You simply check inside the proc which channel it is.

Statistics: Posted by ppslim — Thu May 01, 2003 5:58 pm

bind/proc sections per channel?

2003-05-01T16:40:38-04:00

Hi there,

At this moment I ahve set up 1 single bot that sits in three different channels. I want it to respond to public commands in all three channels.

Code:

bind pub - !cmd cmd  proc cmd {nick host handle chan text} {  if {$chan == "#"} {            puthelp "PRIVMSG $chan : this is the output on #chan1"    }  if {$chan == "#chan2"} {    puthelp "PRIVMSG $chan : And this is the output on #chan2"    }  }

My question is: Can I split a script in more sections, where each section describes all the binds and procs for it's own channel? Something like:

Code:

if {$chan == "#chan1"} {          bind pub - !Samplecommand1 Samplecommand1   proc Samplecommand1 {nick host handle chan text} {    puthelp "PRIVMSG $chan : this is the output on #chan1"    }  }if {$chan == "#chan2"} {  bind pub - !AnotherCommand AnotherCommand  proc AnotherCommand {nick host handle chan text} {    puthelp "PRIVMSG $chan : And this is the output on #chan2"    }  }

Statistics: Posted by Guest — Thu May 01, 2003 4:40 pm