Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThe quickest way to host Divine Journey 2 is to rent a Minecraft Java server with a modpack installer, select the pack and its exact version, start the instance, and give players the address shown in the control panel. Self-hosting is also possible: download the matching Divine Journey 2 server pack from CurseForge, extract it, run launch.bat on Windows or launch.sh on Linux, accept the generated EULA, and configure access for your players.
Running a modpack with friends? Godlike.Host offers modded Minecraft server hosting with one-click modpacks (CurseForge, FTB, Technic) and free DDoS protection.
Divine Journey 2 targets Minecraft 1.12.2 on Forge. Every player must use the same Minecraft version, Forge loader, and Divine Journey 2 pack version as the server. The CurseForge listing showed Divine_Journey_2.23.4 as the latest release when checked in October 2026, with more than 960.7K downloads; pack versions and download totals can change, so verify the listing immediately before installation.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft | Java & Bedrock Ultimate Collection | Windows Digital Code | $49.99 | Buy on Amazon |
| 3 |
|
Minecraft | Standard Edition | XBOX Digital Code | $19.99 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What you need before creating the server
Decide first whether you want a managed server or a machine you administer yourself. The game files are the same, but the work, control, and failure modes differ.
- A Java Edition installation: Divine Journey 2 is a Java Edition modpack, not a Bedrock add-on.
- Forge 1.12.2: The server and every client must use the Forge loader for Minecraft 1.12.2.
- One exact pack version: Choose a release on CurseForge and keep the server and clients on that release. Do not let a host silently install a different revision.
- A memory plan: Provider guidance ranges from 6–8 GB for a small group to 10–12 GB for 10 or more players. Another provider recommends 8 GB, with 6 GB as a minimum, for this pack on Forge 1.12.2.
- A way for players to reach the machine: A managed panel normally supplies an address. A self-hosted server also needs a reachable network address and any required router or firewall configuration.
- A current runtime check: Java 8 is commonly suggested for this pack, but the exact requirement was not confirmed from primary documentation. Check the server-owner README linked from the current CurseForge listing before choosing or changing Java.
If you are unsure which release to use, choose one version for the whole group, record it in your group chat, and do not update the server until every player can update their client.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
Managed hosting versus self-hosting
| Decision point | Managed hosting | Self-hosting |
|---|---|---|
| Initial setup | Use a modpack or quick-install tab, search for Divine Journey 2, choose a release, and install. | Download the server pack, extract it, run the supplied launch script, and accept the EULA. |
| Hardware control | Limited to the plan’s RAM and CPU allocation. | You choose the machine, storage, Java installation, and memory flags. |
| Maintenance | The panel usually handles the server process and provides controls; you still manage pack updates and backups. | You are responsible for Java, scripts, operating-system updates, backups, networking, and the process itself. |
| Performance tuning | Change settings exposed by the provider and select a larger plan when available. | Adjust the launch script, memory allocation, CPU scheduling, and operating-system settings directly. |
| Best fit | Players who want the server online quickly and do not want to administer a machine. | Owners who need full control and are comfortable troubleshooting files, Java, and networking. |
Some hosting pages advertise a 10–15 minute one-click setup. That is a provider estimate rather than a guarantee: installation time depends on the host, the selected release, and download speed. Self-hosting takes longer at the first launch because the server must create its files and configuration.
Option 1: install Divine Journey 2 with managed hosting
Use these steps when your provider offers a Minecraft Java modpack installer. Panel names vary, but the sequence is consistent.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Create a Minecraft Java server. Select a location and plan with enough memory for your group. Start with the provider’s published guidance: 6–8 GB for a small group, or 10–12 GB for a group of 10 or more. If the provider lists 8 GB as the recommended allocation and 6 GB as the minimum, treat those values as the starting point rather than a performance guarantee.
- Open the modpack, modpack installer, or quick-install area. Do not use a generic Forge installation unless you also install the complete Divine Journey 2 server files; the pack contains many interdependent mods and configuration files.
- Search for Divine Journey 2. Select the release that your group intends to play. The CurseForge listing showed
Divine_Journey_2.23.4as the latest release at the October 2026 check, but a host’s catalog can lag behind CurseForge. - Confirm the Minecraft and loader labels. The target is Minecraft 1.12.2 on Forge. If the panel shows another Minecraft version or loader, stop and choose the matching entry.
- Run the installation. Allow the panel to download and unpack the server files. Keep the server stopped while the installer is replacing files; starting during an incomplete install can leave a partial directory.
- Accept the EULA when prompted. Some panels display an EULA switch; others create an
eula.txtfile that you must edit. Accept it only after reading the agreement. - Set the memory allocation. Use the panel’s Java or startup settings. Keep the minimum and maximum values aligned if the host recommends matching values. Do not allocate all physical RAM: the operating system, file cache, and the panel’s service also need memory.
- Start the server and watch the console. Wait for the normal ready message before connecting. The first launch can take longer while Forge and the pack create libraries, configs, and world data.
- Copy the address shown by the panel. Give players the exact hostname and port displayed by the provider. Do not substitute the panel URL or an internal address.
- Install the same client pack. Each player should install the identical Divine Journey 2 release, Minecraft 1.12.2, and Forge 1.12.2. A client on another pack revision can fail during the mod handshake even when the server is healthy.
- Connect from the Multiplayer screen. Add the panel’s address, join, and confirm that the player reaches the world. Test with one player before inviting the rest of the group.
What to check in a managed panel
- The installed pack name and release number, not only the word Forge.
- The Java version selected by the panel and whether it can be changed.
- The RAM value in megabytes or gigabytes and whether it is a hard limit.
- Separate controls for stopping, restarting, reinstalling, and changing the pack version.
- Automated backup availability and where backup files are stored.
- The public address and port players must use.
If the installer offers only a different Divine Journey 2 release, do not mix files from two versions. Either select the exact release available to the whole group or use the self-hosting method with the corresponding server pack.
Option 2: self-host from the official server pack
Self-hosting gives you direct control over the files and machine, but every administrative task becomes yours. Use the server pack for the same Divine Journey 2 release that your players will install.
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
1. Download and prepare a clean directory
- Open the current Divine Journey 2 listing on CurseForge and locate the server pack for your chosen release. The main listing credited the pack to AtricosHU and identified version 2.23.4 as the latest release at the October 2026 check.
- Create a dedicated folder for the server, such as a folder named for the pack and release. Avoid placing it inside a client instance or a cloud-synchronized directory.
- Extract the server-pack archive directly into that folder. The launch scripts, libraries, configuration directories, and other files should be at the server folder’s top level rather than buried inside an extra archive folder.
Keep the original archive until the server has started successfully. It is useful for rebuilding a clean installation if a configuration change or failed update damages the working directory.
2. Confirm Java before the first launch
The pack is commonly associated with Java 8, but the exact requirement was not verified from primary pack documentation. Before launching, read the server-owner README linked from the current CurseForge page and follow its Java instruction. If more than one Java installation is present, make sure the script calls the intended executable rather than whichever version happens to be first in the system path.
3. Launch on Windows
- Open the extracted server folder in File Explorer.
- Double-click
launch.bat. If Windows blocks the script, review the security prompt and run it from a Command Prompt in the server folder so you can read the error text. - Allow the first run to finish creating the server files. Do not close the window while libraries or configuration files are being generated.
- When the process stops because the EULA has not been accepted, open the generated
eula.txt, change the acceptance line as required by the agreement, save the file, and runlaunch.batagain. - Leave the console running while the server is online. Closing it normally stops the server; use the server’s stop command before shutting down Windows.
4. Launch on Linux
- Open a terminal in the extracted server directory.
- Make the script executable if necessary, then run
launch.shfrom that directory. Running it from another directory can cause relative paths to resolve incorrectly. - Read the first-run output. As on Windows, the initial launch may create
eula.txtand stop until the EULA is accepted. - Edit the generated EULA file only after reviewing it, save the change, and run
launch.shagain. - Use a persistent terminal session or service manager so the server continues running after you disconnect from a remote shell. Stop it through the server console before maintenance.
5. Give players a reachable address
Players outside your home network cannot use the machine’s private address. Configure the router and host firewall to pass the server’s configured port to the host machine, then give players the public address and port. If your internet connection changes its public address, use the current address or a hostname you control. Test from a different network, such as a phone hotspot, because a test from inside the same network can succeed even when outside access is blocked.
Version matching is non-negotiable
Divine Journey 2’s server and clients must match the Minecraft and Forge pairing: Minecraft 1.12.2 with Forge 1.12.2. They should also use the same Divine Journey 2 release. The most recent release shown by the October 2026 CurseForge check was 2.23.4, but that is a time-sensitive listing value, not a permanent requirement.
Rank #3
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that is unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world full of surprises.
- SURVIVAL ADVENTURES — Face mysterious foes, travel across varied landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play solo or join friends in local split-screen and cross-platform play across console, mobile, and PC. Online multiplayer supports up to 8 players.
- COMMUNITY PLAY — Connect with players on community servers, or subscribe to Realms Plus (sold separately) to play with up to 10 friends on a private server.
Use a simple version record
- Pack: Divine Journey 2
- Pack release: the exact number installed on the server
- Minecraft: 1.12.2
- Loader: Forge 1.12.2
- Java: the version required by the current server-owner README
Put this record in the server’s welcome message or group chat. When updating, stop the server, make a backup, install the new server files, and have every player update their client before reconnecting. Never overwrite a working world without a restorable backup.
RAM, CPU, and startup settings
How much memory should you allocate?
| Group or guidance | Suggested allocation | Qualification |
|---|---|---|
| Small group | 6–8 GB | Range suggested on a provider page; the source was not pinned to a named provider. |
| 10 or more players | 10–12 GB | Provider guidance; actual demand varies with world activity and loaded areas. |
| General Forge 1.12.2 recommendation | 8 GB | One provider recommendation, with 6 GB described as a minimum. |
These are planning figures, not a guarantee that a particular number of players will run smoothly. Start within your host’s limits, watch the console and operating-system memory use, and increase allocation only when the server shows memory pressure. Allocating excessive RAM can leave too little for the operating system and may make recovery harder.
A low-quality AI-generated blog mentions a 16 GB machine with 8–10 GB assigned to the server. That statement is not authoritative and should not be treated as a requirement. Use the current pack documentation and measured behavior on your machine instead.
CPU matters for tick rate
One provider advises that this pack is CPU-heavy on a single core, meaning per-core clock speed can affect tick rate more than a high core count. Treat that as practical provider guidance rather than a benchmark. When choosing between plans with similar RAM, favor the option with stronger per-core performance and monitor the server’s tick behavior under the actual number of players and loaded bases.
Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
Memory flags
Some hosts recommend matching minimum and maximum memory values and adding Aikar’s Java flags. Those settings can be useful when the provider supports them, but flags must match the Java version and the host’s startup format. If the server fails immediately after adding flags, remove the custom flags, confirm the Java version in the pack README, and start with the provider’s default command.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.First-connection checklist
- Confirm the server console has reached its ready state rather than still generating files.
- Check that the client uses Minecraft 1.12.2, Forge 1.12.2, and the same Divine Journey 2 release.
- Use the exact address and port supplied by the host panel or configured for the self-hosted machine.
- Join with one test account before distributing the address to everyone.
- After the first successful login, stop the server cleanly and make a backup of the newly created world and configuration.
Troubleshooting common failures
The server stops with a Java-version error
Read the complete console message instead of repeatedly restarting. Verify the Java version required by the current server-owner README, then check which executable launch.bat or launch.sh is calling. If the script contains a Java path or version-specific option, edit that script carefully and retry. A managed host may require selecting Java in the panel rather than editing files.
Recommended Free Tools
The server reports that memory is insufficient
First confirm the host’s hard RAM limit and the value actually passed to Java. Remove duplicate or conflicting memory options, then raise the allocation within the provider’s limit. For self-hosting, leave memory for the operating system and other services. If the machine cannot provide the required allocation, reduce the player count or move the server to a machine with more available RAM instead of repeatedly restarting an undersized process.
Players receive an incompatible-mod or missing-mod message
Compare the server’s pack release with the client’s installed release, then verify Minecraft 1.12.2 and Forge 1.12.2 on both sides. Do not copy individual mods from a different release to “fix” the list; use the complete matching client or server pack.
Best Value
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
The server is online but nobody outside the host can join
On managed hosting, use the public address and port shown in the panel, not an internal address. On a self-hosted machine, verify the process is listening on the configured port, the operating-system firewall permits it, and the router forwards it to the correct machine. Test from another network to distinguish a local-network success from genuine internet reachability.
Players can connect, but the world feels slow
Check CPU and memory usage while the problem is occurring. The provider guidance for this pack points to single-core CPU speed as an important factor, so adding more cores without stronger per-core performance may not solve tick-rate problems. Confirm that the server is not swapping or repeatedly running out of memory, and avoid changing several startup flags at once.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
An update leaves the server unable to start
Stop the process, restore the pre-update backup, and confirm which release the server directory contains. Reinstall the complete server pack for the intended release rather than mixing files from two archives. Have clients remain on the known-good release until the server starts cleanly and a new backup exists.
Backups and routine maintenance
Back up before every change
Stop the server cleanly before copying world, configuration, and script files. Keep at least one backup outside the live server directory. Label backups with the Divine Journey 2 release and date so you can identify which version can restore the world.
Update in a controlled order
- Announce a maintenance window and stop new logins.
- Stop the server and copy a restorable backup.
- Record the current pack release, Java setting, memory allocation, and any custom configuration.
- Install the new server pack in a clean directory or follow the pack’s documented replacement procedure.
- Start the server and watch the full console for errors.
- Test with one client using the new matching release.
- Only then ask the rest of the group to update.
Keep access limited
Share the address only with intended players, use the server’s built-in access controls where available, and avoid running the server as an administrator or root account. Keep the host operating system and Java installation maintained, and never expose management-panel credentials in chat.
Which hosting route should you choose?
Choose managed hosting when speed matters most
A managed installer is the practical choice if you want a server online quickly, do not want to configure Java or networking, and accept the host’s limits on CPU, RAM, and supported pack versions. Verify the exact Divine Journey 2 release before installation because provider catalogs can lag behind CurseForge.
Choose self-hosting when control matters most
Self-hosting is better when you already have a suitable machine, need direct access to scripts and files, or want to control backups and upgrades yourself. It requires more troubleshooting: Java selection, memory settings, firewall rules, router forwarding, process supervision, and recovery from failed updates all remain your responsibility.
Quick Recap
Final setup checklist
- Divine Journey 2 release chosen and recorded.
- Minecraft 1.12.2 and Forge 1.12.2 confirmed on server and clients.
- Current server-owner README checked for the Java requirement.
- RAM selected from the 6–12 GB provider guidance and adjusted for your group.
- Server pack installed through a managed installer or extracted from CurseForge.
launch.batorlaunch.shrun successfully.- EULA accepted in the generated file when requested.
- Public address tested by a player outside the host’s local network.
- First successful world launch backed up before inviting the full group.
- Update and rollback procedure written down before changing versions.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
