Let's Make Unity Great Again
summary
Argues that Unity’s usability gaps are fixed by three concrete systems with working code on GitHub: a resource Singleton pattern (ScriptableObject assets placed in Resources and auto-created next to their scripts) plus settings overrides to share defaults across prefabs; editor-visible preview models that instantiate then delete themselves before save so artists see real meshes without breaking prefabs; and a manager container that auto-constructs, topologically sorts dependencies, supports per-scene and global managers, and eliminates Behavior Singleton init-order bugs.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:05Why I still love Unity
- 3:57Unity workflow problems
- 11:21Why these problems matter
- 14:12Unity business vs usability
- 14:34Global settings in Unity
- 24:15Solving settings override
- 26:03Demo: global settings
- 28:11Bad idea: models in prefabs
- 29:13Preview models in editor
- 35:38Dangers of Behavior Singletons
- 37:05Singletons to ScriptableObjects
- 43:23Dependencies and execution order
- 45:09Manager containers for systems
- 48:19Demo: manager container
- 49:22Q&A: Models and workflows
- 53:46Q&A: Framework stability
