Zugg Software :: View topic

Newbie Joined: 17 Mar 2006 Posts: 9

I'm having a bit of a problem with #cond in my healing scripts in Imperian.

Adept Joined: 21 Sep 2005 Posts: 250 Location: Austin, TX

The #COND doesn't go inside the trigger body. It's a separate command of its own, issued after the #TRIG. So the code you've written above won't work. Try something like:

Newbie Joined: 17 Mar 2006 Posts: 9

Hmm.. So in

Adept Joined: 21 Sep 2005 Posts: 250 Location: Austin, TX

Ok...one thing at a time.

No, the #NOOP is simply a way for me to put in a comment. It doesn't do any action. That was a short way of saying, "If you need to do an action immediately upon receiving the 'You quickly eat' message from the MUD, this is the place to put that command."
The #COND goes exactly where I showed it. It's a separate command AFTER the #TR command, and adds a second state to the trigger. To be painfully explicit, there are two lines in my code above. One starts with #TR, the second starts with #COND (try making your browser window as wide as possible to avoid line-wraps inside the code block to see what I mean).
Here's another example, that won't wrap. Get a completely clean window by hitting Esc at the character window, then cut and paste the following two lines into the command-line:

Code:

#TR {trig} {#SAY State 1 fired}
#COND {cond} {#SAY State 2 fired}

The first line creates a trigger on 'trig' with a #say action, and the second ADDS A SECOND STATE to that tigger, which catches 'cond' and also has a #say action. Let me say again - there is only ONE trigger, but it has TWO states.
After entering the above, you can type 'cond' all you want, and nothing will happen, because the trigger is in the first state (waiting for 'trig'). If you type 'trig', you'll get the 'State 1 fired' message, and the trigger will change state. Now, you can type 'trig' all you want, and nothing will happen, because the trigger is in the second state (waiting for 'cond'). When you type 'cond', you'll see the 'State 2 fired' message, and the trigger will return to its orginal state.
This is pretty much what the link I posted said, too, but with a different example.
The code you originally posted looked like you were trying to do a multistate trigger which would (a) catch 'You quickly eat', then (b) wait until you got that status-info-looking-thing, then (c) reset your vars to zero if you had eaten 'orphine'. As posted, your code doesn't work because the syntax is wrong - you don't put the #COND inside the action block of the #TRIG, you put it afterward (like in my example).

If this is still confusing, let's work on the simple 2-state trigger I posted in THIS post, and ask away.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

You'll want to modify the parameters on the second state to ensure that it fires on a prompt and that it fires only if it's the very next line after the eating. As it is coded now, your failsafe will reset your afflictions every time you eat the herb.

Newbie Joined: 17 Mar 2006 Posts: 9

I've updated it so far...