All the Mods 7 - ATM7

All the Mods 7 - ATM7

3M Downloads

Error joining server: DecoderException, NullPointerException

Anaganja opened this issue ยท 17 comments

commented

I have setup a fresh server instance of ATM 0.2.45 using the "server starter". In my client, I have added Optifine, StayTrue resource pack, and a ComplementaryShaders 4.3.3. I was able to join and play fine for about an hour.

Now every time I try to connect to the server, I appear to join for a split second before being disconnected with the error, even after restarting both client and server:

Connection Lost
Internal Exception: io.netty.handler.codec.DecoderException: java.lang.NullPointerException: Cannot invoke "net.minecraft.client.multiplayer.ClientPacketListener.m_91403_()" because the return value of "net.minecraft.client.Minecraft.m_91403_()" is null

There's nothing in the server log other than "x joined the game" ... "x left the game".

The client log:

[10:37:49] [Render thread/INFO]: Connecting to example.com, 25565
[10:37:49] [Netty Client IO #2/INFO]: Read 68 traits from server
[10:37:49] [Netty Client IO #2/INFO]: Read 44 parts from server
[10:37:50] [Netty Client IO #2/INFO]: Read 118 materials from server
[10:37:51] [Render thread/INFO]: Injecting existing registry data into this CLIENT instance
[10:37:57] [Netty Client IO #2/WARN]: Updated logging config. RS Debug logging enabled: false
[10:37:57] [Netty Client IO #2/INFO]: Loading JourneyMap Forge Configs
[10:37:57] [Netty Client IO #2/INFO]: Config file changed engineersdecor-server.toml
[10:37:57] [Netty Client IO #2/INFO]: Reloading server config for tradingpost
[10:37:58] [Netty Client IO #2/INFO]: Connected to a modded server.
[10:37:58] [Netty Client IO #2/INFO]: Canceling Microsoft telemetry
[10:37:58] [Netty Client IO #2/INFO]: Injecting world-gen registry defaults
[10:37:58] [Netty Client IO #2/INFO]: Loading world-gen registry content from data
[10:37:59] [Render thread/INFO]: Environment: authHost='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', name='PROD'
[10:37:59] [Render thread/FATAL]: Error executing task on Client
java.util.NoSuchElementException: packet_handler
	at io.netty.channel.DefaultChannelPipeline.getContextOrDie(DefaultChannelPipeline.java:1073) ~[netty-all-4.1.68.Final.jar%2332!/:4.1.68.Final]
	at io.netty.channel.DefaultChannelPipeline.addBefore(DefaultChannelPipeline.java:248) ~[netty-all-4.1.68.Final.jar%2332!/:4.1.68.Final]
	at io.netty.channel.DefaultChannelPipeline.addBefore(DefaultChannelPipeline.java:237) ~[netty-all-4.1.68.Final.jar%2332!/:4.1.68.Final]
	at net.minecraftforge.network.filters.NetworkFilters.lambda$injectIfNecessary$1(NetworkFilters.java:48) ~[forge-1.18.1-39.0.88-universal.jar%23315!/:?]
	at com.google.common.collect.RegularImmutableMap.forEach(RegularImmutableMap.java:196) ~[guava-31.0.1-jre.jar%2321!/:?]
	at net.minecraftforge.network.filters.NetworkFilters.injectIfNecessary(NetworkFilters.java:44) ~[forge-1.18.1-39.0.88-universal.jar%23315!/:?]
	at net.minecraftforge.network.NetworkHooks.sendMCRegistryPackets(NetworkHooks.java:119) ~[forge-1.18.1-39.0.88-universal.jar%23315!/:?]
	at net.minecraft.client.multiplayer.ClientPacketListener.m_5998_(ClientPacketListener.java:372) ~[client-1.18.1-20211210.034407-srg.jar%23311!/:?]
	at net.minecraft.network.protocol.game.ClientboundLoginPacket.m_5797_(ClientboundLoginPacket.java:82) ~[client-1.18.1-20211210.034407-srg.jar%23311!/:?]
	at net.minecraft.network.protocol.game.ClientboundLoginPacket.m_5797_(ClientboundLoginPacket.java:18) ~[client-1.18.1-20211210.034407-srg.jar%23311!/:?]
	at net.minecraft.network.protocol.PacketUtils.lambda$checkThreadAndEnqueue$0(PacketUtils.java:38) ~[client-1.18.1-20211210.034407-srg.jar%23311!/:?]
	at net.optifine.util.PacketRunnable.run(PacketRunnable.java:28) ~[OptiFine_1.18.1_HD_U_H6.jar%23316!/:?]
	at net.minecraft.util.thread.BlockableEventLoop.m_6367_(BlockableEventLoop.java:193) ~[client-1.18.1-20211210.034407-srg.jar%23311!/:?]
	at net.minecraft.util.thread.ReentrantBlockableEventLoop.m_6367_(ReentrantBlockableEventLoop.java:23) ~[client-1.18.1-20211210.034407-srg.jar%23311!/:?]
	at net.minecraft.util.thread.BlockableEventLoop.m_7245_(BlockableEventLoop.java:158) ~[client-1.18.1-20211210.034407-srg.jar%23311!/:?]
	at net.minecraft.util.thread.BlockableEventLoop.m_18699_(BlockableEventLoop.java:135) ~[client-1.18.1-20211210.034407-srg.jar%23311!/:?]
	at net.minecraft.client.Minecraft.m_91383_(Minecraft.java:1010) ~[client-1.18.1-20211210.034407-srg.jar%23311!/:?]
	at net.minecraft.client.Minecraft.m_91374_(Minecraft.java:661) ~[client-1.18.1-20211210.034407-srg.jar%23311!/:?]
	at net.minecraft.client.main.Main.main(Main.java:205) ~[client-1.18.1-20211210.034407-srg.jar%23311!/:?]
	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.88.jar%2323!/:?]
	at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-9.1.0.jar%235!/:?]
	at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:53) [modlauncher-9.1.0.jar%235!/:?]
	at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:71) [modlauncher-9.1.0.jar%235!/:?]
	at cpw.mods.modlauncher.Launcher.run(Launcher.java:106) [modlauncher-9.1.0.jar%235!/:?]
	at cpw.mods.modlauncher.Launcher.main(Launcher.java:77) [modlauncher-9.1.0.jar%235!/:?]
	at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) [modlauncher-9.1.0.jar%235!/:?]
	at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) [modlauncher-9.1.0.jar%235!/:?]
	at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:149) [bootstraplauncher-1.0.0.jar:?]
[10:37:59] [Render thread/ERROR]: Tried to stop JEI but it is not running.
[10:37:59] [Render thread/INFO]: Removed all colony views
commented

Can confirm same stack trace and server logs on a non modified client/server. Running latest 0.3.3 on debian using openjdk 17

commented

Optifine is probably the the reason the pack crashes due to other mods that do performance optimization.
But I'm not sure.

commented

#583 seems to be a copy, doesn't look like they're using optifine either. Doubt it's related since the 3 people including myself on my server don't have optifine installed either. We just spam join till it eventually let's us in.

commented

I'm seeing this exact same issue too, both the server and client are fresh non-modified ATM-7 installed.

commented

JEI could be the problem too because it's trying to close it while it's not running. Try updating JEI https://www.curseforge.com/minecraft/mc-mods/jei/files/3737723
@NachtRaben could you paste your logs, so I can read them through too?

commented

2022-04-09-5.log
@MrLoLf
Provided is a log file with the exception encountered with no additional performance mods clientside.

commented

It says [02:22:28] [Thread-0/FATAL]: theoneprobe config just got changed on the file system! [02:22:28] [Thread-41/ERROR]: An error occurred building event handler maybe you can report the error to theoneprobe if it is not already there. Except for that error, I didn't find any other FATAL errors, and it seemed working as you joined the server. The NoSuchElementException is probably a bug in JEI as it is called when JEI is doing its stuff you can try to upgrade JEI to its newest version maybe there is already a fix for this implemented.

commented

Also having this issue, loading into single player world before going on to multiplayer fixes, very annoying and time-consuming fix though.

commented

Replicated on the latest version of Forge 1.18.1 - 39.1.2, on JDK 17. Haven't been able to host a server on Forge due to this bug. Though I have zero mods installed in replicating this. Is there an issue opened on Forge's end regarding this bug?

commented

why was this closed? its still a problem and given that it takes 8 minutes to launch the game, its pretty darn annoying

commented

I can also confirm that this is still an issue on a fresh install when it worked yesterday just fine.

commented

I have been having a similar issue (not with ATM technically, with a modpack I put together myself).
The issue seems to be with Silent Gear SilentChaos512/Silent-Gear#441

commented

had this issue aswell with ATM7. Fixed it by lowering my render distance.

commented

How long has it been fixed since you changed your render distance? Sometimes the issues fixes itself temporarily after changing settings or the like, but it usually comes back between restarts eventually. I experienced it fixing itself when I did a clean install of the pack, and then it came back after a couple of restarts of the pack.

commented

How long has it been fixed since you changed your render distance? Sometimes the issues fixes itself temporarily after changing settings or the like, but it usually comes back between restarts eventually. I experienced it fixing itself when I did a clean install of the pack, and then it came back after a couple of restarts of the pack.

The error seems to be related to the connection between you and the server. Its possibly caused by your latency and internet speed, lowering the render distance for me made the game request less information from the server and i was able to load in with no issue. Thats my take on it possibly it could be something else.

commented

The internet speed and latency have to be incredibly bad for it to be effected like it is, mine is stable and has good latency from testing (not surprising considering it's local on the same machine). Regardless, I also have a stable fiber connection, so network speed both locally and externally should not be a problem in regards to how I've set it up.

While it can be that, I doubt that is the cause. Investigating what @NightUndead mentioned might be more prudent. A friend of mine manages to connect if he simply tries over and over again, but the same doesn't always work for me, and his internet is stable, quick and doesn't have any significant changes aside from what's normal.

commented

It might be a Minecraft vanilla bug that has been fixed in 1.19.1 MC-252265 with the --server argument. If it is used in the start arguments. I haven't played the modpack for a while so I don't know about it, but it causes the user to logout because he can't load the resource pack.