Hosting a Divine Journey 2 server lets you and your friends explore this ambitious Minecraft modpack together, sharing the intricate tech and magic progression without the single-player grind. This guide walks you through every step, from downloading the right files to configuring the server for a smooth multiplayer experience, whether you’re hosting on your own PC or a dedicated machine.
What You’ll Need
- A copy of Minecraft Java Edition (you don’t need to own it to host, but your players do).
- The Divine Journey 2 modpack from CurseForge or ATLauncher.
- A computer that meets the modpack’s system requirements (at least 4 GB RAM dedicated to the server, preferably 6-8 GB, and a decent CPU).
- Java 8 (the modpack is built for Minecraft 1.7.10, which requires Java 8, not newer versions).
- Optional: a service like Playit.gg or Ngrok if you want to play over the internet without port forwarding, or a VPS/paid hosting provider.
Step-by-Step
- Install the modpack locally (if you haven’t already). Use the CurseForge or ATLauncher launcher to install Divine Journey 2. This ensures you have the correct mod versions and configs.
- Download the server files. On the CurseForge page for Divine Journey 2, click the Files tab and download the server pack (it’s usually a separate download from the client pack). If you’re using ATLauncher, the server files are available under the pack’s page. Alternatively, you can copy your client’s mods and config folders, but the server pack is cleaner.
- Create a dedicated folder. Make a new folder on your hard drive, e.g.,
DJ2Server. Extract the downloaded server files into this folder. If you copied from a client, copy themods,config,scripts, andkubejsfolders (if present) into the server folder. - Run the server once to generate files. Double-click the
server.jarorforge-1.7.10-...-universal.jarfile. It will start, generate aneula.txtfile, and then stop. On some systems, you may need to run it from the command line withjava -jar server.jar. - Accept the EULA. Open the
eula.txtfile in a text editor and changeeula=falsetoeula=true. Save and close. - Adjust the server memory. Create a new text file in the server folder named
start.bat(Windows) orstart.sh(Linux/Mac). Edit it with the following command, adjusting the-Xmxand-Xmsvalues to allocate at least 4 GB (e.g.,-Xmx4G). For 6-8 GB, use-Xmx6Gor-Xmx8G.java -Xms4G -Xmx4G -jar server.jar noguiSave the file. On Windows, double-click
start.batto launch the server. On Linux/Mac, runchmod +x start.shthen./start.sh. - Wait for the server to fully load. The first launch can take a few minutes. Watch the console for the message “Done (x.xxxs)!” or “For help, type ‘help'”. This means the server is up.
- Configure server properties. While the server is running (or after stopping it), edit the
server.propertiesfile. Setserver-port=25565(default),motdto something fun, andmax-playersto your desired number. Also setonline-mode=trueif you want premium authentication, orfalsefor cracked clients (not recommended). - Connect locally. On the same computer, open Minecraft, select the Divine Journey 2 profile, and connect to
localhostor127.0.0.1to test that the server works. - Allow access for friends (if playing over LAN). If everyone is on the same Wi-Fi, they can connect using your local IP address (e.g.,
192.168.1.10). Find your IP withipconfig(Windows) orifconfig(Linux/Mac). - Port forwarding (for internet play). To play over the internet, you need to forward port
25565(TCP/UDP) on your router to the computer running the server. Log into your router’s admin panel (usually at192.168.1.1), find the port forwarding section, and add a rule for port 25565. Then, find your public IP address (search “what’s my IP” on Google) and share it with friends. - Alternative: use a tunneling service. If port forwarding is too complex or your ISP blocks it, use a free service like Playit.gg or Ngrok. Download the tool, run it, and it will give you a public URL that forwards to your local server. This is often easier for beginners.
Common Mistakes
- Using the wrong Java version. Divine Journey 2 is for Minecraft 1.7.10, which requires Java 8. If you have Java 11 or newer installed, the server may crash or fail to start. Make sure Java 8 is the default or explicitly point to it in your start script.
- Not enough RAM allocated. The modpack is heavy. Allocating only 2 GB will cause frequent lag spikes, chunk errors, and crashes. Stick to at least 4 GB, ideally 6 GB.
- Forgetting to accept the EULA. The server won’t start if you don’t set
eula=true. This is a common first-time mistake. - Copying the client mods folder incorrectly. If you copy from the client, you might accidentally include client-only mods (like minimaps) that cause server errors. Always use the official server pack if possible.
- Firewall blocking the server. Windows Firewall or antivirus may block Java from accepting connections. When the server first starts, Windows may ask to allow Java; click “Allow”. If not, manually add an inbound rule for port 25565.
Tips
- Back up your world regularly. Copy the
worldfolder to a safe location. Divine Journey 2 is long, and losing progress is painful. Do this whenever you stop the server. - Use a whitelist. Add
white-list=trueinserver.propertiesand then use thewhitelist add <playername>command in the console to control who can join. This prevents random griefers. - Install a server-side performance mod. Consider adding
FastCraftorOptiFine(server version) to improve tick rates. However, test them first, as they may conflict with some mods. - Keep the server console open. You need to see error messages and use commands. Don’t run it in the background without a way to view the console.
- Use a dedicated machine if possible. Hosting on your main gaming PC will cause lag for both you and your friends. If you have an old PC or a Raspberry Pi (though Pi may be underpowered), use that instead.
Troubleshooting
Server crashes on startup
Check the latest.log file in the logs folder. The most common causes are:
- Wrong Java version. Ensure you’re using Java 8. Run
java -versionin a terminal to check. - Missing mods or configs. Re-download the server pack and extract it fresh.
- Insufficient memory. Increase the
-Xmxvalue in your start script.
Players can’t connect
- Test locally first. If you can’t connect to
localhost, the server isn’t running properly. If you can, the issue is network-related. - Firewall. Temporarily disable Windows Firewall to test. If that works, add an exception for Java.
- Port forwarding. Double-check the port number and that the rule is applied to the correct IP address (the server’s local IP).
- ISP blocking. Some ISPs block inbound connections on common ports. Try using a tunneling service like Playit.gg.
- Online mode. If
online-mode=true, players must have a valid Minecraft account. If you set it tofalse, make sure everyone uses the same version and no one has a conflicting username.
Server lags heavily
- Allocate more RAM (up to 8 GB if you have it).
- Reduce the
view-distanceinserver.properties(e.g., from 10 to 6). - Check if any player is running a chunk-loaded machine that’s causing TPS drops. Use the command
/tps(if a mod adds it) to see the tick rate.
Frequently Asked Questions
Do I need to own Minecraft to host a server?
No, you only need the server files and Java. However, you do need a Minecraft account to join your own server as a player.
Can I host a Divine Journey 2 server on a free hosting site?
Some free hosts exist, but they often have limited RAM (e.g., 1-2 GB) which is insufficient for this modpack. It’s better to host on your own PC or pay for a cheap VPS with at least 4 GB.
How many players can the server support?
With 4 GB RAM, you can comfortably support 4-6 players. With 8 GB, up to 10-12, but the modpack’s heavy automation might cause lag regardless. Keep the player count low for the best experience.
Can I use my existing single-player world on the server?
Yes, but it’s risky. Copy your single-player world folder into the server’s world folder (replace the generated one). Make sure you back up first, as modded worlds can sometimes corrupt when transferred.
Do all players need the exact same modpack version?
Yes, all players must have the same version of Divine Journey 2 (including any mod updates) to connect. The server will reject clients with mismatched mod lists.
How do I update the server when a new version of the modpack comes out?
Download the new server files, stop the server, back up your world folder, then replace the mods, config, and scripts folders with the new ones. Keep the world folder intact. Start the server and test.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Access the DOM in Angular Safely
- Websites Create QR Code? How It Works
- Evaluate Private Cloud AI Security Operations Platforms
- Space Engineers Server Name & Description Setup
- Tongue Escape Events Schedule: Full Guide
- f/2.8 Telephoto Zoom: What to Consider