This is more of a general issue I am having with VASSAL. I have been noticing some very quirky behaviour in VASSAL 3.0 when making changes to a trait/function and then trying to visually check/see the effect the changes have on the mod function.
Typically I will have a saved game open with a few counters on it when editing my mod.
Once I edit and change something in the mod, I return to the game screen (hoping the change is now active) and test out the change either on counters already on the map or by freshly drawing them from the palette.
There have been times where I KNOW/THINK I have done the right thing as far as editing the mod to get what I want but when I go the game/map screen, it’s like the modification is NOT working/in effect. This leads to lots of wasted time wondering what the heck is wrong. Sometimes in frustration I just shut down VASSAL and (sometimes after a few days of calming down) return VASSAL to work on my mod only to NOW find the changes working as they should.
What confuses things even more is that from what I understand, if you load a pre-defined map with counters already on it, there are at least SOME features/functions of the counters that WILL NEVER update by themselves even though the mod itself has been updated.
eg. the position of the 'Mark as moved" graphic.
I think I really need to understand why this is happening and know exactly what kind of changes are more likely NOT to work immediately after editing them in the mod. It will save me a lot of time/frustration.
In general, editing and changing a module while a game is in progress is not supported, the results are unspecified. It might work, it might not.
Specific things that I know do not work:
If you change a unit or prototype definition, this will NEVER EVER have any effect whatsoever on any unit that already exists on the Map. This is what saved game updaters are for.
There is some caching of definitions involved, so if you pull a counter off a palette, then change the definition of prototypes it contains, then pull a new counter, you probably won’t see any change. You can try pulling a different counter that uses the same prototype and this will usually let you see the changes.