[1.14.4] Client crash when starting a new world. .IllegalArgumentException: bound must be positive -- jigsaw.JigsawPattern.func_214944_a
ProsperCraft opened this issue ยท 2 comments
Bug Report
[ ]
How can the crash be reproduced?
[Make a new world]
This seems to be an edge case, and I can reproduce it every time with this world, but only with the full pack, I tried to add one mod at a time, but every load in gave a different looking world as I think each of the mods changed the world so it wasn't loading the biome that crashes unless you have the full pack.
Google search for JigsawPattern.func_214944_a produced nothing.
I downloaded the source and searched inside the files for jigsaw and found nothing.
Crash Report and Logs
Crash report-
https://gist.github.com/ProsperCraft/052389f088886974930c4584fa9510e0
[
latest.log
]
Mod Version
[BiomesOPlenty-1.14.4-9.0.0.254-universal]
forge-1.14.4-28.1.44
Modpack - https://www.curseforge.com/minecraft/modpacks/the-adventures-of-halk
I mean, this doesn't seem to have anything to do with BOP inherently, and is caused by something with village generation (Which, we don't alter at all. We just add villages to some of our biomes, and it's a single line of code for each one).
Sorry to say, but it's really on you to figure out exactly which mod is causing it, when BOP isn't in the stacktrace at all, and you're using other biome mods. Hell, it might not even be caused by a mod. It might just be something weird with vanilla, in which case, you should check the Minecraft Mojira issue tracker as well.
This could indeed be caused by BOP, if it would add a village with an invalid configuration to it's biomes (see TeamLapen/Vampirism#543 (comment))
E.g.
this.addStructure(Feature.VILLAGE, new VillageConfig("village/does/not/exist", 6));
or something less obvious (typo).
However, I went though all of BOPs overworld biomes and couldn't find a typo (might have missed something though)