How to Fix a Soulrend Server That Keeps Crashing
Soulrend is a Souls-inspired dark fantasy RPG on Forge 1.20.1, built around punishing boss fights, stamina-based combat, and an extensive loot system — with a noticeably tighter modlist than most kitchen-sink Souls-like packs. That tighter curation actually narrows down where crashes usually come from: environment setup (Java version, RAM) far more often than mod-on-mod conflicts. Here's the order worth checking before you start disabling mods.
See the Soulrend pack page for the full RAM and setup breakdown before you chase anything else.
1. Wrong Java version on boot
Forge 1.20.1 — which Soulrend runs on — requires Java 17. If the server fails to boot with a class version error, or the process exits almost immediately with no readable crash log, check which Java version is actually running the JVM before anything else. This is a universal requirement for any 1.20.1 Forge pack, not something specific to Soulrend's modlist, which is exactly why it's worth ruling out first.
- Confirm the server is launching with Java 17, not an older default on the host
- A near-instant exit with no world-load progress is a classic Java-mismatch symptom
2. Boss-fight tick spikes
Souls-like combat packs like Soulrend add custom boss AI and stamina-tracking systems that cost noticeably more per tick than vanilla mob logic, especially once multiple players are in a fight at once. If crashes cluster specifically around boss encounters rather than general world activity, this tick-cost spike is a known pattern for hardcore-combat-focused modpacks — the fight itself is pushing an already-tight server over the edge rather than causing a crash on its own.
3. General world-load or chunk-generation lag
Outside of boss fights, the next most common source of instability is ordinary lag during exploration or chunk generation — large loot structures and RPG-style dungeon content can be heavier to generate than vanilla terrain. If TPS drops gradually as players explore further from spawn, that's a resource-headroom symptom rather than a specific bug, and it compounds with the boss-fight spikes above.
4. Config corruption or a bad manual edit (less likely, but check if present)
Because Soulrend's modlist is tighter and more deliberately curated than a sprawling kitchen-sink pack, mod-to-mod conflicts are reported far less often than environment issues. If you've ruled out Java version and RAM and crashes persist, check for a corrupted or hand-edited config file — especially anything touched after a manual update or a config change made while the server was running — before assuming it's a deeper mod-interaction problem.
5. RAM under the pack's realistic floor
6 GB is the real floor for a stable Soulrend server. Under-provisioning rarely shows up as a clean, instant crash — it usually looks like creeping lag and GC pauses that get progressively worse over a session, until a heavier moment (a boss fight, several players exploring at once) finally pushes a tick past the timeout and the server crashes. If your server has been 'mostly fine' on less than 6 GB, that's often the pattern delaying rather than avoiding the problem.
FAQ
Why does my Soulrend server crash during boss fights specifically?+
Souls-like boss encounters run custom AI behavior trees and stamina-tracking logic for both the boss and nearby players, and that adds a real per-tick cost on top of normal mob processing. If your server is already running close to its RAM or CPU ceiling, a boss fight is often the moment that pushes a slow server from laggy into a full tick timeout and crash. If this only happens during fights and the server is otherwise stable, treat it as a resource headroom problem first, not a mod bug.
Do I need Java 17 for Soulrend?+
Yes. Soulrend runs on Forge for Minecraft 1.20.1, and 1.20.1 Forge servers require Java 17 — Java 8 or 11 will fail to boot or throw class version errors before the world even loads. This is one of the first things worth checking on any boot failure, since it produces symptoms that can look like a corrupted install if you don't know to look for it.
How much RAM does a Soulrend server actually need?+
6 GB is the realistic floor for a stable Soulrend server under normal play. That's the verified minimum for day-to-day stability, not a theoretical lower bound — running below it tends to show up as creeping lag and GC pauses that get worse over a session rather than an immediate crash, so a server that 'mostly works' at a lower allocation is often just delaying the problem to a worse moment, like a boss fight.
Is Soulrend crashing because of a mod conflict?+
It's less likely than with a large kitchen-sink modpack. Soulrend ships a tighter, more deliberately curated modlist than broader Souls-like packs, so most reported crashes trace back to the environment — wrong Java version or insufficient RAM — rather than two mods fighting over the same hook. Worth ruling out environment causes first before assuming a mod-interaction issue.
Host Soulrend - Dark Fantasy RPG Soulslike on hardware sized for its real floor
Give Soulrend the verified 6 GB RAM floor it actually needs, and take a backup before any config change or update — especially before a Forge or Java version bump.
View Minecraft Hosting →