|
Davos Adept
Joined: 30 Jan 2003 Posts: 228 Location: USA
|
Posted: Mon Apr 07, 2003 7:58 pm
Capturing |
#CLASS {Communication}
#TRIGGER {~((%w)~):(*)} {#var cap "%1";#class cap 1}
#TRIGGER {(%w) tells you,} {#T+ cap}
#TRIGGER {You tell} {#T+ cap}
#TRIGGER {~((%w) (%w)~):(*)} {#var cap "%1";#class cap 1}
#TRIGGER {~((%w) (%w) (%w)~):(*)} {#var cap "%1";#class cap 1}
#CLASS 0
#CLASS {Communication|Cap} {disable}
#TRIGGER {*} {#CAPTURE Channels}
#CLASS 0
the trigger that I have marked red doesnt fire
let me give you the MUD output:
(The Hashanite Legion): Nimnoth says, "But basicaly, if the Fontis is full
right now, we don't need to hunt them, right?"
In this instance, it skips the first line and captures the rest of the message, In the other triggers they fire correctly, capturing the first line as well as all other lines, btw
I trigger off the prompt to turn off the class called cap so that it stops capturing, any help?
The Seaworthy |
|
|
|
Davos Adept
Joined: 30 Jan 2003 Posts: 228 Location: USA
|
Posted: Mon Apr 07, 2003 11:31 pm |
Noone has any ideas? *whine* IT WONT WORK
The Seaworthy |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Tue Apr 08, 2003 12:32 am |
It does work. At least, it works with the example given. If it didn't work it wouldn't capture any lines, so it appears to be a speed issue. Processing four wildcards probably requires significant (to the computer) time, and the next line has already arrived before the Cap class is enabled.
Is there some particular reason to limit the channel name in @cap to a single word? If not, you might be able to combine several triggers.
#TR {^~((*)~):} {#VAR cap "%1";#T+ Cap}
LightBulb
Advanced Member |
|
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|