Hey guys,
I’m fairly new here. I’ve been playing around with Vassal for about 20 hours so far, and I’m already working out the mechanics to build my own module. In that spirit I’d like to make a request for a feature.
Basically, I have several units, all of which use the same data, so I’m building a property sheet in a prototype. When I build each unit’s counter I’d like to be able to just use markers to define the behaviour in the property sheet.
I’ve been able to have markers or dynamic properties alter the behaviour of labels, but I’d like to be able to have that control over the behaviour of a property sheet as well. Even if it can’t be done to a prototype, setting initial values to a property sheet everytime you load a module is going to be painful.
If you apply the Property Sheet trait directly to the piece, you can open the property sheet by right-clicking the piece graphic when editing the piece and set your starting values. Those values will remain in place at game time.
I realized that. The problem with that is everytime I alter the property sheet in the unit stats, it resets in the game.
However, if the Property Sheet is defined within a prototype, then these changes
will only ‘stick’ in the prototype and affect all pieces. Changes to an individual
unit will be lost as you have seen.
To allow this to work, you have to define the Property Sheet directly in each
individual unit, not in a prototype.
B.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Of this I am aware. I had done this, but as I said - making changes to the property sheet when editing the module resets the properties in the game even when attached to the final counter (not the prototype). It’s livable, but I’d still love to see the property sheet a bit more resilient. Further, I’d love to see the property sheet more accessible, or if it is accessible, some documentation to see how.
Suppose the property sheet has a property called HP. I’d love for a DP to be able to change the HP’s maximum when the key is fired.
That is either a Vassal or Module bug. Please post a link to the module
and the name of the counter causing problens.
Good idea. I have added
RFE [2725945] Allow Property Sheet values to be changed programtically
B.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Ah, Wonderful. 
.
As requested. Here is my module, bear in mind, Its still in deep experimentation.
robinomicon.com/vault/Rob2Mod.zip
The counter giving me issues is called “Oberth”
Works as expected:
- Opened the Frigates panel
- Double clicked on the Oberth counter
- Right-clicked on the graphic at the top of the dalog and selected Properties
- Entered some values in the fields, clicked Apply, then close
- Saved the module and quit vassal
- Play the module
- Start a new game
- Pull an Oberth counter onto the map
- right-click on it and select properties
- I see the values I set in step 4
Am I misunderstanding what you expect to see? Please describe in more detail.
Rgds,
B.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
No, that happens right. The problem is when I try to edit the property sheet in the module editor again.
Edit the module, add a property to the property sheet. Now go to the counter, right-click and open up the properties. All the values have reset.
Again, its workable, but just a small glitch, I think.