Read your game's counts and crash reports
Use Overview to understand activity and investigate reported failures.
Steps
- Open Your games and select the game’s Overview.
- Check the live release and the reporting dates.
- Read Views, Starts and Plays.
- Use From the page to playing to compare the stages.
- In Health, review failed loads and any crash reports.
- Read a frequent crash’s message and code location.
- Choose Fix it in the Studio where offered, or open the linked project.
- Reproduce the error, make a fix, test it and publish a new release.
What the counts mean
| Count | Meaning |
|---|---|
| Views | Game-page loads. |
| Starts | The player pressed play. |
| Plays | Activity counted after the platform sees real input and time on screen. |
| Crashes | Reported failures, not a count of distinct players. |
Counts appear after a day is complete. A visit you just made will not necessarily appear. Read any testing-only notice before interpreting the figures as public activity.
If information is missing
A game with no finished days or no live release may have no relevant figures yet. Detailed crash information is retained for a limited period. Keep the relevant error text in your own fix notes while investigating.
A missing crash entry is not proof that every player had a successful session.
Still stuck?
Email support@4rc4d3.com with the project or game name, if relevant, the action you tried and the exact error. Never include passwords, authenticator codes, backup codes or AI keys.