Zugg Software :: View topic

Posted: Sun Feb 29, 2004 10:18 am

I also had a trigger problem since i upgraded to version 7.02. I noticed elsewhere on the forum that these may be cured by upgrading to version 7.03. I have carried out the upgrade but i am still having problems.

The trouble i am having is proving difficult to trace as the script uses various triggers, scripts and variables. Unfortunatley the whole thing was inherited from a friend and he is not available to help resolve it so some help from you would be nice.

This is one part of the whole thing and i must confess i do not fully understand what the trigger pattern is doing so a simple explanation of it would be useful.

#TRIGGER {%e[37m&{monster} is &{status}.} {#if (%ismember( @status, @badcons) != 0) {movenext} {#if (@status = "in top shape") {#if (@playerdetect == 0) {bs monster} {#if (@playerdetect == 1) {playerdetect=0;movenext}}}}} "script" {color}

The trigger actually detects the status of the monster and if its injured or there is another player in the room it moves on to the next room that has a monster in it. The bit that i'm confused with is the bit in the pattern "[37m" and the "!" after the @badcons variable.

Thanks
Bob

SubAdmin Joined: 18 Nov 2001 Posts: 5182

The "%e[37m" in the trigger pattern is an ANSI color code. This means that the entire trigger is looking to match that specific color.

The use of "!" you mentioned indicates the operation of the expression is 'not equals'. For more on operators check the Expressions page in the Reference section of the help.