How to Fix an FTB Pyramid Reborn Server That Keeps Crashing

1. Confirm you're running Java 8

Forge 1.12.2, which FTB Pyramid Reborn 3.0 is built on, needs Java 8 — this is the standard first check whenever a server on this version refuses to boot or dies within the first few seconds. Running a newer Java runtime is one of the most-reported causes of an instant crash on packs from this era, and it's quick to rule out before looking at anything mod-related.

• Check the launch script or panel's Java version setting against Java 8 specifically
• An UnsupportedClassVersionError in the very first lines of the log points straight at this

2. First-boot lag near the pyramid isn't always a crash

The pack's custom pyramid structure generates considerably more detail on first load than vanilla terrain does, so a slower-than-usual initial boot or exploration lag as players first reach the structure is expected rather than a misconfiguration. If the server does eventually come up and the lag settles once the area has fully generated, that's normal behavior for this pack, not a bug to fix.

Where this becomes a real problem is if that generation load is heavy enough to trip other systems — see the watchdog note below.

3. Watchdog timeouts during heavy structure generation

If the pyramid's structure generation takes long enough on a single tick, a watchdog or tick-timeout mechanism can kill the server process outright, which then presents as a hard crash rather than the lag described above. This is a common escalation path in 1.12-era packs with heavy custom world generation: slowness that would otherwise resolve on its own instead crosses a timeout threshold first. If crashes cluster specifically around first exploration of the pyramid rather than happening randomly later, this is worth checking before assuming a mod conflict.

4. Quest-progress corruption after an unclean shutdown

Like other FTB quest-driven packs, an unclean shutdown — a force-kill, host crash, or power loss rather than a normal stop — is a reported cause of quest-progress corruption that doesn't show up immediately. Instead it surfaces as errors or crashes on the next boot, which can be confusing because the shutdown itself looked fine at the time. If crashes started appearing after a rough restart rather than during normal play, this is a strong candidate, and a recent backup from before the bad shutdown is the fastest way back to a known-good state.

5. RAM under the pack's realistic floor

5 GB is the real floor for FTB Pyramid Reborn 3.0. Under-provisioning below that rarely produces a clean, instant out-of-memory crash — what you actually see is cascading lag and progressively longer garbage-collection pauses as the heap fills up, which then trips a tick timeout and crashes the server anyway. If crashes correlate with how long the server has been up and how much the world has grown rather than any specific action, undersized RAM is worth checking before anything else on this list.