Game Design Framework

3. Response

• Does the game respond INSTANTLY to player input? (<100ms)
• Is feedback proportional to action? (small action = small feedback, big action = big feedback)
• Sensory channels: visual + audio + haptic (at least 2 of 3)
• Rules: Delayed response kills engagement. Silent success is invisible success.

4. Satisfaction

• Does completing the mechanic feel GOOD?
• Is there a "moment of delight" — confetti, sound, screen shake?
• Does difficulty match skill? (Flow state: not too easy, not too hard)
• Rules: If the player completes something and feels nothing — redesign. Satisfaction = effort × surprise.

5. Fit

• Does this mechanic belong in THIS game?
• Does it support the theme/narrative/world?
• Would removing it make the game worse?
• Rules: Cool mechanics that don't fit are worse than no mechanics. Every system must earn its place.

Numbers Policy

When designing game systems with numbers (HP, damage, XP, timers):

1. Start with feeling, derive numbers — "this should take 3 hits" → HP=30, damage=10
2. Use round numbers — 100 HP, not 137. Players do math in their heads.
3. Make progression visible — XP bar, not hidden threshold
4. Balance formula: difficulty = base × (1 + level × 0.15) — 15% increase per level feels gradual
5. Timer sweet spots: micro-challenge = 30s, puzzle = 3-5min, session = 15-20min

State Machine Checklist

Every interactive element must have defined states:

Assumption Labeling

When making design decisions, label your assumptions:

• [TESTED] — Validated with real players
• [ASSUMED] — Based on design principles, not tested
• [RISKY] — Goes against convention, needs testing
• [PLACEHOLDER] — Temporary, will be replaced

Puzzle Design Principles

For educational/narrative games:

1. The puzzle IS the lesson — Don't explain then quiz. The solving process teaches.
2. Fail forward — Wrong answer = new information, not dead end
3. 3 difficulty tiers: Easy (confidence builder) → Medium (learning) → Hard (mastery)
4. Hint system: Passive (environmental) → Active (NPC speaks) → Direct (solution shown)
5. Time pressure: Use sparingly. Timer = stress. Stress ≠ learning. Use countdown only for action sequences, never for thinking puzzles.

Session Structure (20 minutes)