Some mods sabotaged to fail with (this) Harmony

[drok]

Quoting YuLun:

Did two test loading today and here's my results:

• Test 1 (logs)
• Test 2 (logs)

And some known issues:

• @MacSergey removed your harmony (re) from checklist so his mods disabled themselves
• Harmony showing 'FAILURE' and marked in amber might still be able to load game (not sure if that's designed to be)
• Move it mod can load but not functional
• Node Controller (not the redesign one) errors and disables itself
• Realistic Walking Speed also errors and disabled, however I doubt about this
• So far other mods I have are working, only several have UI issues but seems not affecting functions

Update about Realistic Walking Speed: It is incompatible, but it's weird since it worked fine with the workshop version of Harmony (re), I'm not sure if that's a sub-issue of #9 or another hidden issue

Notes:

• CO started Harmony-related hostilities on Feb 6, 2021 with their update to Harmony 2.2 and the related API 2.1.0 which includes social engineering to persuade mod users to switch to the CO Harmony.
• At time of this report, "Move it" has not been updated since Jan 6
• At time of this report, "Realistic Walking Speed" was last updated Jan 2
• some @MacSergey and @kian.zarrin mods have been updated post API 2.1.0, and at this time include the social engineering pop-ups
• due to the assembly resolution logic in mono, mods that use "commons" assemblies may behave differently even if not updated, if another mod of the same author uses a newer "commons" assembly. In this case, the newer "commons" will be used with the old mod, yielding new behaviour.

In CO's Harmony 2.2 release notes, they state publicly (emphasis from original text) that updating to the new API is not needed. However, CO's friends (@MacSergey and @kian.zarrin, among others, ie the clique) have apparently been advised to update their API:

Note that there is NO NEED to update existing mods. The new version should be fully backwards compatible with mods developed for Harmony 2.0.x, unless the developers did something horribly wrong.

This means existing mods can now be classed as follows:

• mods that do not participate in hostilities (ie, pinned to API 2.0.0, which was the last API to not include social engineering)
• mods that deliberately participate in hostilities (updated to API 2.0.0 and took other steps to break compatibility)
• mods that accidentally participate in hostilities (updated to 2.1.0 not realizing this update only adds the social engineering features)

If you have a mod and are accidentally using API 2.1.0 you can roll back to API 2.0.0 (direct download) - Note that Microsoft/nuget.org does not allow nuget packages to be removed or changed once published, but they can be hidden at author's request. The direct link will always work even when the package is hidden. Using API 2.0.0 will allow your mod to be compatible with any Harmony version 2.0.4 or newer.

[drok]

YuLun, the output logs are cut short because of the InstantReturnToDesktop mod; this mod forcefully shuts down the application, preempting orderly shutdown. This means the full, "Final Harmony Report" is not generated and written to the log file.

Would you mind disabling InstantReturnToDesktop and running your test once more, and update the output_log.txt ?