modmuss
modmuss
> I've also seen devs run into issues when switching between Ornithe b1.7.3 and Babric b1.7.3, because both use a different manifest, so switching between projects requires clearing the cache....
Humm, intresting. I can see that being an issue, the easy fix for this is to not share the caches between diffrent versions. Or take into account the entire class...
This can likely be best fixed by allowing the jars to be split with `splitMinecraftJar()` without the adding the client only annotations. Care needs to be taken to ensure that...
The test harness is tottaly broken with configuration caching, in current shipping loom `gradlew --configuration-cache help` works just fine. Right now its exploding on a simple `SourceSet.getResources()` when ran using...
I really need a simple way to reproduce this, and more details. "not remapped" isnt so helpful, when there are about 4 diffrent ways things get remapped. The crash log...
> 1.3 fixes it This suggests that it was a 1.4 change that broke things? Most of the remapping changes I made happened in 1.5, the 1.4 diff to 1.3...
Easy enough to reproduce, many thanks for that. It doesnt take much to go deeper into the rabbit hole. Enabling mixin debug, its obvious the culpret seems to be: https://github.com/TerraformersMC/Terraform/blob/e876c3efc45db8bc690ddb7cfc66a4ab2c452668/terraform-wood-api-v1/src/main/java/com/terraformersmc/terraform/leaves/mixin/MixinProperties.java#L11...
I believe its caused by `fabric.loom.multiProjectOptimisation` and only building a single sub project. With MPO you must remap all of the jars at once, especially including the root project. The...
> This behaved itself from Loom 1.1 through 1.4. Yeah, im not sure what changed and what is the root cause. I'll leave this issue open to hopefully improve it...
Yes, MM likely need updating to our mercury fork as well as looking into what https://github.com/CadixDev/MercuryMixin/issues/18 means. Its been so long I have forgotten what this issue was about.