[1.3.59.1062] Launch failure without Reliquary
Closed this issue ยท 4 comments
Minecraft version: 1.21.1
Neoforge version: 21.1.192
SophisticatedCore version: 1.3.59.1062
It looks like there is an underlying requirement on Reliquary that may be causing the game to fail to launch without it. I'm getting the following error at launch without Reliquary installed but once added the game boots just fine.
-- Head --
Thread: Render thread
Stacktrace:
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) ~[?:?] {}
-- Mod loading issue --
Details:
Caused by 0: java.lang.NoClassDefFoundError: reliquary/entity/potion/ThrownPotion
at TRANSFORMER/[email protected]/net.p3pp3rf1y.sophisticatedcore.init.ModCompat.lambda$register$18(ModCompat.java:32) ~[sophisticatedcore-1.21.1-1.3.59.1062.jar%23674!/:1.21.1-1.3.59.1062] {re:classloading}
at TRANSFORMER/[email protected]/net.p3pp3rf1y.sophisticatedcore.compat.CompatRegistry.lambda$initCompats$3(CompatRegistry.java:30) ~[sophisticatedcore-1.21.1-1.3.59.1062.jar%23674!/:1.21.1-1.3.59.1062] {re:classloading}
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596) ~[?:?] {re:mixin}
at TRANSFORMER/[email protected]/net.p3pp3rf1y.sophisticatedcore.compat.CompatRegistry.lambda$initCompats$4(CompatRegistry.java:28) ~[sophisticatedcore-1.21.1-1.3.59.1062.jar%23674!/:1.21.1-1.3.59.1062] {re:classloading}
at java.base/java.util.concurrent.ConcurrentHashMap.forEach(ConcurrentHashMap.java:1603) ~[?:?] {re:mixin}
at TRANSFORMER/[email protected]/net.p3pp3rf1y.sophisticatedcore.compat.CompatRegistry.initCompats(CompatRegistry.java:26) ~[sophisticatedcore-1.21.1-1.3.59.1062.jar%23674!/:1.21.1-1.3.59.1062] {re:classloading}
at TRANSFORMER/[email protected]/net.p3pp3rf1y.sophisticatedcore.SophisticatedCore.lambda$construct$1(SophisticatedCore.java:78) ~[sophisticatedcore-1.21.1-1.3.59.1062.jar%23674!/:1.21.1-1.3.59.1062] {re:classloading}
at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?] {}
at MC-BOOTSTRAP/[email protected]/net.neoforged.fml.DeferredWorkQueue.lambda$makeRunnable$2(DeferredWorkQueue.java:67) ~[loader-4.0.41.jar%23107!/:4.0] {}
at MC-BOOTSTRAP/[email protected]/net.neoforged.fml.DeferredWorkQueue.makeRunnable(DeferredWorkQueue.java:62) ~[loader-4.0.41.jar%23107!/:4.0] {}
at MC-BOOTSTRAP/[email protected]/net.neoforged.fml.DeferredWorkQueue.lambda$runTasks$0(DeferredWorkQueue.java:47) ~[loader-4.0.41.jar%23107!/:4.0] {}
at java.base/java.util.concurrent.ConcurrentLinkedDeque.forEach(ConcurrentLinkedDeque.java:1650) ~[?:?] {}
at MC-BOOTSTRAP/[email protected]/net.neoforged.fml.DeferredWorkQueue.runTasks(DeferredWorkQueue.java:47) ~[loader-4.0.41.jar%23107!/:4.0] {}
at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?] {}
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?] {}
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?] {}
at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?] {re:mixin}
It will only try to load the Reliquary compat if Reliquary mod is present, but recently one of the packages in Reliquary changed its name from entities to entity and from the look of it seems like you have older version of Reliquary, but hard to tell without the full crash log that includes list of mods.
Just to be sure I have tried to start a modpack that has just Sophisticated Storage and Backpacks in it and that loads without any issue so it really looks like you had an older version of Reliquary in your modpack
I definitely didn't have Reliquary in my modset but now I'm curious if some other mod was making sophisticatedcore think it was present? I'm building a custom modset so not a big deal, I can just add reliquary but very curious.
the only way this could happen is if the modlist included mod with id reliquary because that's what is checked before the compat tries to load. anyway I am going to close as I don't see anything wrong / nor can recreate. If you will still get this issue feel free to reopen, but I would like to see the full crash log / potentially latest.log in that case.