Default install_to to GameData/Mods for KSP2 #3861
Merged
+17
−3
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.
Motivation
Currently all KSP2 mods install to
BepInEx/plugins
. However, once the official mod loader is completed, this is expected to change toGameData/Mods
.I was expecting to change this in a new client release when the official mod loader was released, but the modding ecosystem has already begun experimenting with using this path. See KSP-CKAN/KSP2-NetKAN#68 and KSP-CKAN/KSP2-NetKAN#70, and current versions of SpaceWarp supposedly already allow it, which means we are likely to see mods soon that require it to be installed properly.
Changes
GameData/Mods
can be used ininstall_to
for KSP2, including with subfolder pathsBepInEx/plugins
can still be used for KSP2, but no longer with subfolder paths (no current mods use subfolder paths)install_to
for the default KSP2 install stanza (the one used when theinstall
property is not present) isGameData/Mods
FYI to @KSP-CKAN/wranglers and @cheese3660.
Risks
GameData/Mods
makes less sense than simplyGameData
), then we'll have to do this all over again with the new path.