August 14, 20232 yr My suggestion since its 1.16.5 and no one will help try getting a new modpack and slowly add mods and load the game till you find the issue Edited August 14, 20232 yr by TaxEvader
August 14, 20232 yr Those logs do not look complete, they look as though they've been cut off. That second log doesn't even have a crash in it. When you have a lot of things and need to find the one(s) that are problematic, there's a method for doing it that's easier than 1 by 1: Remove half of the existing things, and put them aside. Run the program / game. Does the issue still exist? If YES: Repeat from step 1 with the current things. IF NO: Swap out the current things with the ones set aside, and repeat from step 1. Repeat this process until the problematic thing/s have been found.
August 14, 20232 yr With a log that short, the error message is likely in the launcher_log.txt 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.