Mistakes With Data Made During Game Development
summary
Game data breaks because formats lack explicit versioning, version control stores built assets, dependencies live only as string literals, and large mixed files create edit bottlenecks. Practical fixes: include a top-level file version plus per-field versions; use Perforce or similar for source only and keep generated assets in an external cache; record explicit dependency lists inside binaries or stable sidecar metadata; split editable components into separate files; eliminate nondeterminism by clearing padding/initialized memory before serializing and sorting arrays or assigning load indices so diffs and caches remain stable.
AI-written summary · about
chapters (8)
- 0:00Data handling mistakes
- 0:27Missing version numbers
- 2:53Version control for assets
- 5:26Implicit dependencies risks
- 8:35Manually edited file lists
- 9:38Single file storage
- 11:24Nondeterministic files
- 16:04Summary
related talks
59mUnsaved Progress Will Be Lost: Why the Game Industry Forgot How to Make Games, and How to Fix It
08mInterview with
41mPanel: What Tools all Game Developers Should Have at Hand at all Times
34mArchitecting Content for a Live Service Game
21mWhen the Shit Hits the (RGB) Fan: What Can Go Wrong When Making Multiplayer Games
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
31mWhen the data levee breaks: Managing cognitive load in data-intensive projects
43mScaling Indie - Making Bigger Games With Unity