Modpack

Custom

Game log

crash-2025-07-02_23.48.09-server.txt

Description

Upon entering one of the dimensions added by the Caveworld 2 mod, I am met with a crash that told me to mention it here (outlined in the log above, trimmed down to the most essential bits as the original crash log was too big to upload here.)

Additionally, there seems to be a bit of an issue regarding Aether II (and by extension, GalaxySpace and Galacticraft's moon dimension) where the client-side biome name (visible by pressing F3) will seemingly fail to update to reflect the server-side biome name and will instead default to the biome with ID 0 (in my case, Ocean). This doesn't seem to affect terrain generation but is somewhat jarring when using mods like Dynamic Surroundings that add sound effects for specific biomes. I unfortunately do not have any logs that outline why exactly this happens, all I know is that it only started occurring once I installed EndlessIDs and it happens no matter how recently the world was created. The biome IDs for the affected dimensions (at least in my modpack) are still within the original 256 limit range.

Addendum 1: I should also mention that the "biome name failing to update" issue seemingly only happens over random blocks. For example, when walking over a single chunk in the Aether dimension, roughly half of the blocks in said chunk will correctly display the biome as "Aether" when pressing F3 on top of them, while the rest will default to biome ID 0. The world seemingly randomizes which particular blocks are affected every time it is saved and reopened.

Addendum 2: I've experimented a bit and determined what happens when the only mods loaded are Aether II and EndlessIDs (and their dependencies). With EndlessIDs installed, the biome name when pressing F3 in the Aether is always the one registered to ID 0 (Ocean), meaning that the phenomenon I described in Addendum 1 was likely being caused by another mod I had installed. When reloading the world after uninstalling EndlessIDs, the biome name reverts to the correct one (Aether) even in chunks that were generated while using EndlessIDs. Using the Nature's Compass mod with both the Aether/EndlessIDs mods installed, it was able to locate the Aether biome in the Aether but not any Ocean biomes (despite F3 claiming the current biome to be Ocean). This is what leads me to believe that the issue is simply caused by a client-server desync, and I assume a similar problem is what occurs with Galacticraft and GalaxySpace. I can now confirm this also happens in all dimensions added by the Dimensional Doors mod (Pocket Dimension/Limbo) as well.