Zugg Software :: View topic

Newbie Joined: 15 Mar 2006 Posts: 9

Hi.

Freely confessed, I'm a coding idiot, and I could use some help with this.

What I'm trying to do is set up a series of triggers to heal an affliction IF I am currently able to eat the healing crystal.

I'm using the dialogue boxes rather than the command line to set these things up, so I'll use the term 'Pattern' to show what text is used to fire the trigger and the term 'Value' to designate the actions I'm asking it to do.

The trigger to toggle the affliction variable to on is:

GURU Joined: 28 Sep 2000 Posts: 434 Location: USA

---
Pattern: * causes you to fume with {his|her} off color references to

Value: #var taunt 1
---
Pattern: @taunt

Value:
#IF (!@curativebalance) {
eat maroon
#WA 500 }
---
Expression triggers fire when the expression evaluates to true. Since 1 is true, and 0 is false, all you need is @taunt as the pattern. You should also reconsider the use of #WAIT.

Timers, Alarms, and the WAIT command.

Posted: Wed Mar 15, 2006 6:23 pm

The problem is you can not trigger on a variable condition, you trigger on MUD text received. You may consider adding it to your prompt trigger (another trigger that matches on the prompt but is only active while you're fighting.)

As for you other trigger,

Posted: Wed Mar 15, 2006 6:23 pm

Carabas, you beat me to it... with color to boot.

Newbie Joined: 15 Mar 2006 Posts: 9

Thanks a lot Carabas, that did solve the problem...

Unfortunately, with:

Pattern: @taunt

The trigger loops infinitely, regardless of the value of taunt.

GURU Joined: 28 Sep 2000 Posts: 434 Location: USA

Yeah, I can see why you may be experiencing a loop. You may need to add another check variable or perhaps change the value of @taunt to zero more quickly.

If you do not need @taunt for any other reason, then I don't see why this won't work just fine.

#IF (!@curativebalance) {
#VAR taunt 0
eat maroon}

The @taunt trigger should fire (if @taunt is set to 1) until @curativebalance is no longer true itself. At that point @taunt will immediately be set to 0 (false), eat maroon will be sent to the MUD, and the trigger will not fire again until @taunt is set to 1 (true) again.

If eat maroon could fail, you could add another trigger that would set @taunt back to 1.

#TRIGGER {eat maroon failed} {#VAR taunt 1}

Then the @taunt would fire again.

Newbie Joined: 15 Mar 2006 Posts: 9

Having tested the problem remains:

Variable name: Taunt
Value: 0

The trigger is still firing. Every half second.

So what I'm thinking is...

Using:

Pattern :@taunt

The trigger fires regardless of the value of taunt, and it fires for as long as the variable simply exists.

It doesn't seem to matter if @taunt is 1 or 0. I've tried turning off triggers and manually setting @taunt to 0 and it still fires when I turn on triggers again.

If it helps, I'm using version 7.21

Apprentice Joined: 29 Jun 2001 Posts: 198 Location: USA

GURU Joined: 28 Sep 2000 Posts: 434 Location: USA

Make certain that you do not have any other variables of the same name in any other classes. I've tested this on my end, and the trigger does not fire if the variable is set to zero.

Posted: Thu Mar 16, 2006 7:07 pm

First off... setting the pattern to @Taunt will trigger on what ever value @Taunt currently contains... i.e. if it's set to 1 it will fire whenever 1 occurs and likewise for 0.

Try this.

GURU Joined: 28 Sep 2000 Posts: 434 Location: USA

GURU Joined: 28 Sep 2000 Posts: 434 Location: USA

Ranaven, also make sure the the trigger type for the @taunt trigger is set to Expression. If it is set to Pattern, then it will fire when ever a 1 or 0 is output from the MUD (or echoed to the screen), just as Tech suggested it would.

Posted: Thu Mar 16, 2006 8:29 pm

Thanks for the correction Carabas... i didn't have my trigger type set to expression. I see I am still a sophomore when it comes to zMUD. But I'll start using it now. Very Happy

GURU Joined: 28 Sep 2000 Posts: 434 Location: USA

Not a problem at all. I think Expression triggers are one of those seldomly used features that tend to confuse people. I sometimes think of them as if-then statements without the else. Wink

Newbie Joined: 15 Mar 2006 Posts: 9

Carabas, thou art a saviour.

That was the problem right there, it wasn't set to expression type.

Thanks a lot, and you too Tech.

Problem solved.