Zugg Software :: View topic

Beginner Joined: 23 May 2004 Posts: 14

I don't know what it is, maybe it's just my bad luck, or something, but I've been trying to work with "Within Lines" and it hasn't been working correctly. Let me explain the situation.
For starters, I want to match a trigger such as this.

^You eat a ginseng root.$

Now, the trigger I want to match ONLY if it immediently follows it, is my prompt, such as this:

^H: (%d) M: (%d)

However, it seems to match not only if it's immediently after, but also if it's within 2 lines of the "You eat a ginseng root."
So, for instance, when I get..

You eat a ginseng root.
Your stomach becalms itself.
H: 3038 M: 3740 B:100%

It finds it to be true, and executes the commands.

I've even tried using 0 lines, but that doesn't work at all.
Thanks for your help.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

I can't duplicate this. Please post the scripts which are causing difficulty.

Beginner Joined: 23 May 2004 Posts: 14

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

I can't reproduce this. I get correct usage

Using

#TR {^TRIG$} {}
#TR {COND} {#SAY Within 1}
#SAT %cr //newline
#SAY TRIG;#Say COND
output=withing 1
#SAY %cr
#SAY TRIG;#SAY BLAH;#SAY COND
no trigger output

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

Okay, next post the script of 'callherb'.

What I'm looking for is what makes you think that the #COND fired when it shouldn't have. So far all I see is several variables set to 0 and a second use of 'callherb' which is probably an alias. Since the variables could easily already be 0, it's unlikely that their values would make you think the #COND has fired so it must be whatever's in the alias.

Then again, you might misunderstand the concept of multistate triggers. The first trigger state fires based on the first pattern, without regard to what the next line is. If you want the entire trigger to depend on getting both lines together, you need to move all the commands to the second state.