Where to Find Hytale Logs and How to Analyze Them

1. Reproduce the issue in a controlled way

Before opening files, write the action that triggers the problem and the approximate time. If possible, restart once, perform only the failing action, and stop. This reduces noise from older sessions.

Do not repeatedly retry dozens of times. Repetition can flood the end of the log and hide the first useful stack trace.

2. Open the official log locations

The official support guide lists platform-specific client folders and a logs directory inside each saved world for the local server. Use the newest file that matches the time of your test.

On shared or hosted servers, the provider may expose the same files through a panel or file manager. Download the original text file rather than copying only a screenshot.

• Windows client: %APPDATA%\Hytale\UserData\logs
• Windows world server: %APPDATA%\Hytale\UserData\Saves\[world]\logs
• macOS client: ~/Library/Application Support/Hytale/UserData/logs
• Linux client: ~/.local/share/Hytale/UserData/logs

3. Choose the correct session and preserve the original

Sort by modification time and compare timestamps inside the file. Make a copy before trimming or adding notes. Compression is useful for very large files, but keep a plain-text excerpt for quick review.

Include the client log when the client crashes or cannot join. Include the server log when startup, world loading, commands, mods, or all players are affected. Sometimes both sides are needed.

4. Find the first meaningful failure

Search for severity words such as ERROR, WARN, exception, failed, caused by, or timeout. Then move upward and read the preceding lines. Initialization messages often reveal which component was loading when the failure began.

A warning is not automatically the cause. Many applications log recoverable warnings. Give more weight to a clear exception, repeated failure tied to the symptom, or the first error after the triggering action.

5. Read a stack trace without guessing

Start at the exception message and look for a 'caused by' chain. The deepest cause often describes the concrete issue, while upper frames show how the program reached it.

Names of packages, mods, paths, configuration keys, and resource IDs are clues. They are not proof by themselves. Confirm by reproducing after reverting one relevant change at a time.

6. Use the HyTools Log Analyzer

Paste or import the log into the browser-based analyzer. It highlights severity, groups useful lines, lets you navigate occurrences, and helps prepare a compact report. Processing happens locally in the browser.

Use filters to reduce visual noise, but return to the unfiltered context before concluding. Copy the relevant block with several lines before and after the failure.

7. Prepare a support report that can be acted on

A useful report states what you expected, what happened, exact reproduction steps, time, game/server version, operating system, recent changes, and the relevant log excerpt or attached file.

Avoid vague titles such as 'it broke'. Describe the affected action: 'server stops while loading world after adding mod X' or 'client disconnects when joining one world'.

1. 1

   Write a one-sentence problem summary.

2. 2

   List the smallest reproduction sequence.

3. 3

   Record versions and recent changes.

4. 4

   Attach the original log privately when needed.

5. 5

   Paste a short reviewed excerpt in the message.

6. 6

   State what you already tested.

8. Share logs safely

Logs can contain usernames, local folder names, server addresses, authentication details, and third-party plugin data. Search before posting publicly and redact only sensitive values, not the technical context around them.

When reporting to an official or trusted support channel, follow its upload instructions. Do not modify the original file you keep for your own investigation.