The game crashed whilst tesselating liquid in world.
HyperAnimates opened this issue ยท 9 comments
Minecraft Version: 1.20.4
Litematica Version: 0.17.3
MaLiLib Version: 0.18.3
Mod Loader: Fabric 0.15.11
Crash Report : https://mclo.gs/AS1Ched
As you would expect, I was making a build that I wanted to make into a schematic. I finished the build and saved it. That part was normal, however when I go to load it in the same world to test it the schematic crashes my game saying " The game crashed whilst tesselating liquid in world". The game also crashes when I join the same world, make a new world, or load the schematic in a different world. I have to delete the schematic file out of my schematic folder to actually go back into any world I loaded the schematic file in. I even removed all my mods from my mods folder, turned off all my resource packs, and turned off all my shaders but my game still crashed upon loading the schematic. This wasn't a one time thing either, I've made my build into a schematic dozens of times but they all crash. I have tried getting rid of powered on redstone, moving minecarts, and liquid but the schematic still crashes. In the crash report, it gives me cords for where the tesselating liquid is but it is nowhere near the schematic area box...ok its actually like a chunk or two away but it's still far.
The schematic does load in my world and doesn't crash when I turn off rendering but does crash when I turn it back on.
I first tried this on my steam deck with prism launcher but the schematic crashed so I moved over to my laptop with the normal minecraft launcher but it still crashes.
I am new to using litematica but I understand the basics.
Is it just water or what type of fluids does your schematic have? Can you send me the schematic file? What biome are you in, or does that not matter? It seems to crash via the Fabric API fluid rendering stuff while failing to get the biome...
I just tested Litematica 0.17.3 in my test world with the Fabric API version 0.97.0 that you have (and also a couple of other versions) but no crash.
While you tested without other mods, did you still keep Fabric API? My mods don't need it separately installed (at least up to 1.20.4) so you can also try without it to see if it's the Fabric API itself or some other mod that uses it to do something that causes this.
Here is the schematic file if you still want to look at it: https://www.mediafire.com/file/w1b45ngdps7e2a2/Furnace.litematic/file
I use lava and bubble elevators in my build.
I don't think the biome matters. First, I tested the schematic in a custom super-flat world and then I tried it in a new world (in a plains biome) but the game crashed each time.
I did try and remove the fabric API (Just leaving a few mods in the folder) and the schematic actually loaded! But, when I put it back that's when the schematic started crashing again.
Hmm that's weird. That schematic still works fine without crashing in my test instance, even with Fabric API 0.97.0 installed.
My test world is an old superflat world.
These are the mods I had enabled:
Ok, I went back and removed all my mods and added them back one at a time. The problem mod was Legacy4j. Every mod worked fine and my game didn't crash anymore once I removed Legacy4j. I was pretty bummed about this considering that this was the mod that made me want to come back and play minecraft again. Well, thanks for your help.
Try this build of Legacy4J: https://masa.dy.fi/tmp/minecraft/mods/3rd_party/Legacy4J-1.20.4-1.6.7%2Bmasa.1.jar
It should hopefully fix at least this one line where the current crash happens. No idea if there are other issues after this...
This build does nothing. It doesn't change the menus or sounds like the mod normal should. I tried using it with a release of Legacy4j but it still crashed. What exactly does this build do?..other than fixing the line of the crash.
Oh shoot I didn't even look at the file size first, yeah it's basically empty... Which means that I don't know how their build script works then.
