clean(): Pass AmethystRuntime to Initialize function about amethyst HOT 2 CLOSED

I agree with eventually trying to move a system that is more type-safe for mod function parameters, although I don't know exactly how I would want to do that.

I think the problem with the system proposed above is that now amethyst kind of has two stages before and after debugger, the RegisterInputs mod function is called before a debugger is able to be attached to the game.

Because we can't attach a debugger (because it's too slow), it could make developing using that approach hard to debug. We could also split this into two, but I'd rather have one consistent pattern then having two different ones

The extern "C" __declspec(dllexport) can be shortened down using a macro like #define ModFunction extern "C" __declspec(dllexport). Which results in being able to do the following syntax ModFunction void RegisterInputs()

from amethyst.

I'm going to close this issue for now, I think this is something we are going to come back to in the future when amethyst starts to store more of the Minecraft state

from amethyst.