Zugg Software :: View topic

Beginner Joined: 30 Jan 2002 Posts: 20

I'm having some major problems with my triggers in zmud. What seems to be happening, and this is not the case with just this specific trigger (it happens with a multitude of them), is that the trigger is firing once off of the correct line of text, but then fires 2-4 times again off of any line of text afterwards even if it does not match. It is just a simple pattern trigger with no complications that I am aware of. Here is an example of what I'm seeing...

Obvious paths: east, south, northwest.
[^Obvious {paths|exits}-> #VA talkerlist {}
#IF (@script = combat) {#OK}
#VA monscount 0]
GSq1015487187
A wary field goblin begins to advance on you!
The field goblin is still a distance away from you and is closing steadily.
GSq1015487191
parry
[^Obvious {paths|exits}-> #VA talkerlist {}
#IF (@script = combat) {#OK}
#VA monscount 0]

Notice the OBVIOUS PATHS is what it triggers off of first, and it works correctly. However, several lines down, after I input PARRY, it is triggering the same trigger of OBVIOUS PATHS again off of my input. Any help would be appreciated. If anyone needs further explanations or examples of this problem feel free to let me know. Thanks.

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

You need to have a look through your triggers. You AREN'T supposed to see:
[^Obvious {paths|exits}-> #VA talkerlist {}
#IF (@script = combat) {#OK}
#VA monscount 0]

That should be processed by zMUD rather than displayed on the screen. And that means you have made a serious error in your scripting somewhere.

LightBulb
All scripts untested unless otherwise noted

Beginner Joined: 30 Jan 2002 Posts: 20

No, I'm pretty sure that is supposed to be there. I have the "SHOW TRIGGERS" option turned on to help me with my debugging.

GURU Joined: 26 Jul 2001 Posts: 1958 Location: Canada

Odd.

Have you tried to turn the show triggers off and add an

#ADD Debug 1
#ECHO Debug @Debug

kind of deal to your Obvious {paths|exits} trigger?

That way you avoid any trigger on triggers and see the counter go up as it
gets called.

If you get weird results from that, I'd say open up the debugger and step through with
something like:

#SH .
#SH Obvious paths: east, south, northwest.
#SH A wary field goblin begins to advance on you!
#SH The field goblin is still a distance away from you and is closing steadily.
#SH etc

to see what it is doing.

TonDiening
Beta Upgrading to 6.26

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

Do you perhaps have the trigger options set to both Trigger on Newline and Trigger on Prompt?

LightBulb
All scripts untested unless otherwise noted

Beginner Joined: 30 Jan 2002 Posts: 20

I've tried everything...however, I've managed to eliminate the problem (i think so at least). My script relied heavily on #WAIT commands, but I've replaced all of those with #ALARM and it seems to run MUCH better. Thanks for the help.