How to Fix a Divine Journey 2 Server That Keeps Crashing
Divine Journey 2 is one of the longest expert progression packs around, stacking GregTech-adjacent tech, Thaumcraft and Botania magic, and exploration into a single guided quest chain that's meant to span hundreds of hours. That scope is exactly why its servers run into a different crash profile than a short, narrow-scope pack: the problems tend to show up gradually, as the world and the base grow, rather than all at once on day one.
See the Divine Journey 2 pack page for the full RAM and setup breakdown before you chase anything else.
1. Check the Java version first
Divine Journey 2 runs on Forge for Minecraft 1.12.2, and any Forge pack on that version line needs Java 8 specifically. Running it on a newer Java runtime is the standard first check whenever a server crashes immediately on boot rather than after some time running — it's a quick thing to rule out before looking anywhere else.
2. Autosave stalls on a long-played world
Because Divine Journey 2 is built as one of the longest expert quest chains in the catalog, the accumulated quest progress and world-save data grow substantially the deeper a group gets into the pack. On an old world, that can lengthen how long autosave takes to run, which shows up as a periodic lag spike or an apparent freeze right when the server writes the world to disk.
- If freezes line up with the autosave interval, that's a strong signal this is the cause rather than a crash
- Spacing autosave out further reduces how often that stall happens, at the cost of slightly more risk if the server does go down between saves
3. GregTech-style multiblock tick overhead
GregTech-adjacent multiblock machines are a well-documented source of tick overhead once a base's automation scales up — this is the same pattern seen across every GregTech-inspired pack, not something unique to Divine Journey 2. As a tech base grows into larger processing lines, the per-tick cost of keeping all those multiblocks ticking can climb enough to drag the whole server's tick rate down, which players experience as rubber-banding or a server that feels like it's about to crash even when it technically hasn't.
This tends to get worse gradually as a base expands, rather than appearing suddenly, which is a useful way to distinguish it from a one-off crash caused by something else.
4. Tech-and-magic mod interaction conflicts
Combining a tech progression (GregTech-style) with magic systems like Thaumcraft and Botania in one expert pack raises the odds of running into a specific mod-interaction conflict, simply because there are more systems touching the same world events, blocks, and dimensions than in a narrower-scope pack. If you've ruled out the Java version and the tick-load causes above and crashes still cluster around a particular activity — crossing into a specific dimension, using a particular combination of machines and magic items together — that's worth treating as a mod-interaction issue and checking the pack's own known-issues list for it, rather than assuming it's a generic server problem.
5. RAM under the pack's realistic floor
The real floor for Divine Journey 2 is 8 GB. Under-provisioning rarely looks like a single clean crash — it usually shows up as cascading lag and longer garbage-collection pauses as the base and world grow, until eventually one of those GC pauses runs long enough to trigger a tick timeout and the server drops. Because the pack's quest and world data keep growing over hundreds of hours of play, a server that was fine at launch can still end up memory-starved months later even with no change in player count, simply because the world itself got bigger.
FAQ
Why does my Divine Journey 2 server crash right at startup?+
The first thing to rule out on any Forge 1.12.2 pack is the Java version — Divine Journey 2 needs Java 8, and running it on a newer runtime is one of the most common causes of an instant crash on boot. After that, check that the world actually loaded cleanly; a long-played save with hundreds of hours of quest and chunk data takes noticeably longer to come up than a fresh world, and a server that's killed for 'hanging' during that window will look like a crash when it was really just still loading.
Is it normal for autosave to lag the server on an old Divine Journey 2 world?+
Yes, and it gets more noticeable the longer a world has been played. Divine Journey 2 is one of the longest expert quest chains in the catalog, so by the time a base is hundreds of hours in, the world save and quest-book data have grown substantially, and autosave can produce a visible lag spike or tick stall every time it runs. That's expected behavior, not necessarily a sign of corruption — but if it's severe, increasing the autosave interval can help.
How much RAM does a Divine Journey 2 server actually need?+
The real floor is 8 GB. That's higher than some generic modpack guides assume, because the combination of long-term quest progression data, a growing world save, and GregTech-adjacent multiblock automation all add to the server's working memory footprint as a base matures — not just at a single busy moment, but as a steady baseline once players are deep into the pack.
Host Divine Journey 2 on hardware sized for its real floor
Divine Journey 2's world and quest data keep growing over hundreds of hours, so give it the real 8 GB floor from day one and take a backup before any risky change like a mod update or a GregTech-scale automation expansion.
View Minecraft Hosting →