Your Game Works… Until Someone Else Plays It!

Summary

The video explains why bugs that do not appear during development can still break a game for players. It shows how quick, automated error reporting can help developers diagnose issues before they lead to widespread frustration, refunds, or negative reviews.

Bugs Demonstrated

• Frozen build menu: A missing serialized reference caused an exception when the game tried to create a machine. The error report included the relevant code location, logs, and a screenshot, helping trace the issue to an unassigned prefab reference.
• Save failure: A save operation failed because the expected directory did not exist on the player’s computer. The fix was to check for the directory and create it if necessary. The speaker says a similar bug occurred in one of his own games.
• Event error in a larger game: In a complex Unity project, an event tried to update an object that had already been destroyed. The likely cause was that the object had not unsubscribed from the event before being destroyed.

Tool and Workflow

The video demonstrates Sentry, a sponsored error-monitoring tool for game projects. Instead of relying on players to find local logs and send them manually, developers can view reported errors in an online dashboard. Reports can include:

• Exception details and stack traces
• Logs leading up to the error
• Screenshots of the game at the time
• The affected code location, with repository integration
• Information about the player’s device

The speaker demonstrates setting up Sentry in Unity through its package manager and setup wizard. He also mentions optional custom data and metrics, an AI debugger that analyzes logs, and the ability to mark issues as resolved. The video presents the service’s free option for solo developers and pricing for small teams as claims made during the sponsored segment.

Guides and Tutorials

• The video provides a practical walkthrough of diagnosing three types of game bugs using error reports, logs, and screenshots.
• The speaker briefly references a separate tutorial on creating an in-game error detection window, noting that a local window does not automatically send diagnostic information to the developer.

Main Speaker and Sponsor

• Main speaker: Code Monkey, presenting as “CodeMage”
• Tool discussed: Sentry, identified in the video as its sponsor