Create a new setup or import config.json, adjust performance, backups and updates, then download ready-to-use files. Everything runs locally in your browser.
This tool brings the main setup decisions into one workflow: the server profile, connection values, Java memory, file paths, backups, update behavior, launch commands, and an organized download package.
It is designed as a reviewable starting point. The generated files should make setup faster, but they do not replace a backup, a test launch, or the current official server documentation.
Treat the generated files as a reviewed starting point, not as a blind replacement for a working server. Confirm the server name, bind and connection values, memory limits, backup behavior, update channel, folder paths, and operating-system commands before you use the package.
When you import an existing config.json, HyTools preserves properties it does not manage. That reduces accidental data loss, but you should still compare the new file with your current version and keep a backup before replacing anything.
Test the generated package in a separate folder first. Start the server, read the complete console output, confirm that the expected port is listening, and verify that save, backup, and restart behavior match your hosting environment.
After a Hytale server update, review the official server documentation again. Configuration names and defaults can change, so a previously valid file should not be assumed to remain correct forever.
| File | Purpose | Review before use |
|---|---|---|
| config.json | Server and update settings | Profile, limits, backups, update mode |
| jvm.options | Java memory and extra JVM arguments | Xms, Xmx, AOT path, duplicate flags |
| Launch command | Direct command for the selected layout | Paths, bind, assets, extra arguments |
| start.bat / start.sh | Repeatable startup and update wrapper | Working directory and permissions |
| README | Local setup summary | Paths and steps for the target machine |
The Hytale Server Manual is the source of truth for Java requirements, launch arguments, networking, AOT, view distance, backups, and the update-ready layout.
Yes. It generates a versioned config.json with the server profile and update settings selected in the assistant. Imported properties the tool does not edit are preserved, but production files should still be reviewed after Hytale server updates.
Yes. Select Import config.json to load supported values. Unknown properties are kept in the generated file so the assistant does not discard settings it does not manage.
No. Importing, validation, draft saving and ZIP generation happen in your browser. The optional password is excluded from the locally saved draft.
HyTools has a dedicated Ports and Firewall Assistant for network rules. This page stays focused on server configuration, JVM options, launch files, backups and updates.
No. Stop the server, back up the current folder and world data, compare the generated files, and test the new package separately before replacing production files.
No. Memory needs vary with player behavior, loaded world area, entities, mods, and hosting limits. Use the value as a starting point and monitor real CPU and RAM usage.
A practical path from an empty folder to a maintainable Hytale server, with the decisions that matter before players connect.
A safe, layer-by-layer method to make a local Hytale server reachable without disabling protection or exposing unnecessary services.
Turn a long log into evidence: locate the right file, preserve context, identify the first meaningful failure, and share only what support needs.
