Skip to main content
Errors and crashes are events, as in GameAnalytics and PostHog. An error goes into the same table as your other events, with the same player, session, build and platform. So you can use errors in funnels, retention, filters and charts. For example:
  • Do players from one campaign crash more often?
  • Did the error rate go up after build 572?
  • Do players who get an error in level 3 stop playing?
ManaLens does not store native crash dumps or symbols. For native crashes (a segfault in the engine or in a GDExtension), keep Sentry or Backtrace. ManaLens still counts these crashes, with app_unclean_exit.

The events

app_unclean_exit has the session ID and the time of the run that crashed, so it counts in that session and that build. A game that the operating system closed in the background is not counted. A normal quit (with or without shutdown()) is not counted. Properties of error:

Send errors from Godot

On Godot 4.5 and later, the SDK also sends engine and script errors (for example push_error(), a call on a null instance, or a failed load()). It uses OS.add_logger(). Set capture_engine_errors to false to turn it off. Warnings are off by default (capture_warnings). In release exports, script stack traces need the project setting debug/settings/gdscript/always_track_call_stacks. On Godot before 4.5, use track_error(). The crash event works on every version.

Send errors from Unity

The Unity SDK also sends unhandled exceptions, Debug.LogError and failed asserts, from any thread (Application.logMessageReceivedThreaded). Set CaptureErrors to false to turn it off. Warnings are off by default (CaptureWarnings).

Grouping

By default the fingerprint is a hash of error_type, file and function. The line number is not in it, so an edit above the error keeps the group. Without a file or function, the hash uses the message with numbers and quoted text removed: Save failed for slot 3 and Save failed for slot 4 are one group. Set fingerprint in track_error() to group in your own way.

Limits

track_error() calls do not count toward the session limit. The SDK adds the number of dropped errors to the next session_end as errors_dropped.

Remove personal data

The function gets the properties of each error event. Return the properties to send, or null to drop the error.

Game health board

Open Dashboards, click the Game health template under Templates, then click Create board. It has:
  • Crash-free sessions: 1 minus the share of sessions with app_unclean_exit or a critical error with handled = false.
  • Crash-free players: the same, with distinct players.
  • Errored sessions: the share of sessions with an error or critical error. Warnings do not count.
  • Errors per session and Errors per session by build.
  • Top errors: one row for each fingerprint, with the latest message, count, players, first and last time seen in the date range, and the latest build.
The board reads game events: client events with context.app, from a native build or from a browser game that sets the web SDK app option. These are SQL charts, so you can edit them in the chart editor. Rates over date ranges of different lengths are not comparable: a longer range has more sessions for each player.

Other engines

Any engine can send error and app_unclean_exit to the events endpoint. Use the same property names, so the Game health board works.