Was <ksp_root>/GameData/KerbalTek/HyperEdit/, now
<ksp_root>/PluginData/HyperEdit/
There is also code to move files from the old location to the new
location so that the user's settings are not wiped
This prevents (1) KSP from loading these files into the game database
and (2) ModuleManager from considering them for its cache
There's no technical reason they couldn't e.g. be stored at e.g. <ksp_root>/GameData/KerbalTek/PluginData/HyperEdit/ (this would accomplish the same thing), but moving settings files out of GameData prevents issues with e.g. CKAN removing a mod but leaving the directory because there are unrecognized files in it, making ModuleManager think that the mod is still installed
Was
<ksp_root>/GameData/KerbalTek/HyperEdit/
, now<ksp_root>/PluginData/HyperEdit/
There is also code to move files from the old location to the new location so that the user's settings are not wiped
This prevents (1) KSP from loading these files into the game database and (2) ModuleManager from considering them for its cache
There's no technical reason they couldn't e.g. be stored at e.g.
<ksp_root>/GameData/KerbalTek/PluginData/HyperEdit/
(this would accomplish the same thing), but moving settings files out ofGameData
prevents issues with e.g. CKAN removing a mod but leaving the directory because there are unrecognized files in it, making ModuleManager think that the mod is still installed