Trigger's PME: HighScore < CurrentVal I am trying to track the highest card currently in play. I have two global properties which are set with initial values of zero. When a new card is played, a GKC on the main map fires the card's trigger to read the value of a dynamic property associated with the card and update CurrentVal with that value. Another trigger also fires from the GKC which checks if HighScore < CurrentVal, and if so send keystrokes to update HighScore with the CurrentVal.
The second trigger is firing no matter what the value of HighScore and CurrentVal are, which means that every time a card is played on the board HighScore is set to CurrentVal (the current card's value) even if a higher card has already been played. If I can't compare two global properties, is there another way to track the current highest value in play? Thanks! -Dale Timothy Mccarron wrote: > What is the PME of your Trigger and GKC. sounds like you are trying to > compare the properties against each other which you cant do, as opposed to > evaluating each property independent of one another to be true or false > > > ----- Original Message ---- > From: Hoalun <[EMAIL PROTECTED]> > To: [email protected] > Sent: Thursday, October 25, 2007 1:17:34 PM > Subject: Re: [vassalengine] Global property reference > > I have noticed this same behavior. I created a trigger to fire when one > global property has a higher value than another (HighScore > > CurrentVal), but the trigger fires no matter what the value of the two > properties are. > > -Dale > > The Sutherlands wrote: > >> Good day all, >> >> Trying to set up a trigger that compares a layer to a global property >> but cant seem to get it to work. It seems to fire the trigger regardless of >> what the layer level actually is. >> >> Trigger; Random_Level >= $ZAL$ >> >> The global property is in the module. Tried moving it to the map but >> nothing seemed to change. >> >> I have tried it without the $s but get the same result. Am I referencing >> the global property ZAL incorrectly? This worked in VASSAL version 2.8 but >> not in 3.0. >> >> Would greatly appreciate any help as this is pretty critical to updating the >> ATZ module to version 3.0. >> >> Charles >> >> >> [Non-text portions of this message have been removed] >> >> >> >> > > > > > [Non-text portions of this message have been removed] > > >
