How to Fix a DeceasedCraft Server That Keeps Crashing
DeceasedCraft drops players into a Forge 1.20.1 zombie apocalypse full of ruined cities, modern firearms, raidable NPC settlements, and a radioactive Wasteland endgame — all mod categories that are known to push server tick time hard. Most reported crashes and freezes trace back to a handful of well-understood causes rather than a single broken mod, and they're worth ruling out in order before you touch anything else.
See the DeceasedCraft pack page for the full RAM and setup breakdown before you chase anything else.
1. Horde AI pathing cost scaling with horde size
DeceasedCraft's core gameplay loop revolves around large zombie hordes, and every mob in that horde runs pathfinding and target-tracking logic each tick. This is the same cost pattern seen across other zombie-apocalypse packs: the bigger the horde, the more tick time it consumes, and a server that's otherwise stable at idle can fall over the moment a large horde event triggers.
- Watch whether crashes or freezes line up with horde spawns specifically rather than happening at random
- If so, treat horde size and spawn density as the first variable to investigate, not mod compatibility
2. Modern firearms adding projectile and hit-detection load
The modern-firearm mods in DeceasedCraft track projectile entities and run hit-detection logic separately from vanilla combat, and that cost is real during sustained firefights. On its own this usually isn't enough to crash a well-provisioned server, but stacked on top of an active horde or a raid, it can be the push that tips tick time over the edge.
If crashes cluster around moments where multiple players are firing into a crowd at once — rather than during quiet exploration — this combined load is a reasonable first suspect.
3. NPC settlement raid AI adding further tick cost
Raiding NPC settlements is a core DeceasedCraft activity, and the AI driving settlement defenders adds its own tick cost on top of whatever else is happening nearby. Engaging a raid while a horde is also active, or while other players are already in combat elsewhere on the map, compounds the load in a way that's easy to miss if you're only looking at one system at a time.
4. Java version mismatch on Forge 1.20.1
DeceasedCraft runs on Forge for Minecraft 1.20.1, which requires Java 17 — Forge will either refuse to start or behave unpredictably on an older Java runtime. If your crashes happen right at boot rather than during gameplay, confirming the server is actually running on Java 17 is a quick check that rules out an entire category of startup failures before you look anywhere else.
5. RAM under the pack's realistic floor
The real floor for DeceasedCraft is 8 GB. Running under that doesn't usually produce an instant, clean crash — what you'll see first is cascading lag and garbage-collection pauses as the heap fills up during a horde fight or raid, and only after the server has fallen far enough behind does it hit a tick timeout and go down. If your crashes keep happening during the most demanding moments in the game — big hordes, firefights, raids — rather than at idle, memory headroom below 8 GB is worth ruling out before anything else on this list.
FAQ
Why does my DeceasedCraft server lag or crash specifically when a horde spawns?+
Zombie-apocalypse packs like DeceasedCraft deliberately spawn large groups of hostile mobs, and each one runs its own AI pathing and target-tracking logic every tick. As horde size grows, the pathfinding cost scales with it — this is the same pattern seen in other zombie-apocalypse packs, not a bug unique to your world. If a crash or freeze consistently lines up with a horde event rather than happening randomly, horde size relative to your available CPU and RAM is the most likely cause, not a corrupted save.
Does firing modern guns a lot make crashes worse?+
It can contribute. DeceasedCraft's modern firearms add projectile entities and hit-detection logic on top of normal mob AI, so heavy combat — multiple players firing into a horde at once — stacks extra tick cost on top of whatever the mobs are already doing. If crashes cluster around big firefights specifically (not just big hordes on their own), that combined load is worth treating as its own variable when you're narrowing things down.
How much RAM does a DeceasedCraft server actually need?+
The real floor for DeceasedCraft is 8 GB. That number already accounts for the mod set's baseline memory use — it's not a conservative round-up from the catalog listing, it's the point below which the server tends to degrade under normal play rather than at idle. Running meaningfully under 8 GB doesn't reliably produce an instant clean crash; it shows up as cascading lag and GC pauses first, then a tick timeout once the server falls far enough behind.
Host DeceasedCraft on hardware sized for its real floor
DeceasedCraft's real floor is 8 GB — size the server for that and take a backup before any big config or mod change so a bad edit never costs you a world.
View Minecraft Hosting →