How to Fix an Endless Horror Server That Keeps Crashing
Endless Horror packs nearly every horror mod available into a single Forge 1.19.2 pack, layered with shaders and content mods to keep every playthrough feeling different. That same density is what makes it fragile to run — a lot of mods each adding their own stalking or jumpscare logic, on a Forge version with its own Java requirements, leaves several ways for a server to crash or freeze if it isn't set up and provisioned correctly.
See the Endless Horror pack page for the full RAM and setup breakdown before you chase anything else.
1. Wrong Java version for Forge 1.19.2
Endless Horror runs on Forge for Minecraft 1.19.2, which requires Java 17. If your server process is still pinned to Java 8 or Java 11 — common defaults left over from older Forge modpacks — the server will fail to boot entirely or crash almost immediately with a class version mismatch error. This is the first thing to check if the server won't even reach the world-loading stage.
- Confirm the server's Java runtime is Java 17, not an older version
- Check your host or launcher's Java version setting wasn't inherited from a different pack
2. Stacked horror-mod AI overwhelming the tick loop
The core design of Endless Horror is combining nearly every horror mod into one pack, and each of those mods ships its own mob-tracking, stalking, or jumpscare-trigger system running every tick. Any single one of these is typically well-optimized on its own, but running many of them together compounds the per-tick cost of target tracking far beyond what one mod alone would produce.
This stacking effect gets worse the more horror mods are actively triggered at once — for example, several players spread across different areas each triggering a different mod's stalking entity in the same tick window. That's a common cause of growing server lag that doesn't trace back to any single mod being broken.
3. Lag spikes escalating into a tick timeout crash
When the stacked AI load above gets heavy enough, the symptom usually isn't an instant crash — it's the tick loop falling behind, visible as rubber-banding and delayed mob behavior, which can then escalate into a full watchdog tick timeout if the server can't catch up. If you're seeing lag that builds over a session and eventually ends in a crash, this compounding AI cost across multiple horror mods is a strong first suspect before you look at any single mod's config.
4. Client-side shader crashes mistaken for server crashes
Endless Horror bundles shaders for atmosphere, but shaders are a client-side setting — they run on each player's machine, not the server. If one player's game crashes or freezes while the server and everyone else stays online, that's almost always a client-side shader or client-mod configuration issue specific to that player's hardware, not a server problem. Rule this out first before digging into server logs for a crash that's really only happening on one client.
5. RAM under the pack's realistic floor
The real floor for Endless Horror is 8 GB. Under-provisioning below that rarely causes a clean, instant crash — instead you'll see cascading lag and garbage collection pauses build up as more horror mods' AI systems activate and the heap comes under pressure, which then tips over into a tick timeout once the server can't recover between garbage collection cycles.
FAQ
Why does my Endless Horror server lag badly or crash when multiple players are exploring at once?+
Endless Horror bundles nearly every genre of horror mod in one pack, and each of those mods runs its own stalking, tracking, or jumpscare AI system. Any one of them alone is usually cheap, but running many simultaneously compounds the per-tick cost of mob tracking well beyond what a single horror mod produces — the more horror mods that are active and triggered at once, the worse this stacking effect gets. With multiple players spread across different biomes or structures, you can end up with several of these systems evaluating targets in the same tick, which is a common cause of lag spikes and eventual tick timeouts.
The server crashed on startup with a Java-related error — what's going on?+
Endless Horror runs on Forge for Minecraft 1.19.2, which requires Java 17. If the server is launched with an older Java runtime (Java 8 or 11, which were standard for older Forge packs), it will fail to start or crash immediately with class version errors. Double-check the server's configured Java version before looking at anything mod-related — this is one of the most-reported setup mistakes for any Forge pack on 1.19.2 or newer.
A player's game crashes but the server itself stays online — is that a server problem?+
No. The shaders bundled with Endless Horror are a client-side setting, so a crash that only affects one player's client while the server and other players keep running is almost always a client-side issue — typically a shader configuration conflicting with that player's GPU or driver, or a client-only mod mismatch. Rule out the player's shader settings and client mod list first before assuming it's a server-side problem.
How much RAM does an Endless Horror server actually need?+
The real floor for Endless Horror is 8 GB. Running it on less can look stable for a few minutes before players scatter and the horror mods' AI systems ramp up, at which point you'll see cascading lag and garbage collection pauses rather than a clean, immediate crash.
Host Endless Horror on hardware sized for its real floor
Endless Horror needs a real 8 GB RAM floor to handle its stacked horror-mod AI load without tipping into lag-induced crashes — and taking a backup before testing any new mod or config change means a bad combination never costs you your world.
View Minecraft Hosting →