Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesTo make a Vault Hunters 3rd Edition server, download the matching server pack from the pack’s CurseForge files page, run it with 64-bit Java 17, accept the Minecraft EULA, configure the server, and make its port reachable to your friends. Vault Hunters 3rd Edition targets Minecraft 1.18.2. Plan for roughly 4 GB of server memory plus 2 GB for each player who will be online at the same time; the client itself should be allocated about 8 GB (8192 MB).
Running a modpack with friends? Godlike.Host offers modded Minecraft server hosting with one-click modpacks (CurseForge, FTB, Technic) and free DDoS protection.
What you need before starting
Vault Hunters 3rd Edition is a Forge modpack for Minecraft 1.18.2. The official guidance centers on Java 17, not a newer Java release selected at random. Install a 64-bit Java 17 runtime on the computer that will run the server, and use the same Java generation for every client.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →- Vault Hunters 3rd Edition server files: Download the server pack from the Vault Hunters CurseForge page’s Files tab. The exact filename changes as releases are published, so verify the current file immediately before you set up the server.
- 64-bit Java 17: Check it with
java -version. A 64-bit installation is important because a modded server can exceed the address space available to a 32-bit runtime. - Memory: Allocate about 8 GB (8192 MB) to each Vault Hunters client. Size the server at 4 GB plus 2 GB for every concurrent player as the official rule of thumb.
- Storage: Keep at least approximately 3 GB of free disk space for the initial installation, and leave additional room for the generated world, logs, backups and future pack files.
- Network access: A home server needs an inbound Minecraft port forwarded from your router to the host computer, plus a firewall rule. If your internet connection uses carrier-grade NAT or blocks port forwarding, use a managed host or a VPN-style overlay instead.
Do not combine files from different Vault Hunters releases. The server pack, client profile, configuration files and mods are intended to work as one versioned set.
Self-hosting or managed hosting: which route fits?
The community documentation describes running your own server as free because the server files are available for download. “Free” does not remove the cost of a computer, electricity, storage or your time maintaining it. A managed Minecraft host charges for that infrastructure and usually handles public reachability, but the exact plans, prices, backups and supported modpack versions vary by provider and must be checked on the provider’s current page.
#1 Best Overall
- 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
| Decision factor | Self-hosted on your computer | Managed Minecraft host |
|---|---|---|
| Upfront cost | No hosting fee; you supply the computer, storage and internet connection. | Recurring fee; current pricing and included resources are provider-specific. |
| Control | Full access to server files, Java arguments, world data, configs and installed versions. | Control depends on the panel and plan; some providers restrict files or Java settings. |
| Setup effort | You install Java, run the pack, configure the firewall and router, and maintain backups. | The provider normally supplies a panel and network endpoint, reducing infrastructure work. |
| Public reachability | Requires port forwarding or an overlay network; some ISPs make this impossible. | A public address is generally part of the service, subject to the provider’s terms. |
| Backups | You must create, test and store dated copies yourself. | Automated backups may be available, but retention and restoration limits differ. |
| Uptime | Depends on your power, hardware, operating system and home connection. | Depends on the provider’s infrastructure and maintenance policy. |
| Player count | Limited by your CPU, memory, storage speed and upload bandwidth. | Limited by the plan’s allocated resources and the provider’s node capacity. |
| Changing versions | You decide when to replace the server pack, after taking a backup. | You may have one-click installers, but the panel may lag behind a new release. |
Choose self-hosting when you want maximum control and are comfortable operating a Java application and a network service. Choose managed hosting when friends need a reliable address and you do not want to maintain router rules, firewalls, backups and uptime.
Step 1: Choose one Vault Hunters release
- Open the Vault Hunters 3rd Edition page on CurseForge and go to its Files tab.
- Identify the release you intend to play. Record its version number so every player can install exactly the same release.
- Download the corresponding server files, not merely the client profile. The server archive’s filename is volatile; use the filename shown on the Files tab on the day you download it.
- Keep the downloaded archive until the server has started successfully and you have made a backup. It provides a known-good starting point if you need to rebuild the folder.
The Vault Hunters site specifically directs users to its own server files on CurseForge. Avoid unofficial repacks: an apparently similar archive can omit required Forge libraries, scripts or configuration files.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Step 2: Install Java 17 and prepare the server folder
Install a 64-bit Java 17 distribution on the machine that will host the world. Open a new terminal after installation and run:
java -versionThe result should identify Java 17 and a 64-bit runtime. If the command is not found, add Java’s bin directory to your operating system’s PATH or use the full path to the Java executable in the supplied start script.
- Create a dedicated folder such as
VaultHuntersServeron a drive with plenty of free space. Do not place the world in a temporary Downloads folder. - Extract the server archive into that folder without nesting it several levels deep. You should see the supplied scripts, configuration directories and Forge/server files together.
- Read the included README or start-script comments. Use the supplied script first because it contains the pack’s expected launch arguments and file names.
- If your operating system blocks a script downloaded from the internet, approve it in the file’s security properties or recreate the launch command from the pack’s README. Do not guess a jar filename.
On Linux, a supplied shell script may need execute permission before you run it, for example chmod +x start.sh followed by ./start.sh. On Windows, run the supplied batch file from the server folder so its relative paths resolve correctly.
Step 3: Run the server once and accept the EULA
- Start the supplied script and wait for Forge and the pack to create its initial files. The first launch can take longer than later starts.
- When the process stops or reports that the EULA must be accepted, open the newly created
eula.txt. - Change only the value from
eula=falsetoeula=trueafter reading and accepting Mojang’s EULA. Save the file. - Start the same script again and wait for the server to finish generating the world and reach its ready prompt. Do not close the terminal while generation is in progress.
- Stop the server cleanly from its console with
stop. A clean stop flushes world data and reduces the chance of a corrupted save.
Make your first dated backup now, before inviting anyone. Copy the entire server folder, or at minimum the world directories plus configuration and allowlist files, to a separate disk or storage location.
Recommended Free Tools
Step 4: Configure the server
After the first successful launch, stop the server before editing files. The main general settings are in server.properties; pack-specific settings normally live in the server’s supplied configuration folders.
Set basic gameplay options
- Difficulty: Set the value you want for your group. Vault runs can be punishing, so agree on the setting before beginning a shared world.
- View distance and simulation distance: Lower values reduce the number of chunks and entities the server must process. Raise them only after confirming that the host has CPU and memory headroom.
- Game mode and permissions: Keep ordinary players in survival unless your group has agreed otherwise. Give operator status only to people who need administrative commands.
- Whitelist: Enable the allowlist if the server is private, then add each friend by their exact Minecraft username. This is safer than relying on an undisclosed address alone.
- Server name and message: Set a recognizable name and welcome message so players can identify the correct entry in their multiplayer list.
Use the configuration files included with the server pack. Do not copy client-only configuration files into the server directory; client settings can be ignored, cause errors or overwrite values the pack expects on the server.
Step 5: Make the server reachable to friends
Players on the same home network
Give players on the same LAN the host computer’s private IPv4 address, such as 192.168.x.x, followed by the port if necessary. Reserve the host’s local address in the router so it does not change after a reboot. A LAN address will not work for friends connecting from outside your home.
Friends connecting over the internet
- Find the host computer’s private address and make it stable with a DHCP reservation or a static local configuration.
- In the router’s port-forwarding page, create a rule for the Minecraft server’s normal TCP port,
25565, forwarding it to that private address. Use a different external port only if your router or ISP requires it, and tell players the resulting address and port. - Allow the Java runtime or the selected TCP port through the host operating system’s firewall. On a Linux system using UFW, the equivalent rule is commonly
sudo ufw allow 25565/tcp; use your distribution’s firewall tool if it differs. - Start the server and test from outside your home network, for example with a friend’s connection or a phone hotspot. Testing only from inside the LAN can hide a forwarding or ISP problem.
- Send friends your public IP address or a stable DNS name, never your router’s private address. Treat the public address as information for your invited players, not as a substitute for a whitelist.
If the port remains unreachable despite correct forwarding and firewall rules, your ISP may use carrier-grade NAT, block inbound connections or provide a changing public address. In that case, use a managed host or a VPN-style overlay network and give friends the address generated by that service. Document which method you chose so players do not try to use the wrong address.
Step 6: Install matching clients and connect
- Each player installs the same Vault Hunters 3rd Edition release through CurseForge or another launcher that supports the pack.
- In the launcher’s Java settings, select 64-bit Java 17. Remove older Java paths that the launcher may have retained from another Minecraft instance.
- Allocate about 8192 MB to the client. This is the official client allocation guidance, not a guarantee that every computer can run the pack smoothly.
- Launch the pack once in single-player or the main menu so required files finish downloading before connecting.
- Choose Multiplayer, add the server’s LAN or public address, and connect. If you use a nonstandard port, enter it as
address:port.
A “mod list mismatch,” missing-mod error or immediate disconnect usually means the client and server are not on the same release, the client was installed from a different pack version, or a file was removed or changed. Compare the exact release number first; reinstalling the client profile is often faster than manually replacing individual mods.
How much RAM does a Vault Hunters server need?
The official Vault Hunters FAQ gives this sizing rule: 4 GB plus 2 GB for every player who will be online at the same time. It is guidance, not an independent benchmark. Actual use changes with view distance, exploration, chunk generation, redstone and mob activity, backups, and whether the same computer is also running a client.
Rank #4
- 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
| Concurrent players | Rule-of-thumb server allocation | Planning note |
|---|---|---|
| 1 | 6 GB | Leaves little room if the host also runs the client. |
| 2 | 8 GB | A practical starting point for a small private group. |
| 4 | 12 GB | Allow additional headroom for exploration and world generation. |
| 8 | 20 GB | Check CPU, storage speed and upload bandwidth as carefully as memory. |
| More than 8 | 4 GB + 2 GB per concurrent player | Use the formula, then monitor real usage before increasing limits. |
Do not allocate all physical memory to Minecraft. Leave enough for the operating system, Java overhead, the launcher and backup tools. If the host computer also plays Minecraft, budget the client’s roughly 8 GB separately. A server that constantly reaches its memory limit can pause during garbage collection; a server with too little CPU or slow storage can still lag even when memory is available.
Keep the server healthy after launch
Stop it cleanly
Use the console’s stop command before shutting down the computer or restarting the operating system. Avoid killing the Java process unless it is completely unresponsive. Abrupt termination can leave region files or player data in an inconsistent state.
Back up on a schedule
- Create dated backups before every pack update, configuration change and major world operation.
- Keep at least one copy outside the live server folder. A backup on the same disk does not protect against disk failure or accidental deletion.
- Test a backup by opening it as a separate temporary server. A file that copied successfully is not necessarily restorable.
- Tell players when backups run and avoid copying while the server is actively writing world data; stop the server first unless you use a backup method designed for live worlds.
Monitor the right symptoms
Watch the server console for repeated warnings, long save times and tick-delay messages. Check available memory, CPU load, disk space and network upload capacity while several players explore. If lag appears only when new terrain generates, reduce view and simulation distances before increasing memory. If the process is killed by the operating system, verify that the host has enough free memory and that the Java maximum is not larger than the machine can provide.
Update deliberately
- Read the release notes and confirm that a new server archive exists for the exact client version you want to use.
- Tell players to stop launching the old profile until the maintenance is complete.
- Stop the server and make a full, dated backup of the world and configuration.
- Install the new server files in a fresh folder or replace files according to the pack’s instructions; do not blindly overwrite a live world.
- Start the updated server once, check the console for errors, and connect with a matching updated client before inviting the whole group.
Avoid updating a Forge modpack in the middle of a vault run without a rollback plan. If the new release fails, restore the previous server folder and backup rather than deleting files at random.
Troubleshooting common failures
The server closes immediately
Run the supplied script from a terminal so you can read the final error. Confirm Java 17, check that the archive was fully extracted, and verify that you are launching from the server folder. If an EULA file was created, set its value to true only after accepting the EULA.
Free tools Windows power users keep installed
One-click scans. No signup required.
Friends cannot connect, but you can
Test the server from outside the LAN. Recheck the host’s current private address, the router’s port-forward destination, the operating-system firewall and the port number entered by players. If local connections work but outside connections never reach the server, suspect carrier-grade NAT or an ISP restriction and switch to managed hosting or an overlay network.
Players receive a version or mod mismatch
Compare the release number shown in every launcher and in the server files. Confirm that nobody installed an additional mod or removed a required one. Reinstalling the exact client profile is safer than copying individual jar files between installations.
Memory warnings or severe pauses
Confirm that the Java maximum is realistic for the host, close unrelated applications, and leave operating-system headroom. Reduce view and simulation distances, limit simultaneous exploration and check whether the world is generating many new chunks. Increase memory only when the machine has spare physical RAM; more allocated memory cannot compensate for an overloaded CPU or slow disk.
The world will not start after an update
Stop trying different files against the only copy of the world. Restore the last known-good server folder and backup, then compare the update instructions and required client release. Test the new pack against a copy of the world before making it the group’s live server.
Quick Recap
What a successful setup looks like
- The server and every client show the same Vault Hunters 3rd Edition release.
- The server runs on 64-bit Java 17 and reaches its ready prompt without recurring startup errors.
- The host has roughly 4 GB plus 2 GB per concurrent player available to the server, with additional memory reserved for the operating system and any local client.
- Players on the LAN use the private address; remote players use the tested public address and port.
- The allowlist and operator permissions contain only the people who need access.
- A dated backup exists outside the live folder, and everyone knows how updates and maintenance will be announced.
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.
