Crash: `ExecutionException:ArrayIndexOutOfBoundsException`
Nlkolev opened this issue · 8 comments
Description
i can't open my world in version 1.10.0
To Reproduce
Modpack version v1.10.0
debug.log or Crash report
Remove mod justenoughdimensions-1.12.2-1.6.0-dev.20211009.214847.jar
but I'm not getting it even though I removed this mod.
i deleted it and installed it again and it didn't work either, same thing pops up and yes i removed the mod, I instead of updating directly in the profile of the modpack in curse, I'm updating the modpack in another profile.
Worlds made between the addition of otg and before 1.1 need some manual editing. Please try these steps and report if they work or not (they worked for me).
1️⃣ Attempt to load the save, it fails (but don't skip this step, it changes something)
2️⃣ Open savename/OpenTerrainGenerator/Dimensions.txt
If it looks like this:
0,overworld,true,-2189424128043441729,0,3,Void,false,3930270392853900288,1
Remove second half, make it look like this:
0,overworld,true,-2189424128043441729,0
(Yours might look different. In any case delete the 5 consecutive values "3,Void,false,some_big_number,1,")
3️⃣ Open savename/OpenTerrainGenerator/Config.yaml
Find - PresetName: "Void"
Delete this and every indented line under it stopping right before the next - PresetName
and double check that step 3 took effect, because your change might get overwritten by the running game
everything was going well, but the map crashed, it appears like this: "Could not initialize dimension e", OTG Preset "Void" is not installed."
I did it, i deleted the "OpenTerrainGeneration" Folder, then it opened normally.
Thanks for the attention!
Glad you got it working, but deleting the folder will cause a few problems. The alien jungle dimension won't be working anymore, and if your overworld is handled by otg, then you'll get some ugly terrain borders because your seed changed. There might be other problems, depending on what exactly otg stores in there, but probably nothing pack breaking.
I recommend you keep the folder around under a different name, because this might be fixed in the next version.