Chapter 2: The Blueprint of a Game
The Blueprint of a Game 📐
Section titled “The Blueprint of a Game 📐”When game designer Shigeru Miyamoto was a kid exploring the woods near his home in Japan, he stumbled upon a dark, hidden cave. That thrilling feeling of mysterious discovery stuck with him forever — and years later, he wrote a massive blueprint to recreate that exact feeling for players. The legendary Legend of Zelda series was born!
Imagine building a 100-story skyscraper without a blueprint. Walls wouldn’t line up, the roof might cave in, and the builders would be completely confused. Making a video game is no different. Before a single line of code is typed or a single character is drawn, game developers must plan everything out. In this chapter, you’ll learn how to take a game from a tiny concept to a fully planned project.
2.1 — The Art of the Story 📖
Section titled “2.1 — The Art of the Story 📖”Not every game needs a complex story — think of Tetris or Rocket League — but for many games, the story is the hook that keeps players glued to the screen.
Environmental Storytelling
Section titled “Environmental Storytelling”Environmental storytelling Environmental storytelling: Telling a story through the game world itself — objects, scenery, and details — instead of dialogue or cutscenes. means telling a story without using dialogue or cutscenes. The world itself gives players clues about what happened.
Think about Five Nights at Freddy’s:
- A brightly lit, clean party room tells one story.
- A dark room covered in cobwebs with a broken animatronic twitching in the corner tells a completely different story.
Nonlinear Stories
Section titled “Nonlinear Stories”Video games can tell stories in ways books and movies simply cannot. In a book, you read from page one to the end in a straight line. But in games, you can create a nonlinear story nonlinear story: A story structure where the player's choices change what happens next, leading to multiple possible paths and endings. . The player makes choices that actually change what happens next.
Games like Undertale and Detroit: Become Human offer completely different endings based on your decisions. To keep track of all these branching paths, writers use dialogue trees dialogue trees: Sprawling maps of conversations that show how every player choice connects to the next piece of dialogue or story event. — massive maps showing how every choice connects to the next.
2.2 — Game Mechanics and Making It “Fun” 🕹️
Section titled “2.2 — Game Mechanics and Making It “Fun” 🕹️”What exactly makes a game fun? While graphics and story are great, the answer usually comes down to mechanics.
Game mechanics Game mechanics: The actions the player can take and the way the game responds to them — jumping, shooting, crafting, managing health, etc. are the actions the player can take and the way the game responds. Jumping, shooting, sneaking, crafting items, and managing your health bar are all mechanics. A racing game needs smooth driving mechanics; a farming simulator needs planting and harvesting mechanics.
The Core Game Loop
Section titled “The Core Game Loop”When you combine your main mechanics, you create a Core Game Loop Core Game Loop: The primary sequence of actions a player repeats throughout the game. If this loop isn't fun, the whole game will feel boring. . Think of your favorite game — what’s the sequence of actions you repeat most often?
Minecraft Core Game Loop:Mine resources → Build shelter → Survive the night → Upgrade gear → Repeat!If your core game loop isn’t fun, the whole game will be boring.
UI and UX
Section titled “UI and UX”You also need to think about how the player interacts with your game:
| Term | Stands For | What It Means |
|---|---|---|
| UI UI: User Interface — the visual elements on screen like health bars, mini-maps, menus, and buttons. | User Interface | The stuff on screen: health bars, mini-maps, menus |
| UX UX: User Experience — how intuitive, smooth, and enjoyable it feels to use the game's interface and controls. | User Experience | How it feels to use the UI and controls |
Think about Mario Kart. The core mechanics are driving and throwing items. But what if the button to throw a Green Shell was hidden in a weird menu you had to pause to open? That’s terrible UI — and it leads to a frustrating UX!
Rewards and Economies
Section titled “Rewards and Economies”Earning gold coins, collecting rare armor, unlocking character skins, or getting a high score are great ways to keep players motivated. But beware of the “grind” — if you force players to collect 10,000 coins just to buy a basic hat, they’ll get bored and quit!
2.3 — Conflict, Objectives, and Rules ⚔️
Section titled “2.3 — Conflict, Objectives, and Rules ⚔️”Every good game has a goal and something trying to stop the player from reaching it.
Objectives
Section titled “Objectives”An objective objective: The goal the player is trying to achieve, such as 'rescue the prince,' 'defuse the bomb,' or 'win the race.' is what the player is trying to do — “rescue the prince,” “defuse the bomb,” or “win the race.”
Types of Conflict
Section titled “Types of Conflict”| Type | Description | Example |
|---|---|---|
| PvE PvE: Player versus Environment — the player fights computer-controlled enemies, avoids hazards, or solves puzzles. | Player vs. Environment | Fighting monsters, avoiding lava, solving puzzles |
| PvP PvP: Player versus Player — competing against real human opponents. | Player vs. Player | Fortnite, Super Smash Bros. |
| Player vs. Time | Beat the clock | Timed missions, shrinking zones |
Game Balance
Section titled “Game Balance”Rules are the secret to game balance game balance: Designing a game so that no single strategy, weapon, or character is so powerful that it makes everything else pointless. . How much damage does a sword do? How high can a character jump? If one weapon is so powerful (known as OP OP: Overpowered — when something in a game is so strong that it breaks the balance and everyone uses it. ) that everyone uses it and ignores the rest, the game is unbalanced.
Victory and Failure Conditions
Section titled “Victory and Failure Conditions”You must define how the game ends:
- Victory conditions: Crossing a finish line, collecting 100 hidden stars, surviving until sunrise.
- Failure conditions: What happens when you lose? Do you respawn instantly, drop your loot, or restart the entire level?
2.4 — Putting It on Paper 📝
Section titled “2.4 — Putting It on Paper 📝”Once you have your story, mechanics, and rules figured out, you need to write them down so your team can build the game.
Key Documents
Section titled “Key Documents”| Document | Purpose |
|---|---|
| Game Pitch | A short, exciting summary of your game — like a movie trailer on paper |
| Game Design Document (GDD) Game Design Document (GDD): The giant blueprint for a game. It contains the story, rules, victory conditions, controls, and a list of every asset needed to build the game. | The giant blueprint: story, rules, controls, victory conditions, and all required assets |
| Technical Design Document (TDD) Technical Design Document (TDD): A document for programmers explaining the math, code architecture, and software needed to make the game mechanics work. | For programmers: explains the math, code, and software architecture |
Assets Assets: All the individual pieces needed to build a game — 3D models, sound effects, music tracks, UI buttons, textures, etc. are all the individual pieces needed to build the game: 3D models, sound effects, music tracks, and UI buttons.
Development Phases
Section titled “Development Phases”Before building the entire game, developers break the process into phases:
- Prototype — A super basic, rough version (often just gray blocks) to test whether the core mechanics are fun.
- Vertical Slice — One polished slice of the game showing final graphics, sound, and gameplay for a single level.
- Alpha — The game is mostly built but still full of bugs.
- Beta — The game is fully playable and ready for player testing.
Key Concepts Checklist
Section titled “Key Concepts Checklist”- I understand why planning a game before building it is essential
- I can explain environmental storytelling and nonlinear stories
- I know what a Core Game Loop is and why it matters
- I understand the difference between UI and UX
- I can name three types of game conflict (PvE, PvP, Player vs. Time)
- I know what game balance means and why it’s important
- I can describe the key game documents (Pitch, GDD, TDD)
- I understand the development phases: Prototype → Vertical Slice → Alpha → Beta