
Can't use the other classloader with mixinbooter
SettingDust opened this issue · 6 comments
ConfigDecorators
need Launch.loader
for get mod id. I'm sideloading a mixin service in my own Class Loader for mixin some others.
Can I disable it? Or remove the restrict since any classloader is able to adapt the logic?
It is meant for mod ids hence why it is pulling resource names from LaunchClassLoader
. How will you be sideloading another mixin service? What is the usecase?
I'll make the decorators non-static and decouple the FML elements then, thank you for bringing it up.
How will you be sideloading another mixin service?
Standalone class loader and a new MixinService
What is the usecase?
Mixin the bukkit plugins
It's being worked on here. The API should be finalizing in the next couple of days.