Game Design Basics – Core Concepts, Process, and Documentation

1. What is Game Design?

Game design is the discipline of defining rules, systems, and content that together create an interactive experience for players. It differs from programming (implementation) and art (visuals) but works closely with both. A game designer must answer three core questions:

1. What can the player do? – the mechanics (e.g., jump, collect, trade).
2. How do those actions interact? – the dynamics (emergent behavior, strategy).
3. What does the player feel? – the aesthetics (fun, tension, narrative).

These three layers are formalised in the MDA framework (Mechanics → Dynamics → Aesthetics).

2. Core Concepts

2.1 Mechanics in Detail

Mechanics can be atomic (single action) or compound (combination of actions). They are usually expressed as if‑then rules:

$$\text{If }\text{player presses Jump}\to \text{character’s vertical velocity }=+V_{jump}$$

2.2 Dynamics as Systems

Dynamics are best understood through state diagrams that show how game states transition based on player input and internal timers.

stateDiagram-v2
    [*] --> "Idle"
    "Idle" --> "Running" : press ArrowRight
    "Running" --> "Jumping" : press Space
    "Jumping" --> "Falling" : peak reached
    "Falling" --> "Idle" : land on ground

2.3 Aesthetics Categories (MDA)

3. Game Design Documentation

A Game Design Document (GDD) is the central reference that records every design decision. A concise GDD for a small 2‑D platformer might include:

1. Game Overview – title, genre, target audience.
2. Core Loop – player actions → system response → reward.
3. Mechanics List – jump, double‑jump, enemy defeat, power‑up.
4. Level Design – sketches, tile maps, difficulty curve.
5. Art & Audio – sprite sheets, UI mock‑ups, sound cues.
6. Technical Specs – engine (Unity), platform (Android), performance targets.

3.1 Worked Example: “Mountain Hopper”

Trace of a Play Session (first 10 seconds):

1. 0 s – Game starts, speed = 5 m/s.
2. 1.2 s – Player taps → Hopper jumps over a low rock (Mechanic: jump).
3. 2.5 s – Hopper lands, particle effect shown (Feedback).
4. 3.0 s – Coin appears; player taps again → Hopper collects coin (Mechanic: collect). Score +10 (Aesthetic: reward).
5. 4.8 s – Speed increases to 5.2 m/s (Dynamic).
6. 6.0 s – Obstacle pattern changes to a gap; player double‑taps → double‑jump clears gap (Mechanic: double‑jump).
7. 7.5 s – Combo multiplier reaches 2×, score per coin now 20.
8. 9.0 s – Player slides under a low barrier (Swipe down).

This trace demonstrates how mechanics (jump, collect), dynamics (speed increase, combo), and aesthetics (sound, visual feedback) intertwine to produce the intended player experience.

4. Game Design Process

The design cycle is iterative; each iteration refines the game based on testing results.

4.1 Phases Explained

1. Concept Ideation – Brainstorming, market research, defining unique selling points.
2. Paper Prototype – Sketching level layouts, simulating mechanics with cards or dice.
3. Digital Prototype – Minimal viable product (MVP) built in a rapid‑development tool (e.g., Unity, Godot).
4. Playtesting – Observing real players, collecting quantitative (score, time) and qualitative (fun rating) data.
5. Feedback Analysis – Identifying pain points, balancing issues, unclear affordances.
6. Refinement – Adjusting mechanics, tweaking UI, re‑balancing difficulty.
7. Pre‑production – Finalising GDD, asset pipelines, technical architecture.
8. Full Production – Asset creation, programming, QA.
9. Launch & Post‑launch – Marketing, patches, DLC, community management.

5. Genre Classification & Comparison

Understanding genre conventions helps designers set player expectations and avoid “genre‑confusion”.

Advantages / Disadvantages

6. Applications of Game Design Principles

• Educational Games – Use mechanics that reinforce learning objectives (e.g., spaced repetition in language apps).
• Serious Games for Training – Simulate real‑world scenarios (flight simulators, medical procedures).
• Gamified Services – Loyalty points, achievement badges, and progress bars in e‑commerce or banking.

7. In the Real World

Real‑world Worked Example Tie‑In:
The “Mountain Hopper” speed‑increase mechanic mirrors Daraz’s flash‑sale timer: as time passes, the game’s speed rises, just as Daraz’s countdown makes the purchasing window shrink, increasing player (buyer) urgency. Designing the speed curve in the prototype helps students understand how to balance tension in both games and e‑commerce promotions.

8. Exam Tip

• Remember the MDA hierarchy: exam questions often ask you to map a given mechanic to its resulting dynamics and intended aesthetic. Write the three‑step chain explicitly.
• GDD structure is a frequent short‑answer topic; memorize the six core sections and be ready to give a one‑sentence purpose for each.
• Process diagrams earn marks – reproduce the iterative cycle in the correct order; use the keywords “prototype → playtest → refine”.
• Genre comparison tables are high‑yield; practice filling the table with at least three genres, focusing on mechanics vs aesthetics.
• Real‑world examples are rewarded. Cite a Nepali service (eSewa, Daraz, Ncell) and link it to a specific design concept (reward loop, dynamic difficulty, achievement badge).

In the real world

• Pathao (Nepal) uses dynamics (ride demand vs. driver supply) and feedback (real-time ETA updates) to balance player satisfaction and operational efficiency.
• eSewa applies mechanics (QR scanning, PIN entry) and aesthetics (satisfying transaction sounds) to simplify financial interactions.
• Nepali banks’ mobile apps leverage affordances (clear buttons for transfers) and goals (daily transaction limits) to guide user actions.