How to Fix an FTB Revelation Server That Keeps Crashing

1. Running the wrong Java version

FTB Revelation runs on Forge for Minecraft 1.12.2, and that whole Forge generation was built and validated against Java 8 — not Java 11, 17, or 21. Launching it on a newer Java runtime is one of the most-reported causes of a server that fails to start cleanly, or that boots but then crashes partway through world load with mods throwing errors that don't obviously point back to the Java mismatch.

• Check your server's Java version explicitly rather than trusting an 'auto-detect' setting
• If your host offers multiple Java versions, pin this server to Java 8

2. AE2 network overload on startup

A large Applied Energistics (AE2) network overloading on startup is a common cause of crashes in 1.12-era tech packs like Revelation. When the server boots, AE2 has to rebuild the full connectivity graph for every ME network on the map at once — on a base with a sprawling network of cables, drives, and autocrafting setups, that rebuild can spike CPU hard enough to trip a watchdog timeout or produce an out-of-memory crash during the first few minutes after a restart.

If crashes cluster right after boot rather than during normal play, this is the first place to look before suspecting anything else.

3. IndustrialCraft2 and Thermal Expansion power networks stacking tick cost

Revelation ships both IndustrialCraft2 and Thermal Expansion, each with its own independent power system (EU and RF respectively). Running both power networks on the same base is a known source of tick-cost stacking once either system scales up — generators, cables, and machines from both mods are each doing their own per-tick calculations, and the combined load grows faster than either mod alone would suggest. This tends to surface as gradually worsening lag that eventually tips into a tick timeout rather than a single clean error.

4. Stale or conflicting config files after a modpack update

Kitchen-sink packs like Revelation get periodic updates that bump individual mod versions, and if the server's config folder was carried over from an older pack version instead of regenerated, you can end up with leftover config entries that no longer match the mod they belong to. This usually doesn't crash the server outright, but it can cause a specific mod to silently fall back to defaults or fail to initialize, which then cascades into a crash once something else depends on that mod's expected behavior. If you've recently updated the pack version, compare your config folder against a fresh copy before assuming the crash is something more exotic.

5. RAM under the pack's realistic floor

The real floor for FTB Revelation is 6 GB dedicated to the server process — higher than some generic sizing guides suggest, because the combination of IndustrialCraft2, Thermal Expansion, AE2, Tinkers' Construct, and exploration content all compete for heap simultaneously once a base matures. Under-provisioning rarely shows up as an instant, clean crash. More often it looks like cascading lag and longer garbage-collection pauses over hours or days, which eventually tip over into a tick timeout or an out-of-memory crash right when the server is under the most load — usually with several players on and several machines running at once.