Vault Hunters 3rd Edition: Server Hardware Specs and Configuration Guide
Vault Hunters 3rd Edition (VH3) is not a casual modpack. It runs over 250 mods including Apotheosis, Create, and Sophisticated Storage, all of which compete for CPU cycles during every Vault dimension load. Most hosts will struggle with it. Here is how to set up and run it correctly.
Minimum vs. Recommended Hardware
| Spec | Bare Minimum | Recommended (Space-Node) | |---|---|---| | CPU | 4 cores @ 3.5 GHz | Ryzen 9 7950X3D (5.7 GHz boost) | | RAM | 10 GB | 14–16 GB | | Storage | SSD | NVMe Gen 4 | | Network | 100 Mbps | 1 Gbps |
VH3 crashes on HDD within hours of heavy play due to vault dimension I/O. NVMe is non-negotiable.
JVM Arguments for VH3
java -Xmx14G -Xms14G \
-XX:+UseZGC \
-XX:+ZGenerational \
-XX:+AlwaysPreTouch \
-XX:+DisableExplicitGC \
-Dfml.readTimeout=240 \
-jar server.jar nogui
The extended readTimeout of 240 seconds is critical. VH3's vault dimension generation is slow. Without this setting, players time out while entering vaults on the first load.
Server Configuration for VH3
In server.properties:
simulation-distance=5
view-distance=8
max-tick-time=120000
difficulty=normal
max-tick-time=120000 prevents the server from crashing when vault dimension initialisation takes longer than the default 60-second watchdog timeout. This is not removing safety checks — it is adjusting them for the known-slow VH3 dimension loading behaviour.
Expected Player Count Limitations
VH3 is fundamentally designed for small groups:
- 1–5 players: Smooth and stable with 10–12 GB RAM
- 5–10 players: Requires 14–16 GB; vault runs should be staggered
- 10+ players: Only on dedicated hardware; simultaneous vault runs will cause severe lag
The vault dimension loading sequence is CPU-bound on the main thread. When two players enter different vaults simultaneously on the same server, the load compounds multiplicatively. Server-side rules about one vault open at a time dramatically improve quality of life.
Common VH3-Specific Issues
Vault crash on entry: Usually RAM exhaustion. Increase to 14 GB and set -XX:+AlwaysPreTouch.
Lag during crafting stations: Sophisticated Storage's terminal is tile-entity-heavy. Limit crafting terminal use to 1–2 simultaneously per area.
World save lag: VH3 vault worlds are large. Run AutoSave with a 15-minute interval rather than the default 5-minute. Autosave pauses the entire server on SATA SSD — NVMe reduces this to imperceptible.
Space-Node's Minecraft plans include NVMe storage and the Ryzen 9 processor stack that handles VH3's demands. Our support team has configured VH3 servers extensively and can assist with vault crash diagnoses.