• More sensible warnings about the :FOR[foo]:NEEDS[foo] problem, avoiding flagging the occurrences where the problems are not triggered.
• Reworks issues:
  • #31 Warn when :FOR is used with :NEEDS using the same modName on the patch

I will keep this release as PRE-RELEASE for some time, as I'm not fully confident I'm not missing some positives while trying to avoid false positives.

Your Attention Please

• Needs KSPe 2.5 or higher.
• Packages with -122- in the name are meant to be used on KSP 1.2.2.
• CurseForge packages are not built anymore, as Modular Management is the preferred distribution package for it.

As a matter of fact, first installs are usually better served by Modular Management so I strongly recommend you use it instead of doing everything by hand.

Keep Walking

• Fixes a pretty nasty Log Spam I let pass trough
• Log a warning when :FOR and :NEEDS on the same patch uses the same identifier, as this will not work exactly as one would expect.

Your Attention Please

• Needs KSPe 2.5 or higher.
• Packages with -122- in the name are meant to be used on KSP 1.2.2.
• CurseForge packages are not built anymore, as Modular Management is the preferred distribution package for it.

As a matter of fact, first installs are usually better served by Modular Management so I strongly recommend you use it instead of doing everything by hand.

Keep Walking

• Fix some long due "Reload Database" on the Module Manager Menu (Alt-F11)
  • Nope, the Full Reload is still broken, and it was hidden. Sorry!
• We had moved!
  • The Official Repository is now on https://github.com/KSP-ModularManagement/ModuleManager

Your Attention Please

• Needs KSPe 2.5 or higher.
• Packages with -122- in the name are meant to be used on KSP 1.2.2.
• CurseForge packages are not built anymore, as Modular Management is the preferred distribution package for it.

As a matter of fact, first installs are usually better served by Modular Management so I strongly recommend you use it instead of doing everything by hand.

• Slightly less spammy on spamming logs.

Keep Walking

Your Attention Please

• Needs KSPe 2.5 or higher.
• Packages with -122- in the name are meant to be used on KSP 1.2.2.
• CurseForge packages are not built anymore, as Modular Management is the preferred distribution package for it.

• Logging revamp/refactoring
  • Saner code
  • MOAR LOGS
  • Previous LOGSPAM conditional compiling is now pushed into the mainstream as TRACE messages.
    • Edit the relevant ModuleManager section on <KSP>/PluginData/KSPe.cfg file to set the desired log level.

Your Attention Please

• Needs KSPe 2.5 or higher.
• Packages with -122- in the name are meant to be used on KSP 1.2.2.
• CurseForce packages are not built anymore, as Modular Management is the preferred distribution package for it.

• Bumps versioning, catching up with upstream and formalising the fixes already implemented - some for ages... :)
• Removes yet some more deprecated calls from KSPe.

• (Hopefully) mitigates a pretty weird problem happening on some new Intel CPU's with asymmetric cores (and on a less extent, faster Intel and probably AMD with symmetric ones).
  • Initially discovered by LinuxGuruGamer, then (pretty badly) misdiagnosed by me until I got in my senses and did some testings.
• Removes some deprecated calls from KSPe.

Your Attention Please

• Needs KSPe 2.5 or higher.
• Packages with -122- in the name are meant to be used on KSP 1.2.2.

• Drops the Experimental status
• Relicense the whole shebang to GPL-3.0
• Make the thing properly distributable.
• Needs KSPe 2.5 or higher.

Note: files with -122- in the name are meant to be used on KSP 1.2.2.

• Updates the INSTALL.md file to reflect the new deployment model.
  • A new MM/L release wasn't really needed, but since I failed to update the install instructions and there're people using this, I choose to be conservative on the matter.
  • There're no changes on the DLL, so I choose to shove a "b" on the same release number.

Note: files with -122- in the name are meant to be used on KSP 1.2.2.

• Fixed a pretty lame mistake on the 1.2.2 port.
  • And, yeah. I should had tested this thing on KSP 1.2.2 recently... #facePalm