Player.log Analyzer
Player.log Analyzer
Section titled “Player.log Analyzer”You do not need to understand every line before you can start debugging. Drop Player.log below or paste its text.
LOG
LOCAL-ONLYWorkbench
Player.log Analyzer 2.0
The file is processed locally in your browser. It is not uploaded anywhere.
RULEThe analyzer recognizes signatures and routes you to documentation. It does not claim a root cause without enough context.
Environment summary
Detected signals
What to do next
Loaded mods
What 2.0 does
Section titled “What 2.0 does”It extracts the current WorldBox build, NeoModLoader version, PoliticalWorldAPI version and loaded mods, then groups recognizable signals such as:
- C#
CSxxxxcompiler errors; StackOverflowExceptionandNullReferenceException;- Event Bus callback failures;
- NML listener construction failures;
- Political World
WARN/ERRORdiagnostics; - Harmony/patching signals;
- missing localization;
- common network/TLS and fallback-library noise.
Each recognized group links to the most relevant guide/reference we currently have.
Important boundary
Section titled “Important boundary”This is triage, not an automatic root-cause oracle. A signature can prove that a certain exception/error exists; it usually cannot prove why it happened without surrounding context and reproduction.