[1.12.2] Custom dimensions spawn overworld mobs, are seen as "Plains" biome

[Dizzlepop12]

After porting from 1.8.9 to 1.12.2, it's apparent that something has changed with dimension biomes. Each of my custom dimensions only has one biome in it, but apparently it's setting the biome to plains instead of the specified dimension biome, which is causing overworld mobs to spawn and no modded mobs to spawn. Any ideas? All help is greatly appreciated.

 

Dimension example: https://github.com/TheSlayerMC/Journey-1.12/tree/master/main/java/net/journey/dimension/terrania

Dimension registry: https://github.com/TheSlayerMC/Journey-1.12/blob/master/main/java/net/journey/dimension/DimensionHelper.java

[jabelar]

I don't have time at the moment to look at your code, but I would suspect it would be an issue with your BiomeProvider. Did you associate instances of BiomeProviderSingle to your dimensions and do they properly point to your custom biome?

[Dizzlepop12]

25 minutes ago, jabelar said:

I don't have time at the moment to look at your code, but I would suspect it would be an issue with your BiomeProvider. Did you associate instances of BiomeProviderSingle to your dimensions and do they properly point to your custom biome?

Yep. These are the main areas where the biome is supposed to be registered and mobs are set to spawn in the specific dimension:

https://github.com/TheSlayerMC/Journey-1.12/blob/master/main/java/net/journey/dimension/terrania/WorldProviderTerrania.java#L18

https://github.com/TheSlayerMC/Journey-1.12/blob/master/main/java/net/journey/dimension/DimensionHelper.java#L124

https://github.com/TheSlayerMC/Journey-1.12/blob/master/main/java/net/journey/dimension/DimensionHelper.java#L218

 

[jabelar]

Okay, in that case I would add a bunch of console statements throughout your code and then trace what happens. Like add a statement in each method and then you can confirm that every method is being called as expected. Of course in your print statements you can print out any values of interest as well to aid the tracing. It should be quickly obvious what the problem is once you trace it.