Juuz

This happens because Gradle thinks (incorrectly, really) that subprojects' `genSources` tasks cross-depend on `unpickJar` from other projects since they touch the same file. In your case (assuming you have the...

No, if you do `gradlew genSources` it does it in all projects where it's found. `gradlew :genSources` with a colon would be the root project's. (Tasks won't cascade unless you...

> Looking at wiki edit history you seem to be the only editor of the page @i509VCB That's because it's a moved page. The [original page's history](https://fabricmc.net/wiki/format:modjson?do=revisions) also shows asie...

@asiekierka Do you agree to licensing this spec under CC0?

Ah, the irony. I PR'd the use of `archivesBaseName` because people weren't setting their *projects'* names (and with jitpack they get auto-inferred to `build` or something like that). This is...

This probably happens due to the behaviour of `ModCompileRemapper`. Each dependency in `mod*` configurations is treated as its artifacts (which are the jars for included builds and projects too): https://github.com/FabricMC/fabric-loom/blob/dbbc3457d5630661611e7cf4c42dc3f7b0e75e99/src/main/java/net/fabricmc/loom/build/ModCompileRemapper.java#L89...

> The slabs and stairs lack the prefix while the blocks have it. There are both "normal"/uncoloured/yellow and "all" (unprefixed) versions of the slab and stair tags, though?

This type of bugs shouldn't happen anymore after #451, but this might be yet another regression. Although, since you mentioned a "common" and a "fabric" subproject, are you perhaps using...

Hmm, okay. Do you have a link to the project source code? Loom's refmap adder *should* pick up all mixin JSON files that are declared in the fabric.mod.json, so I'd...

There's no clean way to do it, though, since the standard way of `from components.java` just causes an error. Some mods (like mine) want to have non-mod deps that are...