How to Fix a Sculk Horde Survival Server That Keeps Crashing
Sculk Horde Survival is a Forge 1.20.1 pack built around periodic waves of sculk-infected mobs attacking your base, with a tower-defense-adjacent loop of gathering resources and building defenses between waves. That wave structure is exactly what makes crashes on this pack a bit different from a typical kitchen-sink modpack: the server has to absorb a real, recurring spike in mob and entity load at a predictable moment, and a base's own defenses add more tick overhead the longer a world runs. Most of the crashes reported for this pack trace back to one of a few specific, well-understood patterns below rather than a single mystery bug.
See the Sculk Horde Survival pack page for the full RAM and setup breakdown before you chase anything else.
1. Server won't boot at all: check the Java version first
Forge on Minecraft 1.20.1 requires Java 17, and a server that was set up or migrated with an older Java runtime (8 or 11, both still common defaults on generic hosting panels) will typically fail to start before it ever reaches the point of loading a world. This is the first thing to rule out, because it produces an immediate, consistent failure rather than an intermittent one — if the server crashes the exact same way every single boot attempt with no players online yet, it's a boot-time problem, not an in-game one.
- Confirm the server is launching with Java 17, not an older version
- A boot-time crash that happens before the world loads points here, not at gameplay issues
2. Tick spikes and timeouts right as a horde wave spawns
Scheduled horde-wave mob spawns are a core, intentional mechanic of this pack, and they add a real, predictable tick-cost spike at wave time — a pattern specific to wave-based defense packs rather than a sign of a memory leak or a corrupted install. A burst of mobs spawning and path-finding toward a base all at once is genuinely expensive for the server to process in a single tick.
The distinction that matters here is whether TPS was already degraded before the wave hit, or whether the wave alone is what causes the drop. If TPS is healthy (18-20) right up until the wave spawns and only dips briefly, that's expected behavior for this pack. If TPS is already sagging well before the wave, the wave is just exposing a problem that was already there.
3. Lag that gets worse the longer a base survives
Base-defense structures and traps add their own entity and block-update overhead, and that overhead compounds as a base's defenses grow more elaborate over time. A base that was fine on day one of a world can start lagging noticeably by the time players have added multiple layers of traps, redstone-driven defenses, and larger structures — not because anything broke, but because there's simply more for the server to tick every cycle near that location.
4. Chunk loading and entity buildup around defended areas
In a pack centered on repelling waves of mobs at a fixed base location, it's common for entity counts (both mobs and dropped items/projectiles from traps) to build up in the chunks immediately around the defended area faster than in a typical survival world. If crashes or severe lag cluster specifically around the base rather than happening randomly across the map, that's a strong sign to check entity counts and consider periodic cleanup of dropped items and spent projectiles near your defenses, rather than assuming a mod conflict.
5. RAM under the pack's realistic floor
The real floor for Sculk Horde Survival is 6 GB. Under-provisioning below that doesn't usually produce an instant, clean crash — it shows up first as cascading lag and longer garbage-collection pauses as a session goes on, and that degradation then gets tipped over into an actual tick timeout the moment a horde wave or a heavily-defended base area adds its extra load on top of an already-strained heap. If crashes cluster around wave time or around a well-built base specifically, insufficient RAM headroom is worth ruling out even before touching mod configs.
FAQ
Why does my Sculk Horde Survival server crash right at wave time?+
This is almost always a tick-cost spike, not a crash in the strict sense. When a horde wave spawns, the server has to path-find, load chunks, and tick a burst of mobs all at once around the base. If the server was already running close to its TPS limit, that spike is enough to push it into a tick timeout and get kicked by the watchdog, which looks like a crash in the console but is really an overload at a predictable moment. Watch your TPS in the few seconds before a wave fires — if it's already below 15-16, the wave itself isn't the root cause, it's just the straw that breaks it.
Does Sculk Horde Survival need a specific Java version?+
Yes. This pack runs on Forge for Minecraft 1.20.1, which requires Java 17. Running it on an older Java runtime (8 or 11) is one of the most common causes of a server that fails to boot at all rather than crashing mid-game, so it's worth confirming the Java version first before digging into anything else, especially after a host migration or a manual server setup.
How much RAM does Sculk Horde Survival actually need?+
The real floor for a stable server is 6 GB. That's higher than what a quick glance at a generic modpack RAM calculator might suggest, because the horde-wave spawning and the cumulative overhead of player-built defenses both create short, intense memory and CPU demand on top of the pack's base footprint. Running below that floor doesn't always crash cleanly — it more often shows up as rising lag and GC pauses that build over a session until a wave or a big build push finally tips it into a tick timeout.
Host Sculk Horde Survival on hardware sized for its real floor
Sculk Horde Survival needs a real 6 GB floor to absorb horde-wave spikes without tipping into a tick timeout, and taking a backup before any risky config change keeps a bad edit from costing you a world.
View Minecraft Hosting →