Player

Right, I see. I can look into this.

Not sure, the particular code is currently fairly isolated from the runtime state, it doesn't even act on ModContainers with its current uses.

That's unlikely to have been rated to the issue. The actual root cause of this kind of issue is typically an incomplete upload of the libraries folder.

The `.fabric` folder only contains the remapped vanilla server jar, which shouldn't cause the issue mentioned in the opening post. It is possible that you ran into multiple issues at...

If you have Forge you can use https://www.curseforge.com/minecraft/mc-mods/log4j2-jndi-exploit-fix For vanilla Mojang fixed the client if you use their launcher or MultiMC. Servers can use the workaround detailed at https://www.minecraft.net/en-us/article/important-message--security-vulnerability-java-edition Fabric...

This makes it very easy to screw the loaded classes up by loading classes too soon, we need to first ensure that none of MC or its libs are on...

pre-launch was specifically placed at the earliest time where everything is safe to class load and set up, only static initializers can cause a problem there. `freeze` doesn't load mod...

Adding the Jar to the class path does nothing since anything JVM is using lazy loading. Only when a class is accessed the first time, it'll be class loaded, load...

No, I said that the current setup doesn't lend itself to do anything earlier than pre-launch. Once the class loader setup is such that none of the problematic classes (mostly...

I'm working on other bits that somewhat influence it atm. I think the next step would be having a chat.