Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use community-distributed Harmony to avoid inter-mod conflicts #1

Closed
gotmachine opened this issue Mar 17, 2021 · 0 comments · Fixed by #2
Closed

Use community-distributed Harmony to avoid inter-mod conflicts #1

gotmachine opened this issue Mar 17, 2021 · 0 comments · Fixed by #2

Comments

@gotmachine
Copy link

I have released the community distributed Harmony v2 lib available here : https://github.com/KSPModdingLibs/HarmonyKSP

I've also pushed a Kerbalism release using it. Sorry for not waiting for everyone to be ready, but I won't be around much in the next months to take care of the situation.

Note that the CKAN people have done a great job at sorting the compatibility issues by updating the metadata for CKAN indexed mods, but of course that won't help for manual installs.

In the current state of things, mods that bundle Harmony 1 will break when HarmonyKSP is installed, as the KSP assembly loader will always load it first : from my tests, due to the HarmonyKSP folder being named 000_Harmony, any subsequent load of another version will redirect to that first loaded version.

The HarmonyKSP distribution include a basic install checker that will notify end-users during loading when other Harmony versions are installed :
image

As far as I know, outside of Kerbalism, the following mods are currently bundling Harmony :

  • Tilt'em : bundling Harmony 1, not updated since ~1 year
  • AirlockPlus : bundling Harmony 1, seems abandoned (last version is for KSP 1.7)
  • ConformalDecals : bundling Harmony 1 through the Shabby library
  • LMP : latest release is bundling Harmony 1, but master seems to have been updated to use Harmony 2
  • KSPW00tNow : bundling Harmony 2

I'm copy-pasting this issue in all those repositories for awareness. For details about the how and why, please refer to the initial discussion on the CKAN repository here : KSP-CKAN/NetKAN#8288 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant