Zugg Software :: View topic

Posted: Mon Dec 11, 2006 6:06 am

Anyone have triggers that in all reality should be functioning, but all the sudden cease to function. All my other triggers appear to be working and it starts to work again if I restart Zmud.

This has happened a few times to I'm wondering what might be causing it and how I can "reset" it without restarting Zmud.

Posted: Mon Dec 11, 2006 9:57 am

There are a couple of possibilities. One is that you've turned off trigger parsing by accident, with a macro or a typo or something. Second is that you've used the #T- command or the #Class command wrongly somewhere.

Posted: Mon Dec 11, 2006 3:06 pm

Are those the only two possibilities? I'm fairly certain I didn't do either.

Posted: Mon Dec 11, 2006 4:29 pm

No, those were just the two that struck me. It could be something I haven't thought of, or a bug :)

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

If other triggers are working, then it's not Trigger Parsing being turned off. But it really depends on the type of trigger you have. For instance, if it's a multi-state trigger then perhaps one of the states fired on the wrong thing and the trigger is waiting for the next pattern to appear.

It could be you accidentally checked one of the trigger options, or you typed something into the pattern by mistake (creating a pattern that will never match anything).

In a select few cases, it might even be command-interaction issues where the trigger itself is firing but the way the different commands used in the trigger code work they don't produce any output at all.

Sometimes it's just a matter of syntax being just wrong enough to produce no output rather than dumping the rest of the script to the game OR the logic of it being messed up (in ZMud it's possible to make the syntax checker happy and still end up with code that doesn't seem to execute because of extra sets of braces).

Finally, ZMud itself or perhaps your settings file is getting corrupted enough to interfere with operation. For instance, not too long ago ZMud suddenly stopped processing multi-state triggers for me. Things that could have easily been done via multi-state triggers had to be converted to pre-multistate separate triggers. Way back in the day, various functions would output weird things in addition to the proper stuff.

Wanderer Joined: 16 Oct 2006 Posts: 62

I had somewhat of the same problems and it was always when I had a trigger in class none that duplicated one of my ACP triggers in a different class. I more or less fixed it by adding my lines to the ZMud script. That was tedious and if I ever import a newer version of ACP I'll need to reinsert the lines. For some reason I still loose the functionality of one now and then but usually I find that there is a conflict somewhere. It is easy to put the trigger words in the find box and select all triggers to find the conflicts. Also, I've tried to msg scripts to my friends in Achaea. One word on that "DON"T" Ive ended up with a mess doing that as mine tries to import classes and vars a second time creating all kinds of conflicts. IMHO it is much better to e-mail the scrips back and forth. Hope this helps.

Posted: Thu Dec 28, 2006 5:17 am

My best theory on it as of right now is to select the "trigger on trigger" option and to put the internals of the trigger in a priority statement. Doing that seems to have fixed the problem. It seems like it is some concurrency thing that is fixed by doing those things.