Closed IsSkyfalls closed 3 months ago
The version.json
file looks exactly like that in a vanilla Minecraft 1.20.2 client jar, so that part is really not a Loom issue. I think release_target
is just a field that's not there on all game versions.
Loader is also able to read the version from the other fields just fine: https://github.com/FabricMC/fabric-loader/blob/d69cb72d26497e3f387cf46f9b24340b402a4644/minecraft/src/main/java/net/fabricmc/loader/impl/game/minecraft/McVersionLookup.java#L222-L227
Thank you for the quick response. It's indeed problem on my end. After comparing the code I realized that I was on an ancient version of loader. A few days back I thought that I can just go back to 0.14.1 since I needed to support 0.14.2x. The old dependencies probably got cached for a few days and didn't update until this afternoon, then it all broke. I also somehow pasted the old gradle.properties into the new repo when testing things, and thought I was going crazy(which I probably am). Sorry for my confusion.
This is reproducible with a newly generated mod on 1.20.2 with https://fabricmc.net/develop/template/. I haven't tested other versions yet.Not possible AftergenSources
theversion.json
in both clientOnly and common jars looks like this:Which is missing the
release_target
. I don't know whether it's been there before or not, since I had to nuke all my gradle caches in order to pin point the issue. This causesMcVersionLookup.fromVersionJson
in the fabric loader to fail, and it eventually falls back to using the file name as version string, which isminecraft-clientOnly-1f338b2c9f-1.20.2-net.fabricmc.yarn.1_20_2.1.20.2+build.4-v2
. Then it falls at the parser on runtime:I don't think I did anything before every single mod stopped being able to pass this step on my machine. Maybe it's a dependency issue? I can investigate more if anyone can point me to where this
version.json
is generated, thanks.