Posted April 9, 20232 yr Using forge 43.2.6. Using ATM 8 modpack with my own mods and my own configurations. Once the game is started up to the loading screen, the loading screen is corrupted with purple and black squares. Something, somehow broke ATM's custom loading screen. After a little bit, the game outright crashes with this report: https://gist.github.com/vainlaind4in/45aaa50c7cf632d361249c8515704d51 Here is the latest.log, if it'll help: https://gist.github.com/vainlaind4in/ee86d41dc03c2866275fa3264875a118 I've tried to look through the latest.log and the crash report to find the issue myself, but I could not find any specific mods that were causing it, and I am not a coder myself. I'm thinking it's something to do with a mod that changes rendering, or an obscure mod incompatibility. Edited April 9, 20232 yr by Bartdoytr22
April 9, 20232 yr Quote Caused by: java.lang.IllegalArgumentException: No model for layer midnight-hats:witch_hat#main at net.minecraft.client.model.geom.EntityModelSet.m_171103_(EntityModelSet.java:17) ~[client-1.19.2-20220805.130853-srg.jar%23957!/:?] {re:mixin,re:classloading,pl:rei_plugin_compatibilities:B} at eu.midnightdust.hats.witch.WitchHatFeatureRenderer.<init>(WitchHatFeatureRenderer.java:43) ~[midnightlib-forge-1.0.0.jar%23790!/:?] {re:mixin,pl:runtimedistcleaner:A,re:classloading,pl:rei_plugin_compatibilities:B,pl:runtimedistcleaner:A} Check you have the latest version then contact the mod author. 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.
April 9, 20232 yr Author Oh, right. I found a different person reporting the same issue on their GitHub just now, so I can hopefully find a fix for it. Thanks for finding it and narrowing it down for me.
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.