How to Fix a Horror Craft Server That Keeps Crashing
Horror Craft is a curated horror experience on Forge 1.20.1 — a smaller, hand-picked roster of horror mods chosen for compatibility and scare quality over sheer quantity, which deliberately avoids conflicting mob spawns and broken encounters. That curation means most crash reports for this pack don't come from mods fighting each other; they come from the environment around the pack — the Java version it's launched with, or RAM provisioned below its real floor.
See the Horror Craft pack page for the full RAM and setup breakdown before you chase anything else.
1. Wrong Java version on boot
Forge on Minecraft 1.20.1 requires Java 17 — this is a well-established requirement across the entire 1.20.1 Forge ecosystem, not something specific to Horror Craft's mod list. If the server refuses to boot, exits instantly, or throws an UnsupportedClassVersionError before the world even starts loading, this is the first thing to check. Running Java 8 or Java 16 against a 1.20.1 Forge pack is one of the most-reported causes of an instant, clean-looking failure that has nothing to do with the mods themselves.
- Confirm the server is launching with Java 17, not an older or newer JDK
- Check this before touching configs or mod files — it rules out an entire class of boot failures in one step
2. RAM provisioned below the real floor
Because Horror Craft is a smaller, curated pack rather than a massive tech or kitchen-sink stack, it's tempting to assume it needs less memory than a heavier modpack. In practice the floor for reliable operation is still higher than a vanilla server needs, and running it tighter than that floor is a common source of slow, creeping instability rather than a clean one-time crash.
3. Scripted horror-event CPU spikes stacking with other load
Horror Craft's event-driven scares — ambient triggers, jumpscares, mob behavior changes — cause short CPU spikes when they fire, and that's a normal part of how this category of pack works rather than evidence of a leak. The problem shows up when those spikes land on a server that's already close to its ceiling: a brief spike that would be harmless on a well-provisioned server can be the push that causes a tick timeout on one that's already tight on headroom.
4. Config or save corruption after an unclean shutdown
Because Horror Craft's roster is small and deliberately chosen for compatibility, outright mod-vs-mod conflicts are less common here than on sprawling packs. A more realistic cause of repeat crashes on restart is a world save or mod config that got corrupted during an earlier unclean shutdown (e.g. the process being killed mid-save rather than stopped cleanly). If crashes started after a forced restart or power interruption rather than happening from a fresh install, a corrupted save is a more plausible lead than a mod conflict.
5. RAM under the pack's realistic floor
The real floor for a reliable Horror Craft server is 5 GB. Under-provisioning below that doesn't usually show up as an instant, clean crash — what it actually looks like is cascading lag as garbage collection pauses get longer and more frequent under load, eventually tipping into a tick timeout once a scripted horror event or a few players loading new chunks pushes memory pressure past what's available. If your server is slowing down for a few seconds at a time before it finally drops, check allocated RAM against the 5 GB floor before assuming it's a mod bug.
FAQ
What's the single most common cause of a Horror Craft server crashing right at boot?+
A Java version mismatch. Horror Craft runs on Forge for Minecraft 1.20.1, which requires Java 17 — not Java 8 or 16. If the server fails almost immediately with no world load at all, check the Java version your host is launching with before looking at anything else.
If Horror Craft only has a small, curated mod list, why does it still crash?+
Because it's a smaller, hand-picked roster rather than a sprawling kitchen-sink pack, most crashes trace back to the environment — wrong Java version or insufficient RAM — rather than mods actively conflicting with each other. The curation reduces mod-interaction risk but doesn't remove the need to size the server correctly.
Is a CPU spike when a horror event triggers a sign something is wrong?+
Not on its own. Scripted horror-event triggers (jumpscares, ambient sequences, mob behavior changes) are event-driven and cause a brief CPU spike when they fire — that's normal for this kind of pack. It only becomes a problem if the server is already running close to its RAM ceiling and the spike is what tips it into a tick timeout or crash.
Host Horror Craft on hardware sized for its real floor
Horror Craft needs at least 5 GB of RAM to run reliably, and taking a backup before any config change or Forge version bump is the single habit that turns a bad crash into a two-minute rollback instead of a lost world.
View Minecraft Hosting →