The Graveyard (FORGE/NEOFORGE)

The Graveyard (FORGE/NEOFORGE)

16M Downloads

The Graveyard breaks Distant Horizon server side LOD generation

johalun opened this issue · 0 comments

commented

Hi

Distant Horizons 2.0.4 for 1.20.1 has a fork that enables server side rendering, where the server generates the LOD data and sends it to the client. This fork is available in their Discord. After a lot of bisecting and testing with our mod pack, I found that The Graveyard mod breaks this functionality. When this mod is installed DH logs error regarding unhandled messages, which I assume is DH on the server, talking to the client. When I removed this mod from our pack, DH works as expected and the client receives and renders the LODs.

This was confirmed with a minimal pack containing for both client and server

  • Minecraft 1.20.1
  • Distant horizons 2.0.4 (server rendering fork)
  • Geckolib 4.4.4
  • The Graveyard 3.1
  • Forge 47.2.30

Relevant snippet from client log

[12:42:21] [DH-Network - Client Thread-2-1/WARN] [co.se.di.co.ne.NetworkEventSource/]: Unhandled message: ExceptionMessage{futureId=64, exception=com.seibel.distanthorizons.core.network.exceptions.InvalidLevelException: Generation not allowed. Requested dimension: overworld, player dimension: overworld}
[12:42:21] [DH-Network - Client Thread-2-1/INFO] [minecraft/ChatComponent]: [System] [CHAT] [Distant Horizons] §uWARN: Unhandled message: ExceptionMessage{futureId=64, exception=com.seibel.distanthorizons.core.network.exceptions.InvalidLevelException: Generation not allowed. Requested dimension: overworld, player dimension: overworld}
[12:42:21] [DH-Network - Client Thread-2-1/WARN] [co.se.di.co.ne.NetworkEventSource/]: Unhandled message: ExceptionMessage{futureId=65, exception=com.seibel.distanthorizons.core.network.exceptions.InvalidLevelException: Generation not allowed. Requested dimension: overworld, player dimension: overworld}

and server log

[12:42:21] [DH-Network - Server Worker Thread-3-1/ERROR] [co.se.di.co.ne.pr.ne.NettyMessageHandler/]: Exception caught in channel: [NettyMessageHandler#0].
io.netty.channel.StacklessClosedChannelException: null
	at io.netty.channel.AbstractChannel.close(ChannelPromise)(Unknown Source) ~[netty-transport-4.1.82.Final.jar%2385!/:4.1.82.Final] {}
[12:42:21] [DH-Network - Server Worker Thread-3-1/ERROR] [co.se.di.co.ne.pr.ne.NettyMessageHandler/]: Exception caught in channel: [NettyMessageHandler#0].
io.netty.channel.StacklessClosedChannelException: null
	at io.netty.channel.AbstractChannel.close(ChannelPromise)(Unknown Source) ~[netty-transport-4.1.82.Final.jar%2385!/:4.1.82.Final] {}
[12:42:21] [DH-Network - Server Worker Thread-3-1/ERROR] [co.se.di.co.ne.pr.ne.NettyMessageHandler/]: Exception caught in channel: [NettyMessageHandler#0].
io.netty.channel.StacklessClosedChannelException: null
	at io.netty.channel.AbstractChannel.close(ChannelPromise)(Unknown Source) ~[netty-transport-4.1.82.Final.jar%2385!/:4.1.82.Final] {}
[12:42:21] [DH-Network - Server Worker Thread-3-1/ERROR] [co.se.di.co.ne.pr.ne.NettyMessageHandler/]: Exception caught in channel: [NettyMessageHandler#0].
io.netty.channel.StacklessClosedChannelException: null
	at io.netty.channel.AbstractChannel.close(ChannelPromise)(Unknown Source) ~[netty-transport-4.1.82.Final.jar%2385!/:4.1.82.Final] {}

I don't know if this is a The Graveyard or Distant Horizons issue but out of 240 mods this was the only one causing issues. Would appreciate if you could take a look. We'd really like to include The Graveyard in our pack but currently we can't.

Thanks!