How to Set Up a Hytale Server: Files, Java, Memory, and First Launch

1. Decide what the server must support

Write down the intended player count, whether the server is private or public, the operating system, the world type, and whether you will use mods. These choices affect memory, network exposure, backup frequency, and how cautiously you should update.

For a first test, keep the environment intentionally small. A clean baseline makes it much easier to identify whether a later problem came from the server itself, a configuration change, or an added mod.

• Choose a permanent server folder rather than Downloads or the desktop.
• Reserve a separate location for backups.
• Record the server version, Java version, installed mods, and important config changes.
• Use a non-administrator operating-system account whenever practical.

2. Install and verify Java

The official manual currently requires Java 25 for the dedicated server. Install a compatible 64-bit runtime and verify the command available to the account that will run the server.

Do not assume the newest Java installation is the one used by your launch script. A service, terminal, or control panel can point to a different executable. Save the result of the version check in your setup notes.

java -version

3. Create a predictable folder structure

Keep the executable files and generated data easy to distinguish. A simple structure helps when you need to restore only a world, compare configuration files, or collect logs for support.

Do not store live backups inside the same folder that you routinely delete or replace during updates. At least one recent backup should exist outside the active server directory.

• server/ — active server files and launch scripts
• server/config/ — reviewed configuration files when supported by your layout
• server/backups/ — short-term local copies
• backups-offsite/ — a second copy on another disk or provider
• notes/ — update log, mod list, and recovery steps

4. Generate and review configuration files

Use the HyTools Server Configuration Assistant to prepare config.json, JVM options, and launch files for your operating system. Import an existing config when migrating so unknown properties can be preserved rather than silently discarded.

Treat generated files as a starting point, not an excuse to skip review. Confirm names, paths, ports, memory values, update behavior, and backup settings before the first launch. Avoid copying random flags from unrelated Java games.

5. Give the server enough memory without starving the machine

The official manual lists at least 4 GB of RAM for the server. The useful allocation depends on the operating system, active worlds, players, mods, and other services running on the same machine.

Leave memory for the operating system and monitoring tools. Allocating every available gigabyte to Java can cause paging and make the entire machine less stable. Increase memory after observing real usage instead of guessing an extreme value.

6. Perform a local first launch

Start the server before exposing it to the internet. Watch the console, wait for the world to finish loading, connect from the same machine or local network, and confirm that stopping the server produces a clean shutdown.

After the first successful run, inspect the generated folders and logs. Save a backup of this known-good state. It becomes the fastest comparison point if a later update or mod causes trouble.

1. 1

   Run the launch script in a visible terminal.

2. 2

   Wait for the server to report that startup is complete.

3. 3

   Join locally and perform a basic movement and interaction test.

4. 4

   Stop through the supported server command, not by killing the process.

5. 5

   Copy the clean configuration and world to your backup location.

7. Open access only after the local test passes

For public access, configure the host firewall and router or provider rules for the server's UDP port. The official manual uses UDP 5520 as the default. Avoid exposing unrelated ports and do not disable the entire firewall just to make a test work.

Use the HyTools Ports and Firewall Assistant to build a platform-specific checklist. Test from a device outside your home network because a successful local connection does not prove that internet routing is correct.

8. Prepare for updates, backups, and recovery

A server becomes reliable through routine operations. Back up before updates, change one major thing at a time, and keep a short changelog. Verify that backups can actually be restored; an untested archive is only a hope.

Before inviting a larger audience, use the Launch Checklist to review permissions, moderation, announcements, backups, network access, and rollback steps.