Part 1: Send errors and crashes
1
2
Let the SDK capture engine errors
On Godot 4.5 and later, the SDK sends engine and script errors as
error events. This is on by default (capture_engine_errors).3
Report your own errors
Call
track_error() where your game catches a failure:4
Count crashes
You do not need to do anything. At the next launch after a crash, the SDK sends
app_unclean_exit in the session and build that crashed.ManaLens does not store native crash dumps or symbols. Keep Sentry or Backtrace for those. Other engines can send the same
error and app_unclean_exit events to the events endpoint.Part 2: Open the Game health dashboard
- Open Dashboards.
- Under Templates, click Game health. The preview shows your data for the last 30 days.
- Click Create board.
Part 3: Find what to fix
- After a release: filter the dashboard by Build (App group). Compare Errors per session by build with the build before.
- By platform: filter by Platform to find a crash on one operating system.
- Effect on players: add the filter Event property
severityiscriticalto a retention chart. It keeps only players with a critical error. Compare it with all players. - Before the error: open a player from the Users page to see their events. Each
erroralso hasbreadcrumbs: the last 20 event names.
Part 4: Keep personal data out
Useset_before_send() to drop or clean an error before it leaves the game. Do not send email addresses or other personal data in message.
Related
- Errors and crashes: every property, grouping and limit.
- Godot SDK
- Unity SDK
- Game events reference