Crash with new version
mxnmnm opened this issue · 7 comments
Currently, the public stable release of vanilla-fix will cause this issue to happen.
For now, you can disable the mod, or run an experimental build of it here
Also, due to issues with mixin, make sure your client loads JEID first, you can do this by renaming the mod with a "!" at the front for example.
Ex: JustEnoughIDs-1.0.3-54.jar -> !JustEnoughIDs-1.0.3-54.jar
This should fix your issue.
With solution provided by @AWildTeddyBear the game load properly but when loading a world, the screen keep at 0% and in the log it just say server shutdown (with user disconnected etc) (i can provide log if this can be useful)
it looks like its having an issue with sponge. I think they said in the changelog it will take a while to fix this, so just use the previous update for now
Hi, same issue here! Unfortunately the workaround isn't appropriate for my pack as I host on curseforge and as such can't distribute mods with altered filenames. However, I note that a fix is being worked on, so for now I'll simply revert to the last update. In case another data point is helpful, here are my diagnostics:
Forge: 2847
Just Enough IDs: 1.0.3-54
Crash report: https://paste.dimdev.org/soquzasijo.mccrash
This occurred in a pretty heavy modlist (although I do not use sponge or spongeforge) and I have not run an isolated test.
While I'm going to wait on updating and as such don't have anything to report, I would like to point out that renaming files is NOT allowed on modpacks hosted on curseforge, like mine and many others' are. At the very least the mod should be uploaded with the ! already there, assuming it causes no further conflicts. Beyond that, the root issue with mixin will need to be resolved, or a fix with this mod implemented.
Alright so I updated some mods that got new updates and things are good now (I didn't even have to bother renaming JEID)