Athensguy Posted August 10, 2022 Posted August 10, 2022 (edited) I'm trying to connect to one of my friends modded server (1.19.1) but everytime I click connect this error comes up [ Internal Exception: io.netty.handler.codec.DecoderException: java.lang.IndexOutOfBoundsException: readerIndex(27) + length(1) exceeds writerIndex(27): PooledUnsafeDirectByteBuf(ridx: 27, widx: 27, cap: 27)]. The weird thing is before swapping to my current PC I was able to play just fine on a different computer but after swapping I can't seem to join at all while my other friends are able to join just fine. Here's my debug.log (https://pastebin.com/6jV4VLtp). Any help would be nice, if I need to give more files lmk . Edited August 10, 2022 by Athensguy Quote
rochinchi Posted August 26, 2022 Posted August 26, 2022 Hi, do you fixed it? I also get the same problem Quote
Luis_ST Posted August 27, 2022 Posted August 27, 2022 10 hours ago, rochinchi said: Hi, do you fixed it? I also get the same problem 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 in your own thread (create your own thread). Quote
Luis_ST Posted August 27, 2022 Posted August 27, 2022 (edited) @AthensguyPlease add -Dforge.logging.mojang.level=debug to the JVM arguments of your Launcher. Launch the game and produce the error, then post updated debug.log. Edited August 27, 2022 by Luis_ST highlight JVM argument Quote
Lepton Posted August 28, 2022 Posted August 28, 2022 27.08.2022 в 10:08, Luis_ST сказал: @AthensguyПожалуйста, добавьте -Dforge.logging.mojang.level=debug к аргументам вашего JVM Launcher. Запустите игру и выдайте ошибку, затем опубликуйте обновленный файл debug.log. good afternoon, can you please clarify what needs to be done. I added an argument to my minecraft but nothing changed Quote
warjort Posted August 28, 2022 Posted August 28, 2022 The output of the logs will change. Please post the new logs. Quote 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.
warjort Posted August 28, 2022 Posted August 28, 2022 And do it on your own thread. Quote 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.
rochinchi Posted August 29, 2022 Posted August 29, 2022 On 8/27/2022 at 3:07 AM, Luis_ST said: 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 in your own thread (create your own thread). Ok, but how do I do that? Quote
Luis_ST Posted August 30, 2022 Posted August 30, 2022 6 hours ago, rochinchi said: Ok, but how do I do that? Launcher -> Installations -> edit the Forge Profile -> More Options -> Add the Argument to the JVM Arguments Quote
Recommended Posts
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.