Harmony VS UniTask

Some more details https://github.com/pardeike/Harmony/issues/424

Here's what you're looking for.

Probably a little out of your scope but the library Harmony you can write patches (detours) on methods. Using get/set instead of a field would allow you to override the property's method. Let's say you wanted to write something to always have the name uppercase. You could patch the constructor and set this.name = this.name.ToUpper() but that field is publicly assignable so you can't really enforce that. On the other hand with a property you can override the set method to say this._name = value.ToUpper().

It's kind of a subtle distinction that I think was lost between the posted article and the original article it was responding to, but I don't think the kinds of reflection capabilities that Roslyn provides is what the author intended. The specific example given in the referenced article for "Higher-order programs" specifically refers to the ability to replace function implementations at runtime without interrupting the program, and specifically calls out hot-code reloading (such as what Java provides) as a deficient form of similar functionality. This is closer to the type of functionality libraries like Harmony provide, but even that solution requires including the library and instrumenting your code ahead of time.

https://github.com/pardeike/Harmony harmony lets you patch functions at runtime, kind of like a dll injection / memory edit

Download Harmony 2 and put net472 version of the library into GordianQuest_Data\Managed

I'd recommend looking into Harmomy and seeing if you're able to use it. It makes modifying DLLs pretty convenient.

If you develop projects in Unity - i really recommend to see at UniTaks.

Give the UniTask library a look https://github.com/Cysharp/UniTask

What I would say, however, is that I much prefer async / await via UniTask over standard Coroutines!

Lastly I recommend using UniTask to better await an asset load, use it, and release it without clunky Coroutines. Happy to give examples of how to use UniTask to update this code.

If you absolutely must muck about with threads in Unity yourself (though I struggle to think of a reason why you'd need to for the example given) then Unity's Jobs system is probably the way to go - though in most cases you can likely achieve whatever it is you're trying to achieve using something like UniTask (my preference) which gives you much nicer async / await support.

Great comment. The Unity task library is UniTask.

There are a few problems. Firstly use UniTask for async related things in Unity. Provides much better async integration with Unity.

This is where UniTask comes in. If your project relies heavily on asynchronous code-- it sounds like it does -- you'll likely enjoy this package. It doesn't allocate, hooks into Unity's PlayerLoop for per-frame timing, and allows for return types. You can even await existing Coroutines.

UniTask is a popular async/await library that doesn't have this problem.