Troubleshooting

❓ Troubleshooting & Crash Guide

Follow the steps below to diagnose and resolve crashes, connection errors, or performance problems with the modpack.

---

🔍 Step 1: Check Your Crash Logs (Memory Checks)

Most unexpected client crashes during loading or chunk rendering are caused by insufficient RAM allocation.

1. Navigate to your modpack instance directory and open logs/latest.log or the newest file inside the crash-reports/ folder.
2. Search (Ctrl + F) for the following errors:
   • java.lang.OutOfMemoryError
   • Exit Code: -805306369 (or Exit Code: 1 with memory warnings)
3. Fix: Open your launcher's instance settings and increase your allocated RAM to 6 GB – 8 GB.

---

🤖 Step 2: Use the Auto Troubleshooter

If your log does not indicate a memory error or you cannot determine the cause:

1. Copy the full contents of your latest.log or crash report.
2. Paste it into the automated diagnostic tool: ModResolve Auto Troubleshooter.
3. Follow the specific recommendations or mod-conflict fixes generated by the scanner.

---

🔄 Step 3: Clean Reinstallation

Corrupted configs, outdated cached files, or failed auto-updates can cause persistent crashes.

1. Back up your saves/, screenshots/, and options.txt files if desired.
2. Delete or create a fresh instance of the modpack.
3. Follow the step-by-step setup in the Installation Guide to reinstall the pack cleanly and re-enter your verification key.

---

📝 Step 4: Open a GitHub Issue

If the issue persists after attempting the steps above:

1. Head over to our GitHub Issue Tracker.
2. Click New Issue and describe:
   • What you were doing when the crash/error occurred.
   • What troubleshooting steps you have already tried.
3. Upload your full crash-report or paste a link from a paste service (e.g., Pastebin or mclo.gs).