AlexIIL

Sadly it's hidden fairly well, but the root cause of this is: ``` Caused by: java.lang.NullPointerException at mchorse.mclib.utils.PayloadASM.getPayloadSize(PayloadASM.java:14) at net.minecraft.network.PacketBuffer.func_180714_a(PacketBuffer.java:398) at buildcraft.lib.misc.MessageUtil.writeBlockState(MessageUtil.java:209) at buildcraft.silicon.plug.FacadePhasedState.writeToBuffer(FacadePhasedState.java:75) ``` So I think you need...

Implemented in 0.18.1-beta.1 with loader-plugins

Merged (with major edits) in #117

I'm not sure about adding vetoes to be honest - I'd rather information was available to the solver if possible. In addition this is quite a large change to go...

Does your log (not crash report) have any lines like the following: ``` [05:03:21] [main/WARN]: 'Failed to find the ModDependency 'from' to remove! [05:03:21] [main/WARN]: 'minecraft versions [1.20-

Erm, I think what you're running into is quilt's json format doesn't let you create a dependency range like this - we'll need https://github.com/QuiltMC/rfcs/pull/56 to actually be able to support...

This should be updated as of 0.6.4... although I haven't tested it yet. woops.

To be honest, I'm a bit unhappy with how game providers work, since I don't think we really *need* to have a single generalized version of quilt-loader that everyone installs...

Game providers unfortunately touch (and are called by) a lot of loader internals, so it's not really possible to stabilize those APIs. That's okay though since game providers aren't expected...

> It's just considering that if they'll be detached JARs, Oh, er, not all game providers actually - quilt-provided ones would be separate (complete) jars containing bare quilt-loader plus the...