[1.20.4] can not join server
MSandro opened this issue · 6 comments
Minecraft Version
1.20.4
Mod Loader
NeoForge
Mod Loader Version
20.4.227
Mod Version
16.0.5
Balm Version
9.0.7
Describe the Issue
I can not join on a server.
Logs
[11:15:28] [Server thread/INFO] [minecraft/MinecraftServer]: MSandro joined the game
[11:15:28] [Netty Epoll Server IO #4/ERROR] [minecraft/Connection]: Exception caught in connection
io.netty.handler.codec.EncoderException: java.lang.ClassCastException: class java.lang.String cannot be cast to class java.lang.Enum (java.lang.String and java.lang.Enum are in module java.base of loader 'bootstrap')
at io.netty.handler.codec.MessageToMessageEncoder.write(MessageToMessageEncoder.java:107) ~[netty-codec-4.1.97.Final.jar%23108!/:4.1.97.Final] {}
at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:881) ~[netty-transport-4.1.97.Final.jar%23112!/:4.1.97.Final] {}
at io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:940) ~[netty-transport-4.1.97.Final.jar%23112!/:4.1.97.Final] {}
at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:966) ~[netty-transport-4.1.97.Final.jar%23112!/:4.1.97.Final] {}
at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:934) ~[netty-transport-4.1.97.Final.jar%23112!/:4.1.97.Final] {}
at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:984) ~[netty-transport-4.1.97.Final.jar%23112!/:4.1.97.Final] {}
at io.netty.channel.DefaultChannelPipeline.writeAndFlush(DefaultChannelPipeline.java:1025) ~[netty-transport-4.1.97.Final.jar%23112!/:4.1.97.Final] {}
at io.netty.channel.AbstractChannel.writeAndFlush(AbstractChannel.java:306) ~[netty-transport-4.1.97.Final.jar%23112!/:4.1.97.Final] {}
at net.minecraft.network.Connection.doSendPacket(Connection.java:302) ~[server-1.20.4-20231207.154220-srg.jar%23142!/:?] {re:classloading,re:mixin}
at net.minecraft.network.Connection.lambda$sendPacket$9(Connection.java:297) ~[server-1.20.4-20231207.154220-srg.jar%23142!/:?] {re:classloading,re:mixin}
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174) ~[netty-common-4.1.97.Final.jar%23109!/:4.1.97.Final] {}
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167) ~[netty-common-4.1.97.Final.jar%23109!/:4.1.97.Final] {}
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) ~[netty-common-4.1.97.Final.jar%23109!/:4.1.97.Final] {}
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:413) ~[netty-transport-classes-epoll-4.1.97.Final.jar%23113!/:4.1.97.Final] {}
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.97.Final.jar%23109!/:4.1.97.Final] {}
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.97.Final.jar%23109!/:4.1.97.Final] {}
at java.lang.Thread.run(Thread.java:1583) ~[?:?] {}
Caused by: java.lang.ClassCastException: class java.lang.String cannot be cast to class java.lang.Enum (java.lang.String and java.lang.Enum are in module java.base of loader 'bootstrap')
at net.blay09.mods.balm.api.network.SyncConfigMessage.writeValue(SyncConfigMessage.java:126) ~[balm-neoforge-1.20.4-9.0.7.jar%23132!/:9.0.7] {re:classloading}
at net.blay09.mods.balm.api.network.SyncConfigMessage.writeValue(SyncConfigMessage.java:147) ~[balm-neoforge-1.20.4-9.0.7.jar%23132!/:9.0.7] {re:classloading}
at net.blay09.mods.balm.api.network.SyncConfigMessage.writeSyncedFields(SyncConfigMessage.java:113) ~[balm-neoforge-1.20.4-9.0.7.jar%23132!/:9.0.7] {re:classloading}
at net.blay09.mods.balm.api.network.SyncConfigMessage.writeValue(SyncConfigMessage.java:150) ~[balm-neoforge-1.20.4-9.0.7.jar%23132!/:9.0.7] {re:classloading}
at net.blay09.mods.balm.api.network.SyncConfigMessage.writeSyncedFields(SyncConfigMessage.java:113) ~[balm-neoforge-1.20.4-9.0.7.jar%23132!/:9.0.7] {re:classloading}
at net.blay09.mods.balm.api.network.SyncConfigMessage.lambda$register$4(SyncConfigMessage.java:162) ~[balm-neoforge-1.20.4-9.0.7.jar%23132!/:9.0.7] {re:classloading}
at net.blay09.mods.balm.neoforge.network.NeoForgeBalmNetworking$WrappedPacket.write(NeoForgeBalmNetworking.java:47) ~[balm-neoforge-1.20.4-9.0.7.jar%23132!/:9.0.7] {re:classloading}
at net.minecraft.network.protocol.common.ClientboundCustomPayloadPacket.write(ClientboundCustomPayloadPacket.java:111) ~[server-1.20.4-20231207.154220-srg.jar%23142!/:?] {re:classloading,pl:accesstransformer:B}
at net.neoforged.neoforge.network.filters.GenericPacketSplitter.encode(GenericPacketSplitter.java:107) ~[neoforge-20.4.227-universal.jar%23143!/:?] {re:classloading}
at net.neoforged.neoforge.network.filters.GenericPacketSplitter.encode(GenericPacketSplitter.java:45) ~[neoforge-20.4.227-universal.jar%23143!/:?] {re:classloading}
at io.netty.handler.codec.MessageToMessageEncoder.write(MessageToMessageEncoder.java:90) ~[netty-codec-4.1.97.Final.jar%23108!/:4.1.97.Final] {}
... 16 more
Do you use any performance-enhancing mods (e.g. OptiFine) or custom server distributions (e.g. SpongeForge)?
no
Please provide the full logs of both client and server when the issue occurs. This is most likely a version mismatch issue, as I can't reproduce the issue otherwise.
You can find the logs in the logs directory of the client or server. Most of the time latest.log is the correct file (unless the crash or issue happened during an earlier run).
Logs can be uploaded here by dragging the file into the comment field, or you can post them on a site like https://gist.github.com/ or https://pastebin.com/. Make sure they are set to be public (or unlisted) and to never expire.
Have you installed the same version on both the server and the client? I was getting this same error when I forgot to update the version on the server. I also forgot to update balm and got an index out of bounds error.
Would just like to +1 to this. This does indeed seem to happen with this version of Balm and Waystones on NeoForge. Once you downgrade Waystones to 16.0.4 and Balm to 9.0.6 you can indeed connect to the Dedicated Server. As for the logs the message is the exact same as above and it occurs as soon as the player is attempting to login. Then is followed by a simple Player Disconnected message in the logs.
