Posted September 3, 20223 yr hosting a custom pack server for some people, only me and one other person are getting this problem currently. after disconnecting from the server for any reason, the first reconnect gets as far as "loading world" then displays the error: "Internal Exception: io.netty.handler.codec.DecoderException: java.lang.NullPointerException: Cannot invoke 'net.minecraft.client.multiplayer.ClientPacketListener.m_6198_()" because the return value of "net.minecraft.client.Minecraft.m_91403_()" is null' after getting this error, further attempts to connect just result in the connection timing out. the client is able to reconnect after a server restart, but having to restart the server any time i want to reconnect is terrible. restarting the client does not help. log snip: https://pastebin.com/g4sANJmc no real idea what mod is causing the problem at this point. minecraft version: 1.18.2 modpack: https://www.curseforge.com/minecraft/modpacks/bread-bank-3 Forge: 40.1.74 launcher: multimc lwjgl 3 version: 3.2.2 java: 18.0.2.1
September 3, 20223 yr Please add -Dforge.logging.mojang.level=debug to the JVM arguments of your Launcher. Launch the game and produce the error, then post debug.log from the logs folder. Vanilla Laucnher: Launcher -> Installations -> Edit the Forge Profile you are using -> More Options -> Add the Argument to the JVM Arguments If you using CurseForge you need to enable the debug.log in the settings.
September 4, 20223 yr Author here is a debug snippet after successfully joining the server and disconnecting: https://pastebin.com/HdufhZAS and here is a debug snippet when trying to reconnect to the server: https://pastebin.com/JPqssXpx
September 4, 20223 yr Please post full debug.log from server and client. You can use https://gist.github.com/ to upload larger text files. Edited September 4, 20223 yr by Luis_ST
September 4, 20223 yr Author i tried multiple times to upload the full log before, i either get a 'too big' error, or in githubs case just completely crash the page. just me launching the game, failing to connect to the server and quiting makes a debug log that is 600k lines.
September 4, 20223 yr You can upload the file to google drive or similar pages. If the log file is still too large, put it into a .zip file.
September 4, 20223 yr Author google drive ling for debug.log: https://drive.google.com/file/d/1Z_lnkZryAxn3C4bx5e4YzFLRYNmw2gv1/view?usp=sharing
September 4, 20223 yr Unfortunately i have no idea, the only thing i can tell you is that at least one Mod is badly coded. To avoid a lot of work, make sure all Mods you use are up to date.
September 12, 20223 yr Author was finally able to update the server, still get this issue. it let me reconnect a few times without this happening, so its not every time, but it still happens sometimes.
October 1, 20223 yr As was said above. The error says one of your mods has badly coded network code. The error does not say which one. The only way to find it, is to experiment with removing mods until you find the problem mod. (Backup your world before removing mods). NOTE: I am assuming you are still getting the same error after doing your update, because you don't post an updated log. Boilerplate: If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one. If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install Large files should be posted to a file sharing site like https://gist.github.com You should also read the support forum sticky post.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.