Chapter 2: The Blueprint of a Game

🔊Read Aloud⏹️Stop

In Active Review, Subject to Change

This is the expanded edition of Game Development Fundamentals, in review alongside the original book. Content is subject to change.

The Blueprint of a Game 📐

Plan it before you build it

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 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 confused. Making a video game is no different. Before a single line of code is typed or a single character is drawn, developers plan everything out. In this chapter, you’ll learn how to take a game from a tiny concept to a fully planned project, and how to find out whether it’s actually fun before you spend months building it.

---

2.1 — The Art of the Story 📖

Not every game needs a complex story. Tetris and Rocket League have almost none. But for many games, the story is the hook that keeps players glued to the screen.

Environmental Storytelling

environmental storytellingenvironmental storytelling: Telling a story through the game world itself — objects, scenery, and details — instead of dialogue or cutscenes. means telling a story without 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. Nobody had to say a word.

If a player finds a rusted sword sticking out of a rock next to an old campfire, their brain immediately imagines the battle that happened there. You didn’t write a book about it. You placed two objects next to each other. This is one of the cheapest and most powerful tools a designer has.

Nonlinear Stories

Video games can tell stories in ways books and movies cannot. In a book, you read from page one to the end in a straight line. In games, you can create a nonlinear storynonlinear story: A story structure where the player's choices change what happens next, leading to multiple possible paths and endings., where the player’s choices change what happens next.

Games like Undertale and Detroit: Become Human offer completely different endings based on your decisions. To keep track of all the branching paths, writers use dialogue treesdialogue 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.

The Cost of Choice

Branching sounds amazing, and it is. But every branch is content that some players will never see. A story with three choices that each split three ways has 27 endings to write, test, and voice. Smart designers use a few tricks:

• Branch and merge. Paths split for a scene, then come back together.
• Flavor choices. The choice changes dialogue or a small reward, not the whole plot.
• Delayed consequences. A choice in chapter 1 changes one line in chapter 5. Cheap to make, memorable to players.

Stop and Think! 🤔

Think of a room in a game that told you a story without any text. What objects were in it, and what did your brain fill in?

Key Takeaway

Stories can live in the world itself. Branching stories are powerful but expensive, so designers branch carefully.

---

2.2 — Game Mechanics and Making It “Fun” 🕹️

What exactly makes a game fun? Graphics and story help, but the answer usually comes down to mechanics.

game mechanicsgame 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 a health bar are all mechanics. A racing game needs smooth driving mechanics; a farming simulator needs planting and harvesting mechanics.

The Core Game Loop

When you combine your main mechanics, you create a core game loopcore 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?

Game	Core Loop
Minecraft	Mine resources → build shelter → survive the night → upgrade gear → repeat
Stardew Valley	Plant → water → harvest → sell → buy better seeds → repeat
Fortnite	Land → loot → fight → shrink zone → last team standing
Angry Birds	Aim → launch → watch the collapse → three stars or retry

Notice each loop takes seconds or minutes, not hours. If your core loop isn’t fun on its own, no amount of story or graphics will save the game. Designers test the loop first, with placeholder art, before anything else.

Where Fun Comes From

“Fun” is vague, so designers break it into feelings a mechanic can create:

• Mastery. Getting better at something hard (a tricky jump, a combo).
• Discovery. Finding something new (a secret area, a crafting recipe).
• Expression. Making something yours (a base, a character, a strategy).
• Challenge and relief. Tension, then release (a boss fight, then a save point).
• Connection. Playing with or against others.

A good design question is not “is it fun?” but “which of these feelings does this mechanic create, and for whom?”

UI and UX

You also need to think about how the player interacts with your game:

Term	Stands For	What It Means
UIUI: 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
UXUX: 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. If the button to throw a shell were hidden in a menu you had to pause to open, that’s terrible UI, and it leads to a frustrating UX. A rule of thumb: the most common action should be the easiest button.

Rewards and Economies

Earning coins, collecting rare armor, unlocking skins, or getting a high score keeps players motivated. But beware the grind. If you force players to collect 10,000 coins for a basic hat, they’ll get bored and quit. Rewards should arrive on a rhythm: small ones often, medium ones regularly, big ones rarely.

Try It

Write the core loop of a game you play as a chain of five or fewer arrows. Then write which feeling from the list above each step creates. If a step creates none, that’s where players get bored.

Key Takeaway

Mechanics are what the player does. The core loop is the mechanics they repeat. Test the loop with ugly placeholder art before you build anything else.

---

2.3 — Conflict, Objectives, and Rules ⚔️

Every good game has a goal and something trying to stop the player from reaching it.

Objectives

An objectiveobjective: 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,” “win the race.” Good games layer objectives: a long-term goal (beat the game), medium goals (clear this level), and short goals (get across this pit). The short ones keep players moving toward the long one.

Types of Conflict

Type	Description	Example
PvEPvE: Player versus Environment — the player fights computer-controlled enemies, avoids hazards, or solves puzzles.	Player vs. Environment	Fighting monsters, avoiding lava, solving puzzles
PvPPvP: 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
Player vs. Self	Beat your own record	Speedruns, high scores, daily streaks

Game Balance

