Primary source
The way we play. Theory of game design
book_cube post pair [1/2] and [2/2] summarizing the book and practical takeaways.
Primary source
The way we play. Theory of game design
book_cube post pair [1/2] and [2/2] summarizing the book and practical takeaways.
The Way We Play
Authors: Michael Killick
Publisher: Apress
Length: 228
A practical entry point into game design: from ideation artifacts to Unity prototyping, level design, enemy systems and HUD/UI decisions.
OriginalDesign / Product / Systems / Leadership
The Way We Play is useful beyond game studios. It demonstrates an end-to-end product design cadence: concept framing, design artifacts, prototyping, mechanics, UX signaling and iterative delivery.
1. Book structure
1-2. Entering game design
Why games behave like complex systems, which roles compose a game team, and how designers align ideas through written artifacts.
3. From paper to screen
Narrative setup, character archetypes, traversal and camera perspective choices: 2D, 2.5D, 3D, first-person, third-person.
4. Unity practice (FPS controller)
A minimal first-person prototype: movement, camera setup and a simple playable environment.
5-6. Levels and enemies
Level design basics, onboarding for new players, enemy variation and why bosses create pacing peaks.
7. Mechanics, combat and multiplayer
How core loop, combat system and networking constraints must be designed as one cohesive block.
8-11. UI practice and final guidance
A 2D platformer Unity demo, HUD/UI principles, realistic goals and teamwork discipline.
2. Designer artifacts: one-pager to GDD
One-pager
A one-page concept frame: title, target audience, core mechanics, USP and competition context.
When it matters most: Best for early validation: is the idea focused enough to prototype?
Ten-pager
Expanded structure for character, world, gameplay, progression and replay motivation.
When it matters most: Aligns cross-functional teams before costly implementation starts.
Beat chart
A compact pacing map with key events, narrative beats, mechanic shifts and difficulty peaks.
When it matters most: Helps detect pacing gaps before heavy content production.
Game Design Document (GDD)
Operational source of truth for rules, constraints, system states and quality expectations.
When it matters most: Used by design, engineering, QA and production to coordinate execution.
3. Unity practice blocks
FPS demo (chapter 4)
Movement, camera setup and a tiny playable world to validate feel early.
2D platformer demo (chapter 8)
Prototype-first workflow: prove mechanics, then scale content and UX complexity.
4. Why this is useful for engineering leads
- Treat narrative, mechanics and UX as one product loop.
- Design levels and enemies as a learning and pacing system.
- Use HUD/UI as part of gameplay clarity, not as an afterthought.
- Protect realistic scope to ensure a truly playable outcome.
5. Common anti-patterns
Starting from visual polish before locking the core loop and player value proposition.
Writing a monolithic GDD that is disconnected from delivery stage and team needs.
Over-scoping early: open world, bosses and multiplayer without proving the base gameplay.
Treating HUD as secondary and discovering too late that players cannot read system state.
Designing enemies only by damage and HP while ignoring behavior diversity and readability.
6. Recommended patterns
Document value hypothesis first (one-pager), then expand to ten-pager and GDD.
Build vertical slices: one level, one enemy type, one combat loop, one UI context.
Separate static and dynamic HUD to reduce cognitive load during calm gameplay segments.
Design onboarding inside level flow rather than in detached instructions.
Protect realistic scope throughout production iterations.
7. Two-week starter sprint
- Write a one-pager and confirm shared understanding of core player fantasy.
- Prepare a ten-pager with world, mechanics, character and production constraints.
- Build a small Unity prototype (movement, camera, one interactive object).
- Draft a beat chart for 5-7 key events and validate difficulty pacing.
- Sketch first HUD wireframe and run a quick usability smoke test.