Source metadata

Key takeaways

  • The playbook treats engine workflows as design levers: better data structures and tooling make iteration faster and more reliable.
  • It highlights ScriptableObjects, Input System, Starter Assets, and Animator Controller as practical tools for prototyping and tuning.
  • The guide repeatedly focuses on how designers can change behaviour and feel without rewriting core systems each time.

Notable claims

  • ScriptableObjects are framed as a design-tuning convenience as much as an engineering pattern.
  • The Input System is valuable to designers because action maps and bindings can change without rewriting gameplay scripts.
  • Animator-driven prototyping is treated as a legitimate design workflow, not just a final polish step.

Relevance

This source primarily informs:

It also supports:

Open questions raised

  • Which parts of the playbook deserve their own dedicated prototyping workflow pages later?
  • How much should the vault foreground designer-facing use of Unity tools compared with programmer-facing explanation?