Any plans/roadmap for Harmony 2.3?
Just checking in to see if Harmony 2.3 is planned anytime soon for UMM
I can update it if necessary. Is it compatible with version 2.2?
It is, I tried replacing it locally and running a bunch of mods and had no issue personally.
I've been running it for some time, I had no runtime issues but saw a few AccessTools exceptions in HarmonyLog. After moving to 2.3.1.1 I haven't had any problems. Would appreciate if you could upgrade as one of our games has a mix of modloaders and UMM loads before others, breaking some mods.
I decided to wait a bit until they release hotfixes.
Updated
Appreciate the update, unfortunetly the other modloader depends on .NET 4.8 flavor, we're just replacing the one in UMM folder with the 4.8 flavor for now. Anyway to support a 4.8 based release, there are features in Harmony 2.3.1.1 that are only available in the 4.8 flavor.
I also noticed that if a game has its own monomod, then harmony neither the full nor the thin version does not work. I will have to separate 2.2-2.3 and include in the config.
Interesting, I have monomod from RuntimeUnityEditor in the Game_Managed folded and luckily working ok. If you seperate out, can have a 4.i flavor, appreciate the legacy support but it's now hindering recent games.
On Fri, Mar 15, 2024, 9:38 PM newman55 @.***> wrote:
I also noticed that if a game has its own monomod, then harmony neither the full nor the thin version does not work. I will have to separate 2.2-2.3 and include in the config.
— Reply to this email directly, view it on GitHub https://github.com/newman55/unity-mod-manager/issues/137#issuecomment-1999686076, or unsubscribe https://github.com/notifications/unsubscribe-auth/APWQSJ7S35OVTHIDUJQZRTLYYL2WNAVCNFSM6AAAAABECR4G6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJZGY4DMMBXGY . You are receiving this because you authored the thread.Message ID: @.***>
Updated Harmony to net48
What features does Harmony provide on 4.8? Looks like it broke Linux, mono only supports 4.7
I think peeps were trying to patch asyncs and were setting their build target to 4.8 instead of just bumping the C# version in the csproj.