Skip to content

Conversation

@NathanKell
Copy link
Contributor

Adds a new modding patch which changes the functionality of SaveUpgradePipeline for mods. Now mods' UpgradeScripts get passed their own version in the sfs/craft file (or 0.0.0 if it predates this KSPCF version), and they can run based off their own versioning. FileVersion is used when present instead of base assembly version since most mods keep base version fixed so that they can be referenced by other mods safely, and just change fileversion.

Like the other modding patches, this defaults to off, since it is possible it will break some existing modding UpgradeScripts that haven't been rewritten to support this.

…e mods' versions when running SaveUpgradePipeline scripts.
@NathanKell NathanKell changed the base branch from master to dev September 5, 2022 23:50
@NathanKell NathanKell merged commit d9c88bb into dev Sep 6, 2022
gotmachine pushed a commit that referenced this pull request Dec 7, 2022
* Create ModUpgradePipeline modding patch. This patch will store and use mods' versions when running SaveUpgradePipeline scripts.

* Go back to storing versions for all assemblies. Bump KSPCF version to minor, not revision.

* Fix readme to link PR
gotmachine pushed a commit that referenced this pull request Jan 30, 2023
* Create ModUpgradePipeline modding patch. This patch will store and use mods' versions when running SaveUpgradePipeline scripts.

* Go back to storing versions for all assemblies. Bump KSPCF version to minor, not revision.

* Fix readme to link PR
@gotmachine gotmachine deleted the ModUpgradePipeline branch March 9, 2025 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants