Loading Classic fails on versions greater than 0.4.9
See original GitHub issueThe introduction of builtin mods broke it, because Loader can’t find the version string in the main class (either com.mojang.minecraft.Minecraft
or some obfuscated name in 0.0.13a_03 onwards, like com.mojang.minecraft.l
in 0.30 or com.mojang.minecraft.c
in 0.30).
Loader then tries to parse the jar’s same as a version, which fails when it’s just a random name given by Loom.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
KeeperFX - Test builds for version 0.4.9 - Keeper Klan Forum
Install this like you would any version of KeeperFX. You cannot bring over your save files or settings from 0.4.8. Do not overwrite...
Read more >apollo-boost | Yarn - Package Manager
Important: This documentation covers modern versions of Yarn. For 1.x docs, see classic.yarnpkg.com. Yarn.
Read more >Yum update fails due to dependency resolution
Hi, I am trying to update packages in RedHat 7.6 and I keep getting this error due to dependency resolution.
Read more >lavaan: an R package for structural equation modeling and ...
When the package is loaded, a startup message will be displayed showing the version number, and a reminder that this is beta software....
Read more >Can't install mysql2 gem on macOS Sierra - Stack Overflow
Bundle installing the mysql2 gem kept failing, until: ... said you had to use mysql2 gem version greater than 0.3.17 with MySQL version...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had the same issue getting alpha to load, this was the fix. I believe version parsing itself shouldn’t be broken (although I haven’t tested it), but where it finds the version in the jar might be broken. You may have to add something to
net.fabricmc.loader.minecraft.McVersionLookup.getVersion(Path gameJar)
.Thanks, I believe we need to