premium banner
HyLogger makes sure that your server log will be saved for debuging purposes

Description

The mod itself just logs ev# HyLogger

Server-side Hytale plugin that captures the full server log and splits Hytale engine output from mod/plugin output into organized, timestamped files—so you can debug without wading through one giant log.


What It Does

HyLogger records all server console output to disk and sorts it into separate log files by source and severity. You get a complete audit trail of what the server and your mods did, plus dedicated files for Hytale-only errors, mod-only errors, warnings, and severe entries. No configuration needed: install the JAR and start your server; logs are created automatically.


Features

  • Full server log — Everything from stdout and stderr (including output written before the plugin loads) is written to a single timestamped file so you never lose output.
  • Organized by source and severity:
    • ServerLogs — Complete server output (*_full.log).
    • HytaleLogs — Hytale engine output (*_hytale_errors.log), identified by Hytale log tags (e.g. [HytaleServer], [PluginManager], [AssetStore|...], [SERR]) or package name com.hypixel.hytale.
    • ModLogs — Mod/plugin output (*_mod_errors.log). Both stdout and stderr are routed line-by-line, so mod messages (including most INFO lines) appear here, not only errors.
    • WarningLogs — All WARN/WARNING entries (*_warnings.log).
    • SevereLogs — All SEVERE entries (*_severe.log).
  • Operator alerts — When a server operator is online, SEVERE log entries trigger an in-game toast notification and a chat message so you can react without watching the console.
  • No config required — Drop the JAR in your mods folder and start the server; HyLogger creates the log folders and starts writing immediately.

Where Are the Logs?

All logs are stored under your server folder:

<server folder>/mods/HyLogger/

Subfolder What’s inside
ServerLogs/ Full server log files: YYYY-MM-DD_HH-mm-ss_full.log
HytaleLogs/ Hytale-only errors: *_hytale_errors.log
ModLogs/ Mod/plugin errors: *_mod_errors.log
WarningLogs/ All WARN/WARNING entries: *_warnings.log
SevereLogs/ All SEVERE entries: *_severe.log

Filenames include a timestamp (e.g. 2026-03-08_14-30-00_full.log) so each session has its own set of files. Stdout and stderr are both captured and routed line-by-line into the Hytale/mod/warning/severe files, and Java logging (JUL) is also captured, so you get output regardless of how the game or mods log.


Installation

  1. Download the latest HyLogger JAR from this page (Files tab).
  2. Place the JAR in your Hytale server’s mods folder (or plugins, depending on your setup).
  3. Start the server. HyLogger will create mods/HyLogger/ServerLogs, HytaleLogs, ModLogs, WarningLogs, and SevereLogs on first run and begin logging.

No config file or in-game setup is required.


Operator Notifications

If a player with the op permission is online when a SEVERE log entry is written (e.g. chunk load timeout, unhandled exception), HyLogger sends:

  • A toast notification (with a warning icon).
  • A chat message with the log level and message text.

Useful for catching critical issues without keeping the console or log files open.


Requirements

  • Hytale server (release or pre-release). The plugin targets a specific server build; use a JAR that matches your server version.
  • Server-side only — No client installation. Players do not need the mod.

Who Is This For?

  • Server owners who want a full, timestamped log and a quick way to see if a crash or warning came from the game or a mod.
  • Modders who want to separate their mod’s errors from Hytale’s in the logs.
  • Admins who want in-game alerts when something goes wrong, without watching the console.

Summary

HyLogger gives you a full server log plus split logs (Hytale vs mod, warnings, and severe in their own folders), with optional in-game operator alerts for severe entries. Install the JAR, start your server, and check mods/HyLogger/ServerLogs, HytaleLogs, ModLogs, WarningLogs, and SevereLogs whenever you need to debug. erything in the server log and saves it