Player

https://github.com/sfPlayer1/fabric-loader/tree/extension

It is not really expressing this, but whether the mod gets loaded or not. The cs network dependence is to be expressed differently soon.

Ideally we'd skip the methods with the wrong descriptor instead - it has to be identical the non-defaut interface method.

We usually use system properties for these smaller tweaks. Can you say more about the application/purpose?

System properties are part of the jvm arguments, like -Dname=value, before the jar file or main class name. The vanilla launcher supports them. If you really need the argument, make...

It uses the same logic regardless of nested or not for the actual inclusion handling, do you have a reproducer for simple testing?

I think this is a limitation of the junit hackery since that apparently neds log4j on system cl? Do you have any ideas on a potential solution? Ideally one that...

Does this only happen in-dev? If so it may be an incorrect class path groups setting.

You may want to step into a res access in the debugger, it should end up in KnotClassLoader with your jar in the ucp

I already have something similar in the works