Many chunks in The Other not loading clientside
SuperKael opened this issue ยท 1 comments
I just updated my client and dedicated server from version 0.2.30 to 0.2.34, and now many chunks in The Other (Nether) dimension are not loading clientside. It is clear they are loaded on the server for various reasons, but they do not appear on the client. Unfortunately, my teleport pad is in one of the missing chunks, and I have no means of inter-dimensional teleportation, so I am effectively trapped here unless I die or cheat out somehow. It is hard to say for sure, but it seems like the issue might be localized to the Soul Sand Valley Region biome? As in, chunks that overlap with that biome won't load, while others do.
I suspect it to be related to/caused by this error, which is being spammed constantly in my client log file (There are no errors on the server side):
[01:50:57] [Render thread/FATAL]: Error executing task on Client
java.lang.IllegalArgumentException: No value with id 173
at net.minecraft.core.IdMap.m_200957_(IdMap.java:19) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.world.level.chunk.SingleValuePalette.m_5680_(SingleValuePalette.java:57) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.world.level.chunk.PalettedContainer.m_63118_(PalettedContainer.java:150) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.world.level.chunk.LevelChunkSection.m_63004_(LevelChunkSection.java:158) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.world.level.chunk.LevelChunk.m_187971_(LevelChunk.java:431) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.client.multiplayer.ClientChunkCache.m_194116_(ClientChunkCache.java:96) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.client.multiplayer.ClientPacketListener.m_194198_(ClientPacketListener.java:607) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.client.multiplayer.ClientPacketListener.m_183388_(ClientPacketListener.java:602) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.network.protocol.game.ClientboundLevelChunkWithLightPacket.m_5797_(ClientboundLevelChunkWithLightPacket.java:45) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.network.protocol.game.ClientboundLevelChunkWithLightPacket.m_5797_(ClientboundLevelChunkWithLightPacket.java:12) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.network.protocol.PacketUtils.m_131356_(PacketUtils.java:21) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.util.thread.BlockableEventLoop.m_6367_(BlockableEventLoop.java:151) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.util.thread.ReentrantBlockableEventLoop.m_6367_(ReentrantBlockableEventLoop.java:23) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.util.thread.BlockableEventLoop.m_7245_(BlockableEventLoop.java:125) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.util.thread.BlockableEventLoop.m_18699_(BlockableEventLoop.java:110) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.client.Minecraft.m_91383_(Minecraft.java:1009) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.client.Minecraft.m_91374_(Minecraft.java:660) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at net.minecraft.client.main.Main.main(Main.java:205) ~[client-1.18.1-20211210.034407-srg.jar%23281!:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
at net.minecraftforge.fml.loading.targets.CommonClientLaunchHandler.lambda$launchService$0(CommonClientLaunchHandler.java:45) ~[fmlloader-1.18.1-39.0.43.jar%2323!:?]
at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-9.0.7.jar%235!:?]
at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:53) [modlauncher-9.0.7.jar%235!:?]
at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:71) [modlauncher-9.0.7.jar%235!:?]
at cpw.mods.modlauncher.Launcher.run(Launcher.java:106) [modlauncher-9.0.7.jar%235!:?]
at cpw.mods.modlauncher.Launcher.main(Launcher.java:77) [modlauncher-9.0.7.jar%235!:?]
at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) [modlauncher-9.0.7.jar%235!:?]
at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) [modlauncher-9.0.7.jar%235!:?]
at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:90) [bootstraplauncher-0.1.17.jar:?]
I have determined that this was caused by many of the biome IDs becoming scrambled somehow. I am not sure if the update caused this, or if it was some form of save corruption. Either way, by generating a new world and then manually replacing my server's biome registry with the one from the new world, the issue was resolved.