Zugg Software :: View topic - Problem with a trigger that no longer works

Apprentice Joined: 20 Jul 2001 Posts: 127 Location: USA

I have kept up with the beta upgrades that have been introduced recently. I have a problem with one of my triggers tho. It worked ok in 6.16, but doesn't seem to work in 6.22 ... trigger goes as follows

PATTERN: (%w) tells you:

ACTION: #CAP Tells
#T+ {Tells}
#WAIT 1500
#T- {Tells}

in the Tells class is another trigger that looks like this

PATTERN: ^ (5 spaces)

ACTION: #CAP Tells

these two triggers would capture multilined tells without a hitch. Now, it only captures the first. Seems the mud output is not processed until after the #WAIT command. How do I fix this?

I know this has been answered before, so I'm sorry for asking the same question, but I didn't have the problem before, so I didn't pay attention. Thanks for your help :)

Posted: Wed Nov 07, 2001 9:47 pm

It's a known bug that #WAIT halts trigger processing when used in a trigger/alias itself. You can use #ALARM instead of #WAIT. I would look something like:

ACTION: #CAP Tells
#T+ {Tells}
#ALARM +1 {#T- {Tells}}

Acaila