Dimensional Data

Having a firm grasp on the resources, currencies, sources, and sinks in your game is a great start to building a healthy economy, but understanding what behaviors exist within your player base will allow you to tailor your reward and progression design choices.  In this guide, we’ll dive into how you can design your economy around different types of players through the following topics: Payer vs. non-payers Different levels of engagement Player motivations Planning your player journey Using A/B testing to improve your in-game economy Learn about our suggestions for each player type and the variables you should test in Designing a balanced in-game economy. By developing a strong understanding of sources and sinks, currency and resource management, as well as the various types of players of your game, you’ll be fully equipped to create a healthy in-game economy that can drive player engagement.  Start learning today in the first of our introduction to economy series: What is an in-game economy, or skip to Building an in-game economy and Designing a balanced in-game economy. If you want to get started building your own game economy, Economy from Unity Gaming Services has everything you need to design and manage it. If you feel you’re ready for A/B testing, Remote Config lets you run different tests that target specific player segments without code changes or app updates.

Perfecting your game’s design can be difficult when you can’t see how your players interact with it. By doing A/B testing, you can make design decisions based on how your players really play the game. The Unity Gaming Services (UGS) Use Cases are a collection of samples that implement typical backend game use cases and game design elements, show how to resolve specific development tasks, and highlight the efficiency you can achieve in your game backend by integrating different UGS packages in your project. One of these samples is about A/B Testing.This lets you segment players into multiple test groups in order to determine which version of a specific game element is the most engaging or intuitive to your players. The example we show is testing the amount of XP required for leveling up. This particular example is suited for something like alpha playtesting of a single-player game. But this is just one example, and there are many potential uses for A/B testing with UGS, even in published or multiplayer games.