How to Fix an A Shattered Prophecy Server That Keeps Crashing

1. Java version mismatch on boot

Forge 1.20.1 requires Java 17, and this is the first thing to rule out if your server fails to boot entirely rather than crashing mid-session. If the log shows the process exiting almost immediately — before any world or mod-loading messages appear — the server is very likely running on the wrong Java version. This is a universal requirement for any Forge pack on 1.20.1, not something specific to this pack's mod list, so it's worth checking before digging into logs for anything more exotic.

• Confirm the server's Java runtime is Java 17, not Java 8 or Java 11
• A near-instant exit with no world-loading log lines points here first

2. CPU spikes when a scripted encounter fires

A Shattered Prophecy's whole design revolves around scripted narrative encounters — the ARG's signal-and-hidden-message storyline is delivered through custom entities and triggered events rather than static world content. When one of these encounters fires, it's normal to see a short CPU spike or a brief tick stutter as the game loads entities and runs the associated scripted behavior. This is a normal part of how event-driven horror/mystery packs work, not evidence of a memory leak or a failing mod. The distinction that matters is duration: a one-off stutter during an encounter trigger is expected, while a sustained freeze or an outright crash at that moment is not and deserves a closer look at the log.

3. Custom entity AI tick cost during encounters

Beyond the momentary spike when an encounter starts, the custom entities involved in these scripted sequences carry real, ongoing tick cost for their AI while they're active — similar to what you'd see in other horror-encounter-focused packs that rely on custom mobs for atmosphere and narrative beats. If your server's TPS dips specifically while an encounter is in progress (rather than just at the trigger moment), that sustained AI load is a more likely explanation than a one-off bug, and it's worth checking whether multiple encounters or custom entities are overlapping at once.

4. Mod or config conflicts unrelated to the ARG scripting layer

If you've ruled out Java version, encounter-trigger spikes, and sustained AI load, the next place to look is the usual Forge-pack suspects: a corrupted config file from a bad shutdown, or a conflict introduced by a third-party mod added on top of the base pack. Compare your server's config and mod list against a clean copy of the pack before assuming the crash is specific to the ARG scripting system — a generic Forge 1.20.1 conflict will often look superficially similar to a scripted-encounter crash in the log.

5. RAM under the pack's realistic floor

The real floor for A Shattered Prophecy is 6 GB. Running below that doesn't usually produce a single clean crash — it more often shows up as cascading lag and garbage-collection pauses that build up over a play session, especially once a few scripted encounters have triggered and left extra entities and loaded chunks behind, eventually ending in a tick timeout or an unresponsive server rather than a tidy error message. If you're seeing instability specifically during or shortly after encounters and you're under 6 GB, check memory headroom before assuming it's a mod conflict.