(CRE342 Lectures, see source-cre342-lectures)

Summary

Game atoms are the smallest indivisible units of meaningful interaction in a game. They are the raw material from which mechanics, dynamics, and aesthetics are constructed. Understanding atoms allows designers to analyse existing games with precision, identify the source of feel problems, and build new mechanics deliberately rather than intuitively.

The MDA framework (Mechanics-Dynamics-Aesthetics) provides the analytical lens; game atoms are what mechanics are made of.

(CRE342 Lectures, see source-cre342-lectures, mda-framework)

The five atom types

Atom typeDefinitionExample (Pac-Man)
ActionsPlayer inputs — what the player can doMove (up/down/left/right)
ResourcesCollectables or tracked valuesPellets, Power Pellets, Lives
GoalsObjectives that drive engagementClear all pellets in the maze
RulesConstraints and logic governing playColliding with ghost without power-up = lose life
FeedbackVisual, audio, or haptic responses confirming outcomesSound effects, score increase, ghost flicker

Every game mechanic is a structured interaction between atoms.

From atoms to mechanics: the 5-step mapping process

Step 1: Identify the atoms

List all Actions, Resources, Goals, Rules, and Feedback in the game or mechanic under analysis.

Step 2: Combine atoms to form mechanics

Identify which atom combinations produce coherent interactive units.

Pac-Man mechanics example:

MechanicConstituent atomsDescription
MovementAction (Move) + Rule (wall constraints) + Feedback (animation/sound)Player navigates maze but cannot pass walls
CollectionAction (Move) + Resource (Pellet) + Feedback (sound + score)Moving over a pellet consumes it and scores points
AvoidanceAction (Move) + Rule (ghost collision = death) + Goal (survive)Player must avoid ghosts to maintain progress
Power-upResource (Power Pellet) + Rule (ghosts become vulnerable) + Feedback (ghosts turn blue)Temporarily enables ghost-eating

Step 3: Identify emerging dynamics

Mechanics combine to produce dynamics — player behaviours and strategies not explicitly programmed.

Pac-Man dynamics:

  • Risk-reward balancing: Collection + Avoidance → choosing whether to chase pellets near ghosts
  • Strategic timing: Power-up + Avoidance → saving Power Pellets until ghosts are nearby
  • Spatial awareness: Movement + Maze layout → planning safe routes and anticipating ghost patterns

Step 4: Map to aesthetic experience

Dynamics produce aesthetic responses — the emotions and experiences the player has.

Mechanic/DynamicAesthetic outcome
Collecting pelletsSatisfaction, rhythm, flow
Avoiding ghostsTension, fear, excitement
Using power pelletsEmpowerment, mastery
Completing levelAchievement, relief

Step 5: Visual mapping

Diagram the full atom→mechanic→dynamic→aesthetic chain. This makes the design intent explicit and reveals where the chain breaks if the aesthetic is not being delivered.

[ATOM: Move] → [MECHANIC: Collect Pellets / Avoid Ghosts] → [DYNAMIC: Risk-Reward Strategy] → [AESTHETIC: Tension and Satisfaction]

Micro-mechanics: the feel of play

Macro-mechanics define the system (combat, traversal, crafting). Micro-mechanics define the feel — the split-second exchanges between input and feedback that make play tactile and satisfying.

“Micro-mechanics are the momentary building blocks of play — the kinesthetic feedback that communicates quality.”

Design principles for good micro-mechanics

PrincipleDescriptionExample
ResponsiveInput produces an immediate and expected reactionJump registers within <100 ms
PredictableConsistent results reinforce player trust and enable muscle memorySame input always produces same outcome
RewardingSensory feedback amplifies satisfaction and rhythm of playHit-pause on attack connects action to consequence

Specific techniques:

  • Input latency: keep the delay between button press and visible response under 100 ms
  • Anticipation and follow-through: animation principles that signal when actions start and end (see Disney’s twelve principles)
  • Hit-pause/screen shake: brief freeze on impact to accentuate weight; use sparingly
  • Audio layering: primary action sound + environment reverb + success tone
  • Consistency: the same input must always produce the same behaviour — essential for muscle memory development

Case study: Hollow Knight

