Decide whether it is repeatable
- Note the exact action that makes the number increase: opening a menu, entering an area, using an item, or loading a save.
- Repeat that action once. If the number increases again, close the game and open
console.txt. - Find the first stack trace at that time and record any named mod, item, Lua file, Java class, or resource.
- Test the same action on a new unmodded save. If it stops, isolate the mod set in batches.
- If it persists without mods, verify the game files and capture a clean log for support.
How serious is the counter?
One increment with no visible effect may be nonfatal, but a rapidly increasing count, broken interface, failed action, or crash deserves investigation. The severity comes from the behavior and trace, not whether the box displays 1, 2, 3, or 4.
Common diagnostic outcomes
- A mod or modded item is named: check its Build compatibility and dependencies, then isolate it on a copied or new save.
- The error starts only after entering one area: consider a map or spawned-content mod that loads on demand.
- The trace names a base-game file and also occurs in vanilla: verify game files.
- No repeatable action and no gameplay impact: keep the log and watch for a pattern before making disruptive changes.
Sources
The Indie Stone forum: what “Error 4” means — Official support explanation of the counter.
The Indie Stone forum: red box with number 2 — Historical official support discussion.
Community example: Error 2 — Community example, not a fixed-code definition.