https://paste.dimdev.org/ziliruyota.mccrash

I was not using the Deadly Monsters mod when I was receiving a crash on 1.2.0.

However, I am confirming that the newest update (1.2.1) loads without error. Awesome work!

Same to me

Looks like you're using forge 14.23.4.2757, which is beyond the recommended build.Try switching to 14.23.4.2705, which is the 1.12.2 recommended build. Forge versions past the recommended builds are not always stable builds.

I'm not convinced this is related to Forge.

Confirming crash on startup, except I am using Forge 2705. Vibrant Journeys 1.1.5, however, works fine.

Keep up the good work though mc-jt9, I love how much this spices up the world.

Strange...I'm not getting any crashing from both the launcher and the dev environment.

Sorry, I'm sort of sick right nowand very tired, and I'm trying to wrap my head around this. Not sure why it's throwing an IndexOutOfBoundsException, I've followed the stack trace and I understand exactly what it's doing.

My guess is that since it worked perfectly during testing and in my actual Minecraft game, it's likely that another mod is interfering with the spawnable lists.

Hmm but 1.1.5 works fine..strange

Edit: I've uploaded v1.2.1 which reverts the entity spawn changes I made. Could you test it so I know it works? I'd really like you to have the new additions in 1.2.0 rather than having to stick with 1.1.5, which only has half of everything in the mod.
https://github.com/mc-jt9/ProjectVibrantJourneys/releases/tag/v1.2.1

Hi, I had the same problem with the 1.2.0, now it's fine with the 1.2.1.

Ok, I'll release it since it's a stable version. Hoping it works for the others who commented above. I'll close this issue once I'm sure it works for everyone.

Also, I still stick by my earlier statement. Go with the Forge recommended build and only use the later builds with caution.

I strongly suspect the culprit is Deadly Monsters since I tried running the game with only that and PVJ and the crash occurred. And I see that Sunconure11 uses DM too.

I looked at their source code and found no reason for it to cause a crash with this mod. The crash log explained it in the first few lines, but I see no reason for Biome.getSpawnableList() to throw an error. Weird :/

Thanks :)