When building your next great game using the Unity engine, be sure to think about crash and exception reporting before it’s too late! Too often, development teams simplify this step by just writing errors to local log files so that they can collect the needed information when an issue occurs.
That’s useful in isolation, but how do you deal with crashes, exceptions, and errors when the game is in your players’ hands? How do you know which issues are affecting your most important users? How will you know which errors are actually new? How much time will you spend figuring out what to fix instead of doing the fixing?
Backtrace + Unity Engine = Better Games
Backtrace was built to answer these questions and more. With the new Plugin for the Unity editor, get to those answers in minutes. Built on our C# reporting library (read about it here), the plugin provides a simple way to configure your games to send crash and exception details automatically. Backtrace will enable you to quickly tell which issues should be prioritized. Configuration is as simple as filling out a form.
Crashes and exceptions will be grouped together and deduped automatically, enabling your team to prioritize problems based on the number of users impacted, severity of the issue, or any other reasons unique to your game.
What if I’m still developing my game?
Crash and exception reporting is not just for live production games. Teams who are in development can react more quickly to issues that surface as they are building new features. They can be confident knowing that crashes or exceptions encountered during CI/CD, regression suite execution, or early beta tests are captured and available for analysis. This helps minimize the amount of time teams need to invest to stabilize their game, and allows them to focus more on building great experiences.
You can go even further!
Some game development teams using the Unity Plus or Unity Pro plans may have already enabled the Unity Performance Reporting feature, which, similar to Backtrace, allows developers to collect and prioritize errors. This is a nice baseline to start from, but teams often outgrow the limited dashboard, which doesn’t offer much in the way of customization, query-ability, or integration to other tools like Jira and Slack.
Integrating Backtrace with your Unity games will give you new abilities to organize work based on real data. Want to focus on issues impacting new users? Issues that occur in the first 5 minutes of gameplay? Would you like to better visualize the aggregate instability in your game, so you can allocate resources to the modules or services that need the most amount of attention? Only Backtrace gives you this power to explore and make sense of all your exception data. Learn more about our plugin for Unity engine here.