Add a entrypoint before Mixin/AW bootstrap?

I am thinking to add an entry point before mixin/aw bootstrap happens (i.e. immediately after loading happens), which can give more flexibility for the mod developer. I guess we can call it PreInitEntryPoint?

I also see some previous attempts, it would be perfect if someone can share some difficulties on this.

[LogicFan]

What would you be trying to do to Mixin before bootstrap in the first place?

The use case could be:

1. dynamic loads library required by IMixinConfigPlugin.
2. do some initialization needed or alter the function of IMixinConfigPlugin.
3. alter the aw file loaded by fabric loader.
4. re-order how fabric do mixin
5. etc.

[Chocohead]

What would you be trying to do to Mixin before bootstrap in the first place? You can’t (or at least shouldn’t) even interact with it before the MixinBootstrap#init call so I don’t understand why you’d want to be going earlier than preLaunch.

There is certainly merit in being able to add your own mods into the resolution process through Loader plugins, as has been discussed in #223 for example, but even the goal is to make Loader handle them like a mod loaded normally rather than something which needed special handling for Mixins, AWs, etc.