In Part I in our series outlining best practices for scaling observability, we reviewed the data analysis capabilities that can help engineers troubleshoot faster during high pressure situations during a game launch. Nobody wants lag time or crashes in their game launch. Similarly, no one wants terminated sessions or for your gamer customers to log off and play a competitor’s game.

After months–or potentially, years–of hard work by teams across a gaming enterprise, when the day arrives for a game launch, the last thing your enterprise needs is slowdowns, glitches, outages or poor performance. It’s the death knell for any game, because for your avid gaming customers, there’s always something else (read: a game that isn’t yours) to check out.

In 2018 we launched the Sentry Unity SDK, but at the time, we couldn’t crack how to display stack trace line numbers for C# exceptions with IL2CPP scripting backend. And until a recent release of Unity, we thought it wasn’t possible. But here at Sentry we often do the impossible… or at least the improbable. Like adding features to our JavaScript SDK while making it smaller at the same time.

Playing online games is not only a mere leisure activity, but a main job for some people. Working as a game player is not something odd or unheard of anymore. Some gamers generate more income than corporate workers. It’s true. For example, Johan Sundstein earns more than $7 million per month just for playing games. What a life! The most recent trend in the online gaming industry is blockchain games.

Welcome to the final article in this Unity series where we are developing a Unity game.