Tool time is the development phase for editing, validating, and preparing game data before runtime. Separating balance data from runtime assets can make it easier for designers to change and test game rules. section 9.0
Validate balance data before parsing it at runtime: checks for missing or incorrect values can then be omitted from gameplay code, reducing complexity and runtime work. Keep tool-time code separate from runtime code to avoid adding unnecessary libraries to the build or accidentally calling preparation functions during play. section 9.0 section 9.3
Common uses include:
- Store balance data in an external asset, so designers can edit rules independently of the Unity scene and update them more readily. section 9.0
- Assign IDs or indices to data before runtime, then use arrays instead of repeated dictionary lookups during gameplay. section 10.7 section 10.8
- Track balance versions so gameplay changes can be identified when reproducing player issues. section 9.3
Move a check out of gameplay
Validate that a balance value is greater than zero at tool time. Because the data has been checked, runtime code can rely on it instead of repeating the branch check during play. section 9.0
