![]() ![]() Do the same for the latest crash report if available. Share the link to it when making a new support thread. Go to or and paste the debug.log there. If there's no crash reports in that folder, don't worry about it. We can still help as long as we have the debug.log. Right click the modpack you're having trouble withĬrash reports are in the crash-reports folder - the latest one will do Now how to get the debug.log and latest crash report: ![]() You'll need to start the game again to make the log Open the CurseForge app and click the cog on the bottom leftĬlick the Minecraft tab on the right, scroll down and turn on the "Enable Forge debug.log", then click the X near the top to save The CurseForge app disables the debug.log by default, so we need to turn it back on in the settings: Where can I find the debug.log and crash report? Here's a list of exit codes and what they mean:Įrror code 0: Someone clicked "Quit game" and the game closed successfullyĮrror code 1 and -1: The game crashed, refer to the log and/or crash report for details Instructions on where to find this and how to upload it are in this forum post. When making a new thread, you must include a link to your log on or. When you need help, please always make a new thread. Piracy (aka "cracked launchers") and cheats (aka "PvP clients", "x-ray mods", etc.) are strictly forbidden here. There is limited support for older versions - we'll help you if your issue is trivial and quick to answer, but you should consider upgrading to a modern version for full support as most of the time your thread will probably be locked. The grey "Currently supported" banner near the top of all forum pages shows the versions we support.Ĭurrently this is MC 1.20.1, 1.19.4 and 1.19.2. We cannot help you with Fabric, Spigot, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |