Two-sided game piece needs its own layers (Up Front campaign integration)

[cholmcc]

@DiploGuy

However I need the stats: Morale, KIA and Rank (SSG) to show up only on the rallied side (color side). And the Panic, KIA and Rank to show up only on the pinned side (b/w side).

The game pieces are structured with the “good” (rallied) side being the Basic Piece trait. The “bad” (pinned) side is a layer trait
…
I would like to do this without restructuring how the unit pieces were made. Is there a way?

Perhaps a way to do this is to use DynamicPropertyTraits and LabelTraits. E.g.,

• Layer

  Images = [Backside]
  Name = Step
  ...
  

• Morale property

  Actions = [[Increase Moralse,Some-Key,INCREMENT,{1}],
             [Decrease Morale,Shift-Some-Key,INCREMENT,{-1}],
  Name = Morale
  Numeric = True
  Min = 0
  Max = 10
  

• Label display

  Label = {Step > 0 ? "Morale: "+Morale : ""}
  ...
  

The state of DynamicPropertyTraits should be written in saves, so they will come up correctly when re-loading the save.

These traits should most likely be done in a Prototype so that it can be reused across pieces.

@DiploGuy

The other element to the campaign system is a roster sheet to keep track of the soldiers’ performance in the battles they face. In the game it’s basically a spreadsheet to record results on. I found the spreadsheet trait and attached that to a basic piece and formatted the spreadsheet to work. However in testing it I found out that while the spreadsheet retains info put in it by the module creator it doesn’t for the player. So if after a game they enter the stats in for 6 guys, save the game and close it when they load it again what they entered is gone. Any thoughts on this?

The TableInfo (spreadsheet) trait is a bit tricky because - as far as I can tell from the code - user edits are only stored in the GUI element - not the trait itself. That means user-edits will not persist across sessions.

I think you’re better of with DynamicPropertyTraits for this too. The state of those are saved for sure. For example

• Battles won

  Actions = [Set battles won,SomeKey,PROMPT,{"Please enter # of battles won (was "+BattlesWon+")"]
  Name = BattlesWon
  Numeric = True
  Min = 0
  Max = 1000
  

This has the added benefit that you can use these properties (e.g. BattlesWon) elsewhere in the piece properties. For example, if more than 10 net battles have been won by a piece, then that piece earns a veteran status and gets an additional combat factor bonus

• Battles won
  • TriggerTrait to set it (similar for BattlesLost)

    Command = Set battles won 
    Actions = [KeyCommand1,KeyCommand2]
    

  • DynamicPropertyTrait to store it

    Actions = [,KeyCommand1,PROMPT,{"Please enter # of battles won (was "+BattlesWon+")"]
    Name = BattlesWon
    Numeric = True
    Min = 0
    Max = 1000
    

  • DynamicPropertyTrait to set veteran status - note once achieved it will persist

    Actions = [,KeyCommand2,DIRECT,{Veteran?Veteran:(BattlesWon-BattlesLost)>=10}]
    Name = Veteran
    Numeric = True
    Min = 0
    Max = 1
    Value = 0
    

  • CalculatedPropertyTrait for effective combat factor

    Name = EffectiveCombatFactor
    Expression = {BaseCombatFactor + (Veteran ? 2 : 0)}
    

  • LabelTrait to show star when a veteran

    Label = {Veteran ? "☆" : ""}
    

Again, these properties should probably be defined in a Prototype to be re-used across pieces.

Anyway, my 2¢

Yours,
Christian