Paste a server log to highlight errors, warnings, authentication issues and stack traces. Filter the result, jump to important lines and create a support report locally.
A long log can contain many secondary errors after one earlier failure. Start near the first severe exception, then read the surrounding lines for file names, mod identifiers, versions, player actions, or configuration values that explain what happened before the cascade.
Warnings are not automatically harmless, and errors are not automatically the root cause. Compare timestamps and repeated patterns before deciding what to disable or replace.
Remove passwords, tokens, private hostnames, internal addresses, personal data, and unrelated chat before posting a log publicly. Keep enough surrounding context for another person to understand the sequence of events.
When asking for support, include the Hytale server version, relevant mod versions, what changed before the problem, and the smallest repeatable steps. The analyzer helps organize evidence; it does not replace testing or the maintainer’s documentation.
No. Every byte stays in your browser. The analysis is 100% local.
No. It highlights suspicious lines and common patterns so you and your team can diagnose issues faster.
Start with the section around the crash, boot failure, authentication error, or connection problem. The full boot log also works.
