Zugg Software :: View topic

Novice Joined: 04 Jun 2002 Posts: 31

This example is oversimplified just to make it easier to understand, but here's what I want to do.

I'm trying to create a trigger that when activated does nothing until it recieves the next line. If the next line is the prompt, I want it to reset a variable.

Here's an Example:
State 0:
Pattern: You slap your thigh, laughing hysterically.
Value:
State 1:
Pattern: (%d)h, (%d)m (%w)-
Value: #var test 0

I used within 1 and looplines 1 and both don't really work right. The problem is if I type any command on the prompt that I want the 1 state to recognize it won't recognize it. On the otherhand, if I do nothing on that prompt, the trigger seems to work fine. But, that's not really realistic, I need to be able to enter commands and not have to wait for text from the mud to advance the mud.

Just to clarify what works and doesn't I'll give a couple of examples:

This example would work:

Enchanter Joined: 10 Oct 2000 Posts: 698

Quick reply before heading to work, untested.
State 1:
Pattern: ^(%d)h, (%d)m (%w)-*

Apprentice Joined: 28 Sep 2001 Posts: 103 Location: USA

If you want the second state to fire on both

2687h, 4535m cexkdb-
and
2687h, 4535m cexkdb-glance

use a within lines 1 and set it to fire on both prompt and newline.

Beginner Joined: 23 Mar 2003 Posts: 28

I don't understand why what comes after the prompt will matter
unless you use the end line symbol, I have a prompt trigger like
that and it works fine without any wildcard after the dash.