Rules are the secret to game balancegame 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 strong that everyone uses it and ignores the rest, players call it OPOP: Overpowered — when something in a game is so strong that it breaks the balance and everyone uses it., and the game is unbalanced.

Balancing is done with numbers and testing. Designers keep spreadsheets of every weapon’s damage, speed, and cost, then watch what real players choose. If 90% of players pick the same sword, the sword gets weaker, or the others get stronger. This is called a nerf and a buff, and it never really ends; online games rebalance for years.

Difficulty Curves

A difficulty curvedifficulty curve: How a game's challenge changes over time. A good curve rises gradually, with occasional rests, so players stay in the zone between bored and frustrated. describes how hard the game gets as you play. Too flat, and players get bored. Too steep, and they quit. The sweet spot is the zone where the challenge is just slightly above the player’s skill, and the curve rises as the player improves. Many games add difficulty settings or “adaptive” difficulty that quietly adjusts to the player.

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? Respawn instantly, drop your loot, or restart the whole level?

Losing should be a learning experience that makes the player want to try again, not a punishment that makes them rage-quit. The best failure is fast to recover from and teaches something. Celeste restarts you instantly at the start of the screen you died on, which is why players happily die hundreds of times.

Stop and Think! 🤔

Name something you think is OP in a game you play. If you were the designer, would you nerf it, buff everything else, or leave it? What would change for players who love it?

Key Takeaway

Objectives give direction, conflict gives challenge, rules and balance keep it fair, and a good difficulty curve keeps players between bored and frustrated.

---

2.4 — Putting It on Paper and Testing It 📝

Once you have your story, mechanics, and rules figured out, you need to write them down so your team can build the game, and then find out whether your plan actually works.

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: the math, code, and software architecture

assetsassets: 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: models, sprites, sound effects, music tracks, and UI buttons. A GDD lists every one so nothing is forgotten.

The One-Page Version

Big studios write GDDs that run hundreds of pages. You don’t need that. A one-page design doc answers six questions:

1. Hook: what’s the one sentence that makes someone want to play?
2. Core loop: what does the player repeat?
3. Goal and failure: how do you win, and what happens when you lose?
4. Mechanics: the three to five actions the player can take.
5. Look and feel: art style, mood, one reference image.
6. Scope: how many levels, enemies, and assets, honestly.

Development Phases

Before building the entire game, developers break the process into phases:

1. Prototype: a rough version, often just gray blocks, to test whether the core mechanics are fun.
2. Vertical slice: one polished piece of the game showing final graphics, sound, and gameplay for a single level.
3. Alpha: the game is mostly built but still full of bugs.
4. Beta: the game is fully playable and ready for player testing.
5. Release and then post-launch: patches, balance updates, new content.

Playtesting

playtestingplaytesting: Watching real players play your game, without helping them, to find out what is confusing, boring, or broken. is the most important skill in this chapter, and the one beginners skip. Hand your prototype to someone, say nothing, and watch:

• Where do they get stuck? That’s a design problem, not a player problem.
• What do they ignore? Maybe it isn’t needed.
• When do they smile, lean in, or say “one more try”? That’s the fun. Build more of it.

Rules for good playtesting: don’t explain, don’t defend, write down everything, and test with people who are not your friends at least once. Then change one thing and test again.

Watch Out!

Scope creep is the number one killer of student games. Every “it would be cool if…” adds days of work. Write your scope on the one-page doc, and when a new idea appears, put it on a “version 2” list instead of adding it now.

Key Takeaway

Write a one-page design doc, build the ugliest possible prototype, watch new players play it, and fix what confused them. Then, and only then, make it pretty.

---

Chapter 2 Activity: The One-Page Game Design Document 📋

Your Mission: Plan a small game you could actually build in GDevelop this semester, and test the plan before writing any code.

Part 1: The Pitch

Write a one-sentence hook and a three-sentence pitch for an original 2D game. Say who the player is, what they do, and what makes it different.

Part 2: The Blueprint

Fill in the six questions of the one-page design doc from section 2.4: hook, core loop, goal and failure, three to five mechanics, look and feel, and an honest scope (number of levels, enemies, and assets).

Part 3: Balance the Rules

List every number in your game: player speed, jump height, enemy damage, coins per level. Pick two and explain what happens if each is doubled. Which one is most likely to end up OP?

Part 4: Paper Playtest

Sketch your first level on paper and have a partner “play” it by moving a coin while you narrate the rules without helping. Write down three things that confused them and one thing that made them smile. Change one rule and try again.

---

Key Concepts Checklist

• I can explain environmental storytelling and nonlinear stories
• I know why branching stories are expensive and how designers manage that
• I can write a core game loop and name the feeling each step creates
• I understand the difference between UI and UX
• I can name four types of game conflict
• I know what game balance, nerfs, buffs, and a difficulty curve are
• I can describe the key game documents and write a one-page design doc
• I know the development phases and the rules of good playtesting

---

📖 Love what you're reading?

Get Game Development Fundamentals (Expanded Edition) with activities, worksheets, and bonus content — perfect for classrooms and homeschool families.

Get the Full Textbook

☐Mark Chapter Complete

🍎For Educators

Teaching this chapter? Get the full grading rubrics, slide decks, and lab asset bundles in the Educator Portal.

Visit the Educator Portal →