ON ^1:QUIT: {
echo $chan 10.:11 $+ $time $+ 10:. 2*14 $nick has quited with the reason: ( $+ $1- $+ )
haltdef
}
It's echo'ing in my status, but it needs to echo in the chan where i normaly see:
* $nick has quited IRC: ($reason)
....
You need to loop through all the channels you and $nick have in common, since $chan is null in on QUIT events.
On QUIT isn't a channel based event. When someone quits, they 'part' all channels. So you have to use:
on ^*:quit: {
var %x = $comchan($nick,0), %y = 0
while (%y < %x) {
inc %y
echo $comchan($nick,%y) * $nick has quit.
}
haltdef
}
Untested, but thats the basic idea.
Would echo $target work? since she wants the echo in the window where the it would normally appear.
No.
There is NO target in a on quit event. All you're given is $nick, $1-, $server, $serverip, and $cid (and other identifiers excluding $target, $chan).
Click here Here is what you're looking for
ON ^*:QUIT:{
var %x = $comchan($nick,0)
while (%x > 0) {
echo $comchan($nick,%x) 10.:11 $+ $time $+ 10:. 2*14 $nick has quit ( $+ $1- $+ )
dec %x
}
haltdef
}Basically what Kardafol said, but formatted, corrected the error (quited isn't an english word :)) and one less variable.
(quited isn't an english word :))
yes, because it's quitted
"quitted" isn't correct either.
It's just quit.
The past and future tense is the same.
I quit my job. (past)
I will quit my job. (future)
Quitted is apparently correct as well if you speak Commonwealth English
But there aren't a lot of people that use it :p