@@ -14,6 +14,9 @@ To install, place the GameData folder inside your Kerbal Space Program folder. O
1414* ** REMOVE ANY OLD VERSIONS OF THE PRODUCT BEFORE INSTALLING** , including any other fork:
1515 + Delete `<KSP_ROOT>/ModuleManager*`
1616 - Yes. Every single file that starts with this name.
17+ - Older MM/L versions used to shove all files on `GameData`. This changed on 4.2.2.4.
18+ + Delete the directory`<KSP_ROOT>/ModuleManager/` if existant
19+ - This is the new deployment model as 4.2.2.4
1720* Extract the package's ` GameData ` folder into your KSP's root:
1821 + `<PACKAGE>/GameData` --> `<KSP_ROOT>/GameData`
1922
@@ -22,12 +25,16 @@ The following file layout must be present after installation:
2225```
2326<KSP_ROOT>
2427 [GameData]
28+ [ModuleManager]
29+ [PluginData]
30+ ...
31+ CHANGE_LOG.md
32+ LICENSE
33+ ModuleManager.version
34+ NOTICE
35+ README.md
2536 000_KSPe.dll
26- ModuleManager.CHANGE_LOG.md
27- ModuleManager.LICENSE
28- ModuleManager.README.md
2937 ModuleManager.dll
30- ModuleManager.version
3138 ...
3239 [PluginData]
3340 [ModuleManager]
@@ -37,9 +44,14 @@ The following file layout must be present after installation:
3744 ...
3845```
3946
40- Note: the ` PluginData/ModuleManager ` folder will be automatically created and populated after the first run.
47+ Note: the ` <KSP_ROOT>/PluginData/ModuleManager ` folder will be automatically created and populated after the first run.
48+
49+ Additionally, don't mangle with ` <KSP_ROOT>/ModuleManager/PluginData ` as it contents is used by ` ModuleManagerWatchDog ` to keep ` MM/L ` healthy.
4150
4251### Dependencies
4352
4453* [ KSP API Extensions/L] ( https://github.com/net-lisias-ksp/KSPAPIExtensions )
54+ + Hard dependency, it will not work without it.
55+ * [ Module Manager Watch Dog] ( https://github.com/net-lisias-ksp/ModuleManagerWatchDog )
56+ + Soft Dependency. It's possible to run `MM/L` without `MMWD`, but it's highly recommended to install it and let it care about the `MM` (being it my fork or not) healthiness.
4557
0 commit comments