pardeike/Harmony

Improve HarmonySharedState for use in multiple loading contexts

Open

#741 opened on Oct 15, 2025

View on GitHub
 (0 comments) (3 reactions) (1 assignee)C# (4,616 stars) (461 forks)batch import
bugenhancementhelp wanted

Description

The current implementation leads to duplicate shared state when Harmony is loaded in a non-Unity process (like a .exe) and that prevents multiple mods from patching the same method.

At the end of this ChatGPT discussion is a suggestion that needs to be explored. The claim is that its backwards compatible and solves the problem this Issues rises.

https://chatgpt.com/share/68f013cd-b1b0-8009-8be0-1d3a3c182966

This needs to be implemented and tested. In both: the unity case and a single .exe case (maybe make sure it actually fails first).

Contributor guide

Tech stack
csharp
Domain
tooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of HarmonyKnowledge of .NET runtime patchingUnity development basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Explore the ChatGPT discussion linked in the issue for a backwards compatible suggestion. Implement the proposed changes and test them in both a Unity environment and a standalone .NET executable to ensure the shared state duplication is resolved. Verify that the fix does not break existing functionality across different loading contexts.