How to Install Hytale Server Mods and Plugins

Hytale server mods are installed from .zip or .jar packages placed in the server's mods/ directory. The file copy is easy; the important work is verifying the source, matching versions, backing up the world, and testing a rollback before players depend on the change.

Before installing a mod

Record the current server version, patchline, mod list, and last successful startup. Then make a restorable backup of:

• universe/
• config.json and world configuration
• permissions.json, whitelist.json, and bans.json
• The complete mods/ directory

Stop the server cleanly before copying or removing mod files. A filesystem copy taken during an active save can preserve inconsistent world data.

Only download mods from sources you trust. The official server manual points operators to CurseForge as its mod reference. A mod executes code or changes game data inside an important service; popularity is not a substitute for reviewing its publisher, permissions, update history, and reported issues.

Install a server mod

1. Stop the Hytale server.
2. Confirm that the mod supports your exact release or pre-release build.
3. Copy its .zip or .jar package into mods/ without extracting it unless the author explicitly says otherwise.
4. Start the server and watch the console and newest file in logs/.
5. Join with a test account and exercise the feature in a disposable area.
6. Restart once more to prove that the world and mod load cleanly after a save.

Install one change at a time. If five mods are added together and startup fails, the logs may show only the first symptom rather than the incompatible package that caused it.

Client and server compatibility

Some experiences need content on both the server and connecting clients; others are server-side. Follow the mod author's compatibility instructions and do not assume every package is transparent to players.

Hytale also requires compatible client and server protocol versions. A server that worked before an official patch may reject players even when no mod changed. Update the base server and assets together, then confirm each mod supports the new build before returning the production world to service.

Keep release and pre-release installations in separate directories. A pre-release mod or world migration may not safely roll back to the public release.

Early plugins and --accept-early-plugins

The official server exposes an --accept-early-plugins launch argument. Its name is the warning: early plugins may target unstable interfaces and create greater compatibility or security risk than ordinary tested content.

Do not add the flag merely because a package fails to load. First verify that the package genuinely requires it, comes from a trusted developer, and has a documented recovery path. Test early plugins on a copy of the world, not the only production save.

Updating a mod safely

Use a staged workflow:

1. Read the mod changelog for migrations, removed configuration, and supported Hytale builds.
2. Stop the server and take a new backup.
3. Keep the previous mod file outside mods/ as a rollback artifact.
4. Replace the package; do not leave two versions active.
5. Start the server and inspect the first warning or error.
6. Test joining, saving, restarting, and the mod's core behavior.

A successful process start is not a complete test. Data migration problems can appear only after the first save or second restart.

Fix a server that fails after adding mods

Start with the newest log and the first mod-related error. Then:

• Stop the server and move the newest package out of mods/.
• Retry with the exact last-known-good mod set.
• Confirm the base server and Assets.zip match the client build.
• Validate any JSON configuration created by the mod.
• Check for duplicate versions or dependencies.
• Restore the pre-change world if the mod already migrated or damaged data.

Do not repeatedly start a production world while changing random packages. Each startup can run migrations or write new state, making rollback less reliable.

Remove a mod

Removal is not always the reverse of installation. A mod may have created blocks, entities, items, permissions, or configuration referenced by the world. Read its uninstall instructions first. When none exist, test removal against a copy and inspect the logs for missing identifiers before touching production.

Maintain a simple manifest containing the filename, source URL, installed version, compatible Hytale build, installation date, and reason for the mod. That record makes updates, audits, and support far faster than guessing from a folder of renamed JAR files.

Verification standard

Hytale Server Tools labels a mod compatible only when its publisher documents support for the targeted Hytale build or it has been tested against that build. “Loads without an immediate error” is not the same as verified compatibility.

For base-server updates and rollback planning, use the automatic updates guide and backup and migration guide.

Official reference

• Hytale Server Manual