Domain-driven Game Design
summary
Build process uses Event Storming to find a single core mechanic: enemies become usable hats that grant abilities, and that mechanic drives all design choices. Implementation uses the Godot engine, hexagonal ports-and-adapters separation, and a mix of patterns including CQRS & Event Sourcing for inventories and HUD projections. Procedural world generation runs asynchronously, signals map engine events to domain commands, and adapters keep domain code pure. Prototype runs smoothly for small entity counts and supports native C++/Rust drops for heavy optimization.
AI-written summary · about
chapters (15)
- 0:00Start
- 4:24Godot Engine
- 8:26Domain Driven Design
- 9:03Separating Your Domain into Subdomains
- 9:40Collaborative Modelling
- 13:05Fighting System
- 14:21Event Storming
- 18:12Godot
- 19:23Graphical Overview
- 20:33Engine Methods
- 24:14Domain Driven Design Patterns
- 29:40Hexagonal Architecture
- 34:31Event Sourcing
- 46:41Performance Issues
- 47:52Swarm Behavior
related talks
47mDesign Patterns in Games
25mFrom concept to realization: technologies and decisions in the Godot playground
43mGame Design lessons from designing Football, Tactics & Glory
41mFunctional Game Engine Design for the Web
59mThe path to leveraging DOTS in production
43mIntroduction to Data-Oriented Design in Unity
53mBuilding a Doom-Like World to Explore Agentic Systems
44mBuilding an Indie Game in GO