Explainer · Game Design
Mechanics, dynamics and player experience
A mechanic is not automatically an experience. The interesting design work is in what happens when rules, players and context meet.
Use a simple chain
- Rule: the torch loses power while it is switched on.
- Play behaviour: players use short bursts, search for batteries and hesitate before dark spaces.
- Experience: tension comes from deciding when information is worth spending a scarce resource on.
Do not claim one guaranteed emotion
Different players may find the same pressure tense, annoying or trivial. Describe the intended experience, then use observation and feedback to see what the system actually produces.
Teach it backwards
Give learners an intended experience such as mistrust or relief. Ask for a rule, likely player behaviour and a cheap test that might create it.
Take one generated game idea and write a three-line rule → behaviour → experience hypothesis.
Keep moving
Useful next steps.
Turn a vague idea into one testable mechanic
Shrink a large concept into a prototype that can answer one design question this lesson.
Mechanic Mashup
Combine an unusual mechanic and genre, then turn the novelty into one playable rule rather than a page of lore.
Twine for branching prototypes
An open-source tool for making and testing nonlinear interactive stories in the browser or desktop app.