I have found a small bug in this mod. When I attempt to install it alongside the "Twilight Forest" mod, the game loads correctly and then crashes with the following error:
java.lang.ArrayIndexOutOfBoundsException: -1
at CustomSpawner.getCustomBiomeSpawnList(CustomSpawner.java:596)
at CustomSpawner.doCustomSpawning(CustomSpawner.java:266)
at mod_mocreatures.OnTickInGame(mod_mocreatures.java)
at BaseMod.OnTickInGame(BaseMod.java)
at ModLoader.OnTick(ModLoader.java)
at EntityRendererProxy.b(EntityRendererProxy.java)
at net.minecraft.client.Minecraft.run(SourceFile)
at java.lang.Thread.run(Thread.java:679)
The Twilight Forest mod adds a new dimension in which some vanilla Minecraft biomes have been removed or changed, and some new biomes have been added. I suspect that there isn't a proper custom spawn list for one or more of these biomes. As a result, when the getCustomBiomeSpawnList method tries to find the index of this biome's list, it gets back -1. Then it tries to grab the list at index -1, throwing the error. I think a simple bounds check should solve that problem. If not, it might be possible to disable custom mob spawning in areas with unrecognised biome names.
0
java.lang.ArrayIndexOutOfBoundsException: -1
at CustomSpawner.getCustomBiomeSpawnList(CustomSpawner.java:596)
at CustomSpawner.doCustomSpawning(CustomSpawner.java:266)
at mod_mocreatures.OnTickInGame(mod_mocreatures.java)
at BaseMod.OnTickInGame(BaseMod.java)
at ModLoader.OnTick(ModLoader.java)
at EntityRendererProxy.b(EntityRendererProxy.java)
at net.minecraft.client.Minecraft.run(SourceFile)
at java.lang.Thread.run(Thread.java:679)
The Twilight Forest mod adds a new dimension in which some vanilla Minecraft biomes have been removed or changed, and some new biomes have been added. I suspect that there isn't a proper custom spawn list for one or more of these biomes. As a result, when the getCustomBiomeSpawnList method tries to find the index of this biome's list, it gets back -1. Then it tries to grab the list at index -1, throwing the error. I think a simple bounds check should solve that problem. If not, it might be possible to disable custom mob spawning in areas with unrecognised biome names.
I hope this info is helpful to you.