Divine Journey 2 isn’t your average Minecraft modpack—it’s a 600+ hour expert-level gauntlet that demands serious server resources. If you’re planning to host this beast for you and your friends, you need more than a basic setup. Let’s cut through the confusion and get your DJ2 server running properly.
What Divine Journey 2 Actually Requires
Divine Journey 2 is an expert-tier modpack containing over 300 mods, custom questing systems, and heavily modified progression. This means your server needs significantly more RAM and processing power than vanilla Minecraft or lighter modpacks.
Minimum server specifications for Divine Journey 2: 6GB RAM for 2-3 players, 8-10GB RAM for 4-6 players, and 12GB+ RAM for larger groups. CPU performance matters just as much—look for dedicated cores with high single-thread performance since Minecraft relies heavily on single-core speed.
Choosing Your Divine Journey 2 Hosting Method
You’ve got three main options for hosting a DJ2 server, each with distinct trade-offs.
Managed Game Server Hosting
This is the fastest route to getting online. Managed hosts handle the technical infrastructure while you focus on playing. Setting up Divine Journey 2 on managed hosting typically takes 10-15 minutes with one-click installers.
The advantages are obvious: automatic backups, DDoS protection, instant scaling when you need more resources, and 24/7 support when things break. For Divine Journey 2 specifically, you want a host that understands modded Minecraft server requirements and offers sufficient RAM allocation.
Looking for reliable DJ2 hosting? GameTeam.io offers optimized Minecraft servers starting at $1/GB with 20% off for new customers—perfect for resource-intensive modpacks like Divine Journey 2.
Self-Hosting on Your Own Hardware
Running DJ2 on your personal computer works if you have a beefy machine sitting idle. You’ll need at least 16GB total system RAM (allocating 8-10GB to the server), a modern CPU with good single-core performance, and a stable internet connection with decent upload speeds.
The reality? Self-hosting means your computer runs 24/7, your electricity bill climbs, and you’re troubleshooting port forwarding at 2 AM when someone can’t connect. It’s free in terms of hosting costs, but expensive in time and frustration.
VPS or Dedicated Server Hosting
Virtual Private Servers and dedicated servers give you complete control over the environment. You’ll manually install Java, configure the server software, manage firewall rules, and handle all maintenance yourself.
This approach makes sense if you’re technically proficient and want granular control over server optimization. For most players just wanting to experience Divine Journey 2 with friends, it’s overkill.
Step-by-Step Divine Journey 2 Server Setup
Here’s the actual process for getting your server running, assuming you’re using managed hosting (the most practical option for most players).
Initial Server Configuration
First, download the Divine Journey 2 server files from CurseForge or the official modpack page. You need the server files specifically, not the client modpack. The server files include all necessary mods, configurations, and scripts pre-configured for multiplayer.
Upload these files to your hosting provider through FTP, their file manager, or whatever method they provide. The complete server package is typically 200-300MB compressed.
Java Version and Startup Parameters
Divine Journey 2 requires Java 8 (1.8.0). Don’t use newer Java versions—they cause compatibility issues with older Forge versions. Most managed hosts automatically configure the correct Java version, but verify this in your server settings.
Your startup parameters matter significantly for performance. Use these optimized flags for Divine Journey 2:
-Xms6G -Xmx6G -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1
Adjust the -Xms and -Xmx values to match your allocated RAM (both should be identical for optimal garbage collection).
Server Properties Configuration
Edit your server.properties file to configure basic settings:
- max-players: Set conservatively based on your RAM (3-4 players per 6GB allocated)
- view-distance: Start at 6-8 chunks; Divine Journey 2’s complexity strains rendering
- difficulty: Set to hard—DJ2 is balanced around challenging gameplay
- enable-command-block: Set to true for quest functionality
- spawn-protection: Adjust based on your preference
Port Forwarding and Connectivity
If you’re self-hosting, you need to forward port 25565 (or your custom port) through your router. Managed hosting handles this automatically—you’ll receive an IP address and port to share with players.
Test connectivity using server status checkers before inviting players. Divine Journey 2 servers can take 3-5 minutes to fully start due to the massive mod count.
Performance Optimization for Divine Journey 2
Getting DJ2 running is one thing; keeping it running smoothly is another challenge entirely.
Mod Configuration Tweaks
Several mods in Divine Journey 2 have performance-heavy default settings. Navigate to your config folder and adjust these:
BetterFPS: Set algorithm to “rivens” for best server performance. FoamFix: Ensure all optimization features are enabled. Phosphor: Lighting engine optimization should be active by default but verify in configs.
Chunk Loading Management
FTB Utilities (included in DJ2) provides chunk loading management. Educate your players about responsible chunk loading—excessive loaded chunks murder server performance. Set reasonable limits: 25-50 chunks per player maximum.
Monitor chunk loading through the FTB Utilities admin interface. Players building complex automation setups will request more chunks, but every loaded chunk consumes server resources even when players are offline.
Backup Strategy
Divine Journey 2 worlds represent hundreds of hours of progression. Losing that to corruption or griefing is devastating. Implement automated backups every 6-12 hours minimum.
Most managed hosts include automatic backup systems. If self-hosting, use scripts or plugins like Backup Manager to schedule regular world saves. Keep at least 3-5 rolling backups.
Common Divine Journey 2 Server Issues
Server Crashes on Startup
The most frequent culprit is insufficient RAM allocation or incorrect Java version. Check your crash logs (located in the crash-reports folder) for “OutOfMemoryError” messages. If you see these, increase allocated RAM or reduce player count.
Missing or corrupted mod files also cause startup crashes. Verify your server files match the official Divine Journey 2 server pack exactly—don’t mix mod versions from different sources.
Severe Lag and TPS Drops
Ticks per second (TPS) should stay at 20. Anything below 18 TPS means noticeable lag. Use /forge tps to check current TPS.
Common lag sources in DJ2: excessive mob spawners, poorly optimized automation systems, too many active quarries, and dimension-hopping creating chunk loading cascades. Use profiling tools like LagGoggles (if you add it) or Spark to identify specific lag sources.
Player Connection Timeouts
Divine Journey 2’s massive mod count means longer login times. If players timeout during connection, increase the login timeout value in server.properties. Some players need 60-90 seconds to fully connect on slower machines.
Frequently Asked Questions
How much RAM does a Divine Journey 2 server really need?
For 2-3 players, 6GB is the absolute minimum. For 4-6 players with moderate building, allocate 8-10GB. Larger groups or players building extensive automation require 12GB+. Don’t skimp on RAM with expert modpacks—it’s the difference between playable and miserable.
Can I add extra mods to Divine Journey 2 server?
Technically yes, but it’s risky. DJ2 is carefully balanced with specific mod interactions. Adding mods can break quests, create item conflicts, or introduce game-breaking exploits. If you must add mods, stick to purely cosmetic or quality-of-life additions that don’t affect gameplay mechanics.
Why does my DJ2 server take so long to start?
With 300+ mods loading, initialization takes time. First-time startup often requires 5-7 minutes. Subsequent restarts should take 3-4 minutes. If startup exceeds 10 minutes consistently, you likely have insufficient RAM or CPU bottlenecking.
Should I use Minecraft Java or Bedrock for Divine Journey 2?
Divine Journey 2 is exclusively for Minecraft Java Edition. Bedrock Edition doesn’t support Forge mods, which DJ2 requires. All players need Java Edition to join your server.
How do I update my Divine Journey 2 server?
Download the new server files for the updated version, backup your current world and player data, replace all mod and config files with the new version, then restore your world folder. Always backup before updating—some updates aren’t backwards compatible with existing worlds.
Getting Your Players Connected
Once your server runs smoothly, share the server IP and port with your players. They need the Divine Journey 2 client modpack installed (same version as your server) through CurseForge, ATLauncher, or their preferred launcher.
Set clear expectations: DJ2 is a long-term commitment requiring coordination and patience. Server performance depends on everyone playing responsibly—no lag machines, no excessive chunk loading, and communication about major builds that might impact performance.
Your Divine Journey 2 server is now ready for hundreds of hours of expert-mode progression. Keep those backups running, monitor performance regularly, and enjoy one of Minecraft’s most challenging modpack experiences with your crew.
