Design Patterns in Games
summary
Shows how using dependency injection (Zenject), MVC-style models for UI, and state machines in Unity reduces bugs and speeds development. Replaces fragile singletons with Zenject installers and hierarchical contexts, enables tests to inject fake time and controllers to reproduce and reliably run rare (~0.1%) bugs, makes random-driven systems deterministic for benchmarking, and moves gameplay stats into a model so UI becomes testable and portable, illustrated with Unity examples and measured results from a multi-year project.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 3:55Dependency injection
- 20:50MVC in games
- 36:18State machines in UI
- 41:44Observer and summary
related talks
55mLet's Make Unity Great Again
46mTechniques for making reusable code
51mArchitecture of Your First Unity Project
41mPanel: What Tools all Game Developers Should Have at Hand at all Times
20mStudio Speaks: The Reality of AI Adoption in Games
43mIntroduction to Data-Oriented Design in Unity
50mDomain-driven Game Design
26mGetting the Job Done: Using Everything to Make Your Game