Version 1.20.1-4.0-440 Crashes Modpack when opening Creative Inventory
lozadajobd opened this issue ยท 4 comments
I have a modpack that includes Quark and after updating Quark to version 1.20.1-4.0-440 it has been causing my game to crash every time I open my inventory in Creative and Survival mode. Fortunately, this seems to only occur with my modpack since I tested the mod again with a barebones installation of Zeta + Quark only (using the latest versions) and experienced no crashing there.
Also, the game launches completely normally and so does creating a new world and loading a preexisting world. GUI screens such as the pause menu are also unaffected. The game only crashes when opening any inventory screen. Do note that before this update, Quark worked fine for the modpack. I even downgraded to version 4.0-439 and this resolved the issue and is the band-aid fix I am using right now
This might not be a serious issue as my modpack has 160 other mods installed, including Syntra Connector to bring in some Fabric mods, which is known for being quite crash-prone, though I am still searching for the exact culprit for the crashes. Regardless, I will leave this here anyway just in case it provides any useful insights.
Log: https://pastebin.com/raRC8kwZ
Crash Log: https://pastebin.com/WVYdxSWU
Using:
Quark Version: 1.20.1-4.0-440
Zeta Version: 1.20.1-1.0-16
Forge Version: 1.20.1-47.2.17
Allocated RAM: 5080MB
Here's my config since it's not the default one
quark-common.toml.txt
This may be a duplicate of #4768, I commented there that it seems to be the Sort feature being disabled that causes the crash. Try setting it to TRUE (I see its false in your config as well) and see if the symptoms persist.
This may be a duplicate of #4768, I commented there that it seems to be the Sort feature being disabled that causes the crash. Try setting it to TRUE (I see it's false in your config as well) and see if the symptoms persist.
Very interesting! I also had Inventory Sorting Disabled in my config. I can confirm that this fixed things after I re-enabled it in the config. Hope this gets fixed soon but thanks for the temporary fix!