Divine Journey 22026-10-25 · 6 min read

How to Host a Divine Journey 2 Server (Forge 1.12.2 Setup Guide)

Divine Journey 2 is a deep, long-form expert progression pack on Forge 1.12.2 — one of the longest expert modpacks available. It weaves a full GregTech-adjacent tech chain together with magic systems like Thaumcraft and Botania into one guided, quest-driven journey spanning hundreds of hours, which makes getting the server setup right on day one far more important than for a casual pack.

1

Start with at least 8 GB of RAM dedicated to the server — that's Divine Journey 2's own recommended floor, not a generic guess. This pack layers a full tech stack on top of magic systems like Thaumcraft and Botania, and both load heavy block and tile-entity data as the world grows, so going below 8 GB risks garbage-collection stutter once a few players are building bases and running machines at the same time.

2

Import the official Divine Journey 2 modpack through a proper modpack installer instead of zipping up a client instance and guessing which mods, configs, and version lock the server actually needs. A clean server-side import avoids the client-only mod conflicts — Thaumcraft's client rendering, JEI add-ons, and similar — that cause silent crashes on manual uploads.

3

Watch the console through the full first boot before doing anything else. Divine Journey 2 runs on Forge 1.12.2 with a dense mod list, so the first startup has to finish building block and recipe registries for the whole tech-and-magic combination — Thaumcraft's aspect registry, the GregTech-adjacent machine recipes, Botania's flower functions — without a single mod erroring out. Confirm the server reaches a clean "Done" state and the world is reachable before trusting it.

4

Only invite players once that first clean boot is confirmed. Divine Journey 2 is one of the longest expert modpacks available, and quest progress, Thaumcraft research, and GregTech-adjacent material chains all get baked into the save the moment players start interacting with the world — a server that crashes mid-boot with players already connected can corrupt early quest state.

5

Take a backup before importing a new world, updating the mod loader, or changing any config — especially quest-chain or GregTech-adjacent machine configs. Because Divine Journey 2's progression is measured in hundreds of hours across interconnected tech and magic systems, losing a world to a bad update isn't a quick redo; it's potentially months of quest, research, and automation progress gone.

Use a cleaner Divine Journey 2 path

CoalHost is built around modpack hosting, which makes Divine Journey 2 much less annoying to launch correctly.

Deploy Divine Journey 2 now →