Zugg Software :: View topic - [1.15] Multistate Triggers

Apprentice Joined: 12 Jun 2006 Posts: 106

When the first state is an expression this is the only state ever fired. Everything else is ignored that follows. When the expression isn't the first state it seems to get skipped over until all other states have fired. It then is stuck on that state and doesn't move on from there.

Posted: Tue Nov 14, 2006 8:09 pm

That is true. This has always been true in zMUD too I think. There are some trigger types (like expressions, mxp, gsl) that don't work with multiple states. This will probably be improved sometime in the future now that expression triggers work better than they did in zMUD.

Apprentice Joined: 12 Jun 2006 Posts: 106

It worked in zMUD. These are triggers that I replicated from my zMUD triggers.

Posted: Tue Nov 14, 2006 8:58 pm

Well, yes and no. Expression Triggers in zMUD were really flaky. They didn't really "work" as they were supposed to. They were tested and updated when *any* variable changed, which could cause them to get executed multiple times when you didn't want them too. Expression triggers are completely different in CMUD and only trigger once when a variable that is actually referenced in the trigger changes values.

I'll add this to the to-do list to look into, but there are several changes that need to be made to the trigger system to handle multistate triggers in a more general way, and it will probably have to wait until then. Until then, you'll need to change your script so that the expression trigger enables the other multistate trigger using #T+, or something like that.