Yo Jamie! You bombarded my mailbox at my time 08:05:49, Saturday 28-Aug-99:
Howdi there Jamie van den Berge..
>> Executing scripts on Events are really lame, because it's impossible to
>> reliably get the line which triggered the event. GETLASTLINE is the
>> closest I can get, but if another line comes in before the script gets to
>> that line (which happens an awful lot), it misses the line. This badly
>> needs fixing.
> Use %p in the event command, like "/rx MyEventScript %p". The %p token
> will be replaced by the line that triggered the event.
> (The docs REALLY need to be upgraded some day.. hmmm)
One command:
"GETLINE"
It waits for the next line and does em all.
As quoted from the manual:
GETLINE Waits for the next line and parses it into a stem variable.
There is some bugs (or limitations) of the Notify Event. It runs per change
(crazy for scripts!) You will see below. I have a script to autochange to
'lanky' (The script writer should do Parsing of the nicks etc)
EG:
�Notify� Nick lanky is gone.
�Notify� Detected nick lanx ([EMAIL PROTECTED]).
�NICKCHANGE� Changing nick to lanky.
�NICKCHANGE� Changing nick to lanky.
next problem is that once the change is done and notify event isnt triggered
it doesnt pass any info to the script.. Even though lanky is not there.
Notify is only triggered when it displays a change. Not wise.
Or at least make it iptional so you have complete changability.
Catcha..
Paul
--
Member/Programmer for Omniscient International & ACS(K11)
Internet User for 12 Years
<sb>
I like work ... I can sit and watch it for hours.
<sb>
__________________________________________________________
AmIRC Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
