Most modded crashes aren't corrupted files, they're RAM. Match your plan to your pack's mod count before troubleshooting anything else.
How much you actually need
- Light packs (under 100 mods): 4-6 GB
- Mid-size packs: 6-8 GB
- Heavy packs (300+ mods): 8-12 GB
Treat your modpack's listed "minimum" as a floor, not a target, actual usage climbs once players join and chunks load.
How to fix a RAM-related crash
- Open Server Properties and set view-distance and simulation-distance to 10-18. Never leave these at 32, that alone can max out memory regardless of plan size.
- Restart, then watch the memory counter at the top of the page. If it sits near your limit with only a few players online, you need more RAM.
- Check Server Type to confirm you're on one mod loader only, mixing Fabric and Forge mods causes crashes independent of RAM.
- Upgrade RAM from your plan settings if needed, then restart to apply it.
- Add a daily restart in Schedules to clear accumulated memory, this reduces crash frequency even on a correctly-sized plan.
Running 300+ mods? Rule out RAM first. Undersized RAM on heavy packs causes crashes that look identical to mod conflicts.
Still stuck?
Right-sized RAM, lowered view distance, still won't start: check Console for the actual error, see How to Read the Crash Log.
Error mentions a specific mod or dependency: see Fix "Missing Dependency" and Mod Conflict Errors.
Still crashing after all this: open a support ticket with your mod list and Console output, we can confirm the real RAM ceiling your pack needs.
Did this solve it?
If you are still stuck, our team can look at your server directly.