Usability improvements for missing files #4195
Merged
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.
Problem
Discord user
dan
reported frequent prompts from the dev build to reinstall mods after running the game, which said "metadata changed" even though the metadata for those mods had either never changed or changed over two years previously:Cause
This turned out to be due to ZeroMiniAVC, which deletes files that CKAN installed. The feature from #4067 detects that as a mod with missing files and prompts the user to reinstall that mod.
This was challenging to figure out for a CKAN developer and a dev build power user. It should be understandable for anyone.
Changes
This way if someone encounters this after the next release, we can tell them to click the changelog entry, then the Contents tab, and the missing file will be apparent immediately.
Separately, KSP-CKAN/NetKAN#10230 is updating ZeroMiniAVC's metdata to direct users to the CKAN setting they should be using instead.