liveBook · Manning

Chapter 9: Tooltime data parsing

What you will learn in chapter 9 of High Performance Unity Game Development

The introduction explains why separating balance data from Unity scene and runtime assets can improve designers’ workflow, reduce runtime checks, and support live updates and testing.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The introduction explains why separating balance data from Unity scene and runtime assets can improve designers’ workflow, reduce runtime checks, and support live updates and testing.

Key terms: balance data, Game GameObject, Unity scene, external asset, tool time, validating, parsing, runtime, live-updating the balance, versioning

9.1 Moving balance data to an external asset

The section explains why balance data moves out of the Game object, how Google Sheets and ScriptableObjects serve different needs, and how ScriptableObject data becomes the game's runtime balance.

Key terms: Google Sheets, balance, binary format, ScriptableObjects, version control, data types, source of truth, runtime balance file, game designer, engineer

9.2 Parsing the balance

This section explains how the BalanceParser produces a binary balance file at tool time and why balance versioning becomes more important if values can change after release.

Key terms: BalanceParser, FileStream, BinaryWriter, byte array, tool time, game version, balance, live-update, balance version, existing values

9.3 Loading the balance

This section explains why loading balance data differs from loading saved game data, including the need to control its source, allocate from its contents, and keep tool-time work out of runtime.

Key terms: balance data, game data, tool time, runtime, resource folder, balance version, multiple sources, LoadBalance(), GameData, Balance.NumEnemies

9.4 Validating balance data at tool time

This section explains how validating balance data before parsing lets the game avoid repeated runtime checks while catching authoring mistakes.

Key terms: validate(), parse(), tool time, balance.NumEnemies, AllocateGameData(), runtime checks, branches, MAX_ENEMIES, ScriptableObject, sprites

9.5 Handling live balance updates

This section explains why live balance updates require separate version tracking and recommends a single loading source to avoid uncertainty about which balance users have.

Key terms: balance, app version, live-updating the balance, balance version, old balance versions, game data, single source, loaded locally, downloaded every time the user starts the game

9.6 A/B Testing

The section explains how separate balance data makes it easy to A/B test gameplay changes and compare their effect on player retention.

Key terms: A/B testing, retention, balance, balance data, balance A, balance B

9.7 Conclusion

This conclusion explains how external balance data supports a collaborative workflow, tool-time validation, live updates, and controlled testing of balance versions.

Key terms: balance, Google Sheets, ScriptableObject, QA, tool time, binary data, runtime checks, live-updating the balance, single source, A/B testing

9.8 Summary

The chapter summary explains how to author, parse, validate, version, and test balance data kept separate from the game project.

Where this is used later

Concepts explained in this chapter

← Chapter 8: Separating asset data and logic Chapter 10: DOD and Dictionaries →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.