Hi David, I have tracked down the problem. It is actually a bug in the Movement Trail trait and only occurs when the Movement Trail trait is defined after the Mark When Moved trait!
I have booked in a fix, but the simple workaround for you is to just reverse the order of your Movement Trail and Mark When Moved traits in your prototype definition. Regards, Brent. *********** REPLY SEPARATOR *********** On 27/12/2006 at 9:52 PM Aradiel wrote: Hello again, I pushed my tests one step further: I removed all the features specific to late version of Vassal and tested this new mod (http://aradiel.free.fr/vassal file named 'Moves 2.0') with all version from 2.0 to 2.9 using the webstart version available there (http://www.vassalengine.org/community/index.php?option=com_static&dir=downloads&page=index.html&Itemid=26) And guess what? It works 'as advertised' only with version 2.1... v2.0, and v2.2 and above don't update correctly the Moved property of a game piece. Or at least, if one is to use this property in a trigger or a text label, the value returned is not what it's supposed to be. But using v2.1, it work perfectly. It's as if Vassal use another property to track movement and this 'old' Moved property is no longer updated but still present and described in the doc file. I guess I'll have to report a bug on Sourceforge... > Hello, > > I need to be able to apply a global key command only to units that moved. > From > what I read in the doc, there is a boolean property named "Moved" for each > unit > on the board that indicates the moved status of a units (details in the "Mark > when moved" trait html doc file). I tried to use this property in a trigger > and > in a global command but it did not work. I thus devised a mini mod dedicated > to > this property testing. You'll find it here: http://aradiel.free.fr/vassal The > mod is named "Moved". You find in there a map with all needed options > activated > (Mark pieces that moved=always in the main map options, a mark when moved > trait > in the unit prototype). I added a text label showing the content of the Moved > Property for the units (a very useful way to 'debug' faulty triggers and > commands in Vassal when you can't find why your mod does not behave as > expected) > > Try as I may, the Moved property of pieces on the board is always evaluated > to > false, even if Vassal does correctly tag the units as moved... > > Any ideas? > > David > ____________________________________________________________ Brent Easton Analyst/Programmer University of Western Sydney Email: [EMAIL PROTECTED] [Non-text portions of this message have been removed]
