share post Gaming is a vast industry that is continuing to grow. Multi-player cloud-based games especially are becoming more popular and taking the market by storm. With everything going on in the world, it’s no wonder people are looking for a bit of downtime and a way to escape the tribulations of everyday life. Game developers face many challenges in order to get their games on the screens of as many global players as possible.

Try to imagine a bunch of monkeys running around your data center, pulling cables, trashing routers and wreaking havoc on your applications and infrastructure. Ever more crucial in these days of heated competition between online gaming operators, is player experience. Continuity of operations is “Uber-Alles” and avoiding churn, due to service disruption, is the organizational mantra.

At Cloudsmith we love playing video games, everything from Super Meat Boy to Halo, Fortnite to Candy Crush. We’ve got a big Pac Man money box sitting on the office shelf. Steve Collins, of Havok fame, is on our Board of Directors. Quite simply, gaming is in our DNA. When we started Cloudsmith we made a list of customers we’d love to work with someday and there were numerous games studios on the list.

Managing modern mobile games involves measuring and tracking dozens of metrics. Each value lets you know how well your game is doing in a specific area, such as user experience, infrastructure, and monetization, to name but a few. But not all KPIs are created equally. Some metrics are more valuable than others in terms of helping you make informed business and technical decisions about your game. That’s what we’ll take a look at in this article.

Kimberley Wadsworth gambled £36,000 in a fortnight, committing suicide shortly after the loss and leaving her mother homeless as a result. Kimberley Wadsworth started gambling in 2015, visiting brick-and-mortar shops and playing at online casinos. There was no one to promptly alert or save Kimberly from her dreadful destiny.

Crash Report Client is an Unreal Engine tool that allows developers to capture C++ crash reports from supported platforms. At crash time, a dialog is shown to the user so that they may add comments or replication steps to the details of the report. Once the crash report is submitted, it’s pushed to one of Epic’s servers so that developers can review the crash and fix the underlying issue. Often, the crash is a result of code that wasn’t written by Epic.