Hollow Knight exemplifies refined micro-mechanics:

  • Jump arcs — precise and predictable; the player always knows how high they will go
  • Attack feel — weapon swing has subtle hit-pause (a few frames of freeze) followed by satisfying recoil
  • Audio feedback — crisp impact sounds match the animation rhythm
  • Controller vibration — reinforces weight and impact without overwhelming

Together these create a rhythmic, tactile flow that rewards precision and timing.

Representational layers: system vs surface

Every mechanic has two realities:

LayerDefinitionExample (jump)
System layerThe logical/coded function; abstract and mathematicalAdds +3 m/s vertical velocity for 0.4 s; gravity = −9.8 m/s²
Representation layerThe audiovisual, haptic, and spatial expression of that logicCharacter crouches, stretches upward, camera tilts, controller vibrates, jump sound plays

The same system logic can produce dramatically different player experiences through different representation.

Celeste vs Hollow Knight comparison:

AspectCelesteHollow Knight
System layerSimilar jump physics: gravity, variable input duration, dashSimilar gravity-based movement, dash, variable jump height
RepresentationFast animation, bright visuals, punchy click sound, no lagSlower wind-up, darker palette, heavier sound effects
Emotional toneUrgency, agility, optimismResilience, melancholy, endurance

The code is similar; the experience is completely different. Representation layer choices carry the emotional content of the game.

Design implication: When a mechanic feels wrong, the problem may be in the representation layer (wrong audio, wrong animation timing, wrong camera response) rather than the system layer (wrong numbers).

Combo systems as mastery representation

When multiple micro-mechanics chain together seamlessly, they create combo systems that represent and reward player mastery:

  • Atomic chain: each action (atom) triggers another through timing or logic
  • Mechanical interaction: inputs, timing, and feedback combine to create flow
  • Representation: visual, audio, and score-based feedback communicate success

The progressive skill development arc — Tutorial → Application → Mastery → Challenge Plateau — is the scaffolding through which players develop the fluency to execute combos.

Atomic loops and emergence

An atomic loop is the smallest cycle of interaction connecting player Action → System Response → Feedback → Player Understanding → Next Action. Loops create a continuous sense of control, learning, and mastery.

Emergence occurs when multiple atomic loops interact to produce complex, unpredictable behaviours from simple rules. Designers establish rules that interact dynamically; they do not script every emergent event.

Examples:

  • Minecraft — micro-loop: mining block → gaining resource → using tool durability. Macro-loop: crafting → constructing → exploring. Emergence: players build cities and redstone machines never planned by developers.
  • The Sims — needs loops (hunger, hygiene, social) combine into emergent life stories
  • Breath of the Wild — elemental rules (fire spreads, wind moves objects, electricity conducts) produce emergent problem-solving
  • Civilization — economic, military, and cultural loops intersect to produce unique world histories

Why emergence matters: Emergent play gives players ownership and creativity — they become co-authors of the experience. (see second-order-design)

Psychology of loops

Atomic loops tap into operant conditioning — behaviour reinforced by consistent feedback (Skinner, 1953). Predictability builds trust; small variations maintain engagement. Good loop design supports flow: the player is always learning through immediate feedback. (see flow)

Schema theory and cognitive economy

Players do not approach games without prior knowledge. They bring schemas — cognitive structures that organise knowledge and guide expectations.

ConceptDefinitionGame example
SchemaCognitive framework that guides prediction and interpretationRed barrels explode; hearts restore health
AffordanceVisual or auditory cue suggesting an object’s possible actionA lever implies pulling; a glowing door implies interaction
Cognitive economyBrain’s preference for minimal effort by reusing existing schemasGear icon = settings; floppy disk = save — reduce learning friction

Schema mismatch

When a game violates established schemas, confusion or frustration occurs. A door with a handle that cannot be opened breaks affordance trust. Unintentional schema violations produce user error and disengagement.

Intentional schema-breaking can be powerful — deliberately subverting player expectations for narrative or mechanical effect — but must be:

  1. Clearly intentional and communicable
  2. Used sparingly so the violation retains meaning
  3. Followed by new, learnable rules

Design application: Before release, ask:

  • What schemas do players bring from other games or from real life?
  • Does the visual language consistently apply? (Does red always mean danger?)
  • Are there misleading cues that could confuse new players?
  • Include schema testing in playtesting protocols.