[Forge][1.20.1][CrashOnNewWorld] Crash on creating new world after installing Lost Cities+Worlds

Question

[Forge][1.20.1][CrashOnNewWorld] Crash on creating new world after installing Lost Cities+Worlds

drakray opened this issue 2 months ago · 1 comments

drakray commented 2 months ago

As seen in McJtyMods/LostCities#677

Log report a trouble with Blueprint, any idea?

Other report sample

crash-2025-02-09_10.32.32-server.txt

debug.log

snippet

Description: Exception generating new chunk

java.lang.NullPointerException: Cannot invoke "net.minecraft.core.Holder.get()" because "biome" is null
	at mcjty.lostworlds.worldgen.wastes.BiomeMapper.getMappedBiome(BiomeMapper.java:70) ~[5-lostworlds-1.20-0.0.3.jar%23877!/:1.20-0.0.3] {re:classloading}
	at mcjty.lostworlds.worldgen.wastes.WastesBiomeSource.m_203407_(WastesBiomeSource.java:86) ~[5-lostworlds-1.20-0.0.3.jar%23877!/:1.20-0.0.3] {re:classloading}
	at com.teamabnormals.blueprint.core.util.BiomeUtil$OriginalModdedBiomeProvider.getNoiseBiome(BiomeUtil.java:138) ~[0-blueprint-1.20.1-7.1.1.jar%23773!/:7.1.1] {re:classloading}
	at com.teamabnormals.blueprint.common.world.modification.ModdedBiomeSource.getSlice(ModdedBiomeSource.java:94) ~[0-blueprint-1.20.1-7.1.1.jar%23773!/:7.1.1] {re:classloading}
	at com.teamabnormals.blueprint.common.world.modification.ModdedBiomeSource.m_203407_(ModdedBiomeSource.java:71) ~[0-blueprint-1.20.1-7.1.1.jar%23773!/:7.1.1] {re:classloading}
	at net.minecraft.world.level.biome.BiomeSource.m_213971_(BiomeSource.java:140) ~[client-1.20.1-20230612.114412-srg.jar%231378!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:mixins.unusualend.json:BiomeSourceMixin,pl:mixin:APP:terrablender.mixins.json:MixinBiomeSource,pl:mixin:APP:alexscaves.mixins.json:BiomeSourceMixin,pl:mixin:A}

Minecraft 1.20.1
Forge 47.3.27
McJtyLib 8.0.6
LostCities 7.3.6
LostWorlds 0.0.3
Blueprint 7.1.1
BunchaOtherMods™(listed in crashlog)

Default configs, LostWorld Waste world type, Biosphere Cities

SmellyModder · Answer 1 · 2025-02-12T05:17:35.000Z

You have many mods installed and the reason for the crash is quite bizarre, so it's unclear if it's just an issue between Blueprint and Lost Cities. Blueprint wraps the overworld's biome source to allow mods to greatly modify biome distribution.

However, the crash looks to have nothing to do with Blueprint at its deepest level because it looks like somehow the biome source that Lost Worlds wraps ("vanilla's" biome source) is somehow returning a null biome?

Here Lost Worlds calls the multi-noise biome source and the returned biome gets used later in the method.
The mapper then expects a non-null biome, which should be what happens, but gets a null one here, causing the null pointer crash.

Due to how Lost Worlds and Blueprint modify the overworld's biome source, it's easy for the report to point to us, but this could actually be caused by another mod. It also appears the developer of Lost Worlds and I cannot reproduce this issue with just our mods.

Share to