You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: GameData/ModuleManagerWatchDog/CHANGE_LOG.md
+14-3Lines changed: 14 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,16 @@
1
1
# Module Manager Watch Dog :: Change Log
2
2
3
+
* 2024-0423: 1.1.2.0 (LisiasT) for KSP >= 1.2.2
4
+
+ Adds an Option Box asking the user what would be their preferred MM Fork when a conflict is detected.
5
+
+ We had moved!
6
+
- The Official Repository is now on https://github.com/KSP-ModularManagement/ModuleManagerWatchDog
7
+
+ Closes issue:
8
+
- [#11](https://github.com/KSP-ModularManagement/ModuleManagerWatchDog/issues/11) Implement a more friendly way to allow the user to select which MM fork it wants.
9
+
* 2024-0330: 1.1.1.2 (LisiasT) for KSP >= 1.2.2
10
+
+ Implements a "self-cleaning" mechanism intended to prevent the user being forced to manually delete artefacts on `GameData` once they decide to deinstall `Module Manager /L` and/or `Module Manager Watch Dog`.
11
+
- Specially necessary for CurseForge users.
12
+
+ Closes issue:
13
+
- [#10](https://github.com/KSP-ModularManagement/ModuleManagerWatchDog/issues/10) Detects when the host directory (`GameData\ModuleManager`) was removed, and kill `ModuleManager.dll` in response.
3
14
* 2023-0703: 1.1.1.1 (LisiasT) for KSP >= 1.2.2
4
15
+ More sensible updating mechanism, coping with how Windows handles DLL files once they are loaded.
5
16
+ Fixes a bug on the KSPe's Install Checker/Update Tool
@@ -9,11 +20,11 @@
9
20
- Safer handling 1.12.x without screwing older KSPs.
10
21
+ Implements an "AutoFix", automatically fixing the user's rig when possible (respecting user's preferences).
11
22
+ Closes issue:
12
-
- [#8](https://github.com/net-lisias-ksp/ModuleManagerWatchDog/issues/8) Automatically fix the Module Manager installation borks when possible.
23
+
- [#8](https://github.com/KSP-ModularManagement/ModuleManagerWatchDog/issues/8) Automatically fix the Module Manager installation borks when possible.
13
24
* 2023-0313: 1.1.0.4 (LisiasT) for KSP >= 1.2.2
14
25
+ Makes the thing survivable if KSP starts with the `pwd` set to anywhere but the `KSPUtil.ApplicationRootPath`.
15
26
+ Closes issue:
16
-
- [#6](https://github.com/net-lisias-ksp/ModuleManagerWatchDog/issues/6) Resurrect the multiple ModuleManager DLLs check for KSP 1.12.x
27
+
- [#6](https://github.com/KSP-ModularManagement/ModuleManagerWatchDog/issues/6) Resurrect the multiple ModuleManager DLLs check for KSP 1.12.x
17
28
* 2022-1112: 1.1.0.3 (LisiasT) for KSP >= 1.2.2
18
29
+ ***DITCHED***
19
30
* 2022-0719: 1.1.0.2 (LisiasT) for KSP >= 1.2.2
@@ -24,7 +35,7 @@
24
35
- ModuleManager /L
25
36
- TweakScale
26
37
+ Closes issue:
27
-
- [#5](https://github.com/net-lisias-ksp/ModuleManagerWatchDog/issues/5) Cook a `GameData/*.dll` update tool
38
+
- [#5](https://github.com/KSP-ModularManagement/ModuleManagerWatchDog/issues/5) Cook a `GameData/*.dll` update tool
28
39
* 2022-0621: 1.1.0.0 (LisiasT) for KSP >= 1.2.2
29
40
+ ***DTICHED*** due a stupid mistake on handling pathnames... #facePalm
Copy file name to clipboardExpand all lines: GameData/ModuleManagerWatchDog/README.md
+13-11Lines changed: 13 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Module Manager Watch Dog
2
2
3
-
A Watch Dog for Module Manager.
3
+
A Watch Dog for Module Manager - with benefits.
4
4
5
5
6
6
## In a Hurry
@@ -34,7 +34,7 @@ A Watch Dog for Module Manager.
34
34
35
35
`MMWD` is a Watch Dog to monitor Module Manager, preventing known (and unsolved) bugs on KSP 1.8 and newer that affects it.
36
36
37
-
Additional services for updating specific DLLs on `GameData.` are now part of the solution, making it useful even for KSP <= 1.7.3 .
37
+
Additional services for updating specific DLLs on `GameData` are now part of the solution, and it is's now effective for KSP <= 1.7.3 .
38
38
39
39
The following services are provided:
40
40
@@ -44,11 +44,11 @@ Some 3rd party Add'Ons and this tool itself need critical DLLs to be present dir
44
44
45
45
Additionally, CurseForge - at least at the moment of this release - doesn't have a mechanism to allow updating files on it, triggering bug reports that will be easily avoided by deploying this tool.
46
46
47
-
This tool checks for need for installing (or updating) such critical DLLs automatically for selected Add'Ons.
47
+
This tool checks for the need of installing (or updating) such critical DLLs automatically for selected Add'Ons.
48
48
49
49
The feature is implemented on a discrete DLL, `WatchDogInstallChecker.dll`, and can be easily removed from the distribution without colateral effects (other than losing the functionality).
50
50
51
-
**It's not advisable to use it on installments managed by CKAN**, as it manages itself these DLLs.
51
+
**It's _not_ advisable to use it on installments managed by CKAN**, as it manages itself these DLLs.
52
52
53
53
The following Add'Ons are currently managed:
54
54
@@ -64,35 +64,37 @@ Historically, managing multiple Module Manager versions was problematic on KSP -
64
64
65
65
Before KSP 1.8, duplicated Assemblies were being loaded on dedicated App Domains, and so calling them would incur in marshalling (essentially, RPC but on the same process...) with significantly performance issues.
66
66
67
-
But on KSP 1.8 (and until 1.12.0), while trying to tackle down the performance problem by short circuiting all the duplicated Assemblies to the first one loaded, Squad inadvertently caused the oldest MM being elected to be used (as DLLs are loaded in alphabetical order), with pretty serious consequences.
67
+
But on KSP 1.8 (and until 1.12.0), while trying to tackle down the performance problem by short circuiting all the duplicated Assemblies to the first loaded one, Squad inadvertently caused the oldest MM being elected to be used (as DLLs are loaded in alphabetical order), with pretty serious consequences.
68
68
69
-
On KSP 1.12.0 things changed again. Now the DLL version is used as criteria, and the highest version found is the one elected to be used. **However**, a new bug was introduced, playing havoc on the system if more than one DLL **has the same filename**.
69
+
On KSP 1.12.0 things changed again. Now the DLL version is used as election criteria, and the highest version found is the one elected to be used. **However**, a new bug was introduced, playing havoc on the system if more than one DLL **has the same filename**.
70
+
71
+
Finally, on KSP 1.12.5 the problem of selecting the first DLL was resurrected, and now that old problem that started to happen on KSP 1.8 is in effect again.
70
72
71
73
So, different KSP releases will need different MM handling:
72
74
73
75
* On KSP \< 1.8, the tool complains if MM is not installed.
74
-
* On KSP \>= 1.8 and \< 1.12, the tool will yell on any duplicated Module Manager on the rig - *There can be only one!*
76
+
* On KSP \>= 1.8 and \< 1.12, as well KSP 1.12.5, the tool will yell on any duplicated Module Manager on the rig - *There can be only one!*
75
77
* On KSP \>= 1.12, the tool prevents installing MM/L together Forum's one as an extra safety measure.
76
-
+ MM/L behaves and it's 100% compatible, being a drop in replacement - it's safe to switch MM at any time.
78
+
+ MM/L behaves and it's 100% compatible, being a drop in replacement - it's absolutely safe to switch MM at any time (even the functional bugs are the same)
77
79
+ But yet is advisable to avoid having both installed at the same time.
78
80
79
81
The Author strongly advises to edit the `WatchDog.cfg` file and select enforcing the "1.8 rules". It's far the safest option - besides risking being a bit annoying sometimes.
80
82
81
83
### Checking TweakScale
82
84
83
-
Due the general mess that handling duplicated DLLs are on KSP, it was choose to install the formerly named `Scale_Redist.dll` file into `GameData` as `999_Scale_Redist.dll` . This aims to ensure the canon Redist is the first one to be loaded, as well to avoid eventual naming collisions with the few Add'Ons that used to have it embedded.
85
+
Due the general mess that handling duplicated DLLs is on KSP, it was chosen to install the formerly named `Scale_Redist.dll` file into `GameData` as `999_Scale_Redist.dll` . This aims to ensure the canon Redist is the first one to be loaded, as well to avoid eventual naming collisions with the few Add'Ons that used to have it embedded.
84
86
85
87
This way, we can be ensure the best performance on older KSPs as well a safest environment on newer ones.
86
88
87
-
The tool checks for known `Scale_Redist` clients and yells if they are present but not the Redist. It also yells if there're more than one copy of `Scale_Redist`are installed, and also enforce that the only one installed are the `GameData/999_Scale_Redist.dll` .
89
+
The tool checks for known `Scale_Redist` clients and yells if they are present but not the Redist. It also yells if there're more than one copy of `Scale_Redist` installed, and also enforces that the only one installed are the `GameData/999_Scale_Redist.dll` .
88
90
89
91
### Checking KSP Interstellar Extended
90
92
91
93
Similar handling are applied to `Interstellar_Redist.dll` from KSPIE.
92
94
93
95
### Final Considerations
94
96
95
-
This tool was originally aimed to be redistributed embedded on Add'Ons that used to redistribute Module Manager themselves in the past, unintentionally triggering the problems this tool aims to detect, but evolved to an Add'On de jure and de facto.
97
+
This tool was originally aimed to be redistributed embedded on Add'Ons that used to redistribute Module Manager themselves in the past, unintentionally triggering the problems this tool aims to detect - but evolved to an Add'On *de jure and de facto*.
0 commit comments