How to Fix a Biohazard: Project Genesis Server That Keeps Crashing
Biohazard: Project Genesis is a Forge 1.20.1 zombie-apocalypse RPG pack — players explore a broken world, fight infected hordes, scavenge, and build up bases, which means both combat AI load and accumulating world state put real pressure on a server. Most crash and lag reports trace back to one of a handful of well-known patterns: a Java version mismatch, horde AI cost during fights, or save/tick cost creeping up as bases and loot containers pile up. This guide walks through each in order of how often they actually show up.
See the Biohazard: Project Genesis pack page for the full RAM and setup breakdown before you chase anything else.
1. Wrong Java version at launch
Forge 1.20.1 requires Java 17 — this is a universal requirement for any 1.20.1 Forge pack, not specific to Biohazard. If your launch script, panel, or systemd unit is still pointed at an older Java install (common after a host migration or manual setup), the server will fail to boot or crash almost immediately with a JVM-level error rather than loading into the world. This is the first thing to rule out before assuming a mod conflict.
- Check `java -version` in the exact context the server launches from, not just your shell
- Confirm the start script's java path matches a Java 17 (or newer, if the pack explicitly supports it) binary
2. Crashes or freezes during large infected hordes
Horde-based zombie-apocalypse packs put real AI pathing and tracking cost on the server, and that cost scales directly with horde size — this is a well-known pattern across the mod category, not unique to this pack. If lag spikes or watchdog crashes line up with hordes spawning, converging on a player base, or a horde event triggering, that's horde AI load rather than a corrupted install.
Watch TPS specifically during horde events versus normal exploration — a sharp drop only during hordes points straight at AI cost, and reducing mob/horde density settings (where the pack exposes them) is the usual mitigation.
3. Gradual slowdown as the world ages
Because this pack is built around scavenging, looting, and building, player bases and loot containers accumulate as world state over time. That steadily raises both autosave duration and per-tick cost — a server that felt fine in its first week can start showing longer autosave stalls or occasional tick timeouts weeks later purely from world growth, with no new mods or config changes involved.
4. Mod conflicts and config corruption on an apocalypse-RPG pack
Packs that layer RPG progression, exploration, and survival-horror systems on top of each other carry more interacting mod configs than a typical kitchen-sink pack, which raises the odds of a config edit or a partial update leaving one mod in a broken state. If a crash started right after you changed a config value or updated a single mod rather than the whole pack, roll that specific change back first rather than reinstalling everything.
5. RAM under the pack's realistic floor
10 GB is the real floor for Biohazard: Project Genesis in multiplayer, not a generic modpack guess. Under-provisioning below that doesn't usually produce an instant, clean crash — it shows up first as cascading lag and longer GC pauses under horde or world-save load, and only escalates to a hard tick-timeout or watchdog crash once garbage collection can no longer keep up. If your crashes correlate with horde events or autosave rather than a specific action, check allocated RAM against that 10 GB floor before anything else.
FAQ
Why does my Biohazard: Project Genesis server crash right at startup?+
The most common startup-crash cause is running Forge 1.20.1 on the wrong Java version — this pack requires Java 17, and launching it with Java 8 or Java 11 will fail to even boot, usually with a JVM or class-version error before the world loads. Double-check your launch script's java binary points at a Java 17 install before looking anywhere else.
Why does the server freeze or lag badly during zombie hordes?+
Large infected hordes are AI- and pathing-heavy, and the cost scales with horde size — this is the same pattern seen in other zombie-apocalypse packs. If TPS drops hard specifically when a horde spawns or converges on a base, that's horde AI tracking cost, not a crash bug. Reducing mob caps or horde density in the config (if the pack exposes it) is the usual fix, not more RAM alone.
Why does my server get slower and crash more the longer it's been running?+
Biohazard: Project Genesis is an RPG-style scavenging and building pack, so player bases and loot containers accumulate world state over time. That raises both save time and per-tick cost as the world ages, which is why a server that ran fine in week one can start lagging or timing out on autosave by week four. Regular backups before any risky change (updates, config edits) matter here specifically because of that growing save cost.
What's the real RAM floor for Biohazard: Project Genesis?+
10 GB is the verified floor for a smooth multiplayer server. Going under that doesn't usually produce a clean out-of-memory crash — it shows up first as cascading lag and GC pauses, then eventually a tick timeout or watchdog crash once garbage collection can't keep up with horde AI and world-state load.
Host Biohazard: Project Genesis on hardware sized for its real floor
Biohazard: Project Genesis needs a real 10 GB RAM floor to handle horde AI and growing world state without cascading lag — pair that with backups taken before any config change or update so a bad edit never costs you progress.
View Minecraft Hosting →