McGuba wrote: ↑Thu Nov 28, 2024 9:52 pm
Not sure what's wrong here. I tried again and I cannot upgrade the Stg 41 Pak 36 regardless of what mode it is in. Since it has the 'noupgrade' trait.
But of course I can upgrade the other "normal" Pak 36 versions or any other multipurpose unit without that trait. And it does not matter what mode these are in, the game only shows the primary unit class upgrade options. It is all as it should be
Not sure what the "primary" trait really does,
"
primary: used for switchable units to indicate the main unit that is used for purchasing, upgrading, deploying, etc."
https://www.slitherine.com/forum/viewto ... 16#p627816
You are right!
Can't upgrade the Stg 41 Pak 36 in transport mode during BE scenario.
I should have correctly tested it before making that comment, I apologize for the confusion.
PS: For reference if a modder reads this and has a similar problem with PzC mechanics:
1a) The
"noupgrade" trait on a "primary" unit ID entry of a unit, that can switch to one alternate state, does prevent upgrading during a scenario, when switched to non-primary unit ID entry (the alternate state).
1b) This
"noupgrade" trait limitation on the "primary" unit ID entry seems to be disregarded during a deployment phase, here such a 2 state multipurpose unit can be upgraded, when switched to the non-primary unit ID entry (the alternate state).
1c) The
"noupgrade" trait limitation on the "primary" unit ID entry seems also to be disregarded, if the multipurpose unit has at least 3 unit IDs it can switch between. Then the "noupgrade" trait on the primary unit ID entry only effects that primary state, while the other 2+ alternate states seem to be unaffected (thus an upgrade is possible from either of the alternate states, during a scenario and during deployment phase). Though I have only tested this in a case where the 3 states form a loop (primary => secondary => tertiary => back to primary).
2) The
"noreplace" trait limitation on a primary unit ID entry seems to not restrict the replacement option when the unit is in alternate mode (neither in-scenario nor during deployment).
3) The
"nopurchase" trait limitation seems to also only affect the unit ID entry in which it is placed (though there might be shenanigans/issues with multipurpose units and too many nopurchase traits, not sure anymore, might have to use the availability date for purchase restrictions on some of them).
I really have to remind myself not to make inferences or draw from memory when making comments about the workings of the PzC engine

.