This release fixes a number of issues in and around the characteristics of campaign assets.

Campaign assets are quite complex in that they can either be unique or non-unique (see the screenshot above). This setting has a direct impact on how characteristics work for a campaign asset.

In general, unique campaign assets can only have one instance per map. When its characteristics are altered, the same alteration will propagate to all maps and journals.

Non unique campaign assets have characteristics that are completely independent and will never change because of an alteration made to another on-map instance.

Here is a list of the actual fixes that were implemented:

1. Changing the characteristic of a unique campaign asset will now affect all maps equally. For example if you have a unique spacecraft and reduce its hit points from 20 to 14 on one map, all other maps will be updated to reflect that spacecraft’s new hit point total.
2. Non-Unique campaign assets are all completely independent and can have multiple instances per map. Changing their characteristics never alters the characteristics of other instances.
3. Editing campaign assets no longer resets their on-map characteristics. Note, this fix will only kick in for existing on-map campaign assets after their on-map characteristics have been altered by the player with version 1.6.20.0 of Sojour**.
4. Editing the maximum value for a characteristic of a non-unique campaign asset will only affect newly dragged campaign assets to a map. Existing on-map campaign assets retain their current values. (This is the same behaviour as tokens)
5. Editing the maximum value for a characteristic of a unique campaign asset will alter all on-map versions to the new maximum value, regardless of which maps they appear on. (Again, the same behaviour as tokens)

** I did think of adding a data updater to update internal campaign asset values so that this fix would kick in right away. However, I decided against this approach as older versions of Sojour could have unique campaign assets on multiple maps, each with differing characteristic values. For that case, which value would the updater use? It would have to pick one at random, which might make on-map alterations that the user does not want – hence why I abandoned this approach.

That’s it for this release!

Have Fun!

RobP