feat: Implement mod versioning#1051
Merged
Alystrasz merged 27 commits intoR2NorthstarTools:mainfrom Sep 5, 2025
Merged
Conversation
Collaborator
Author
|
@GeckoEidechse what should happen when flightcore can't load |
Member
|
I'd say rebuild in v0 for now but have a feature flag or simple conditional check to tell it to rebuild in v1 instead. That way we can just "flip the switch" when we release the corresponding update in Northstar. |
Member
|
Clippy CI errors are from update in Rust toolchain and will be fixed by #1053 |
… into feat/mod-versioning
and then renaming the new file
as CI might not always have access to signing key so we need to disable the updater
as `sponge` cannot be easily installed on Windows runners
Collaborator
Author
|
Tested today with the new Northstar release candidate, still works with both old and new manifesto formats: multi-versions.webm |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implementation of R2Northstar/NorthstarLauncher#828 new manifest format, going from:
{ "Parkour": false, "HUD Revamp v2": false }to:
{ "Parkour": { "0.2.0": false, "0.2.1": false }, "HUD Revamp v2": { "2.0.0": false } }If the current version of the manifest cannot be defined automatically,
NORTHSTAR_MODS_MANIFEST_VERSIONdefault value will be used instead.(This is not a breaking change, as the current manifest format support is preserved.)
TODOs
set_mod_enabled_statuswith mods we don't know the version to enable/disable (e.g. core mods/mod settings)rebuild_enabled_mods_jsonTesting
With this contribution, Flightcore supports both manifest versions dynamically, which means you can switch between profiles using different versions with no issues.
To test this, I configured a
R2Northstarprofile with current manifest format, and aR2Developmentprofile with new manifest format:mod-versioning-support.webm
v0 (current format) manifest: enabledmods.json
v1 (new format) manifest: enabledmods.json