THE VR SCHOOL
  • Schools & Districts
    • License the academy
    • Free program for your students
    • Request a demo
  • Catalog
    • AI & Data
    • Cybersecurity & Web
    • Programming
    • Health Science
    • All Guilds
    • All courses
  • Families
  • Accreditation
  • Log In
  • Request a demo
  • Home
  • Courses

RLP Video Game Design A — Play, Prototypes, Engines and Worlds

Curriculum

  • 4 Sections
  • 20 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • Unit 1: Play, Players and the Designer’s Craft
    5
    • 1.1
      What Makes a Game a Game
      50 mins
    • 1.2
      Your First Godot Scene
      50 mins
    • 1.3
      Reading a Game: MDA and the Core Loop
      55 mins
    • 1.4
      Thinking Like a Designer: Roles, Paths and Habits
      55 mins
    • 1.5
      Three Games, One Question: Game Analysis Presentation
      50 mins
  • Unit 2: The Design Process: Concepts, Documents and Paper Prototypes
    5
    • 2.1
      From Idea to Ship: The Game Development Pipeline
      50 mins
    • 2.2
      Rules Become Code: A Coin-Grab Core Loop
      55 mins
    • 2.3
      Mechanics, Systems and Feedback Loops
      55 mins
    • 2.4
      Building the Paper Prototype and One-Page Design Document
      50 mins
    • 2.5
      Paper Prototype, Playtest and Design Document
      50 mins
  • Unit 3: Engines and Tools: Building in Godot 4
    5
    • 3.1
      Choosing an Engine: Godot, Unity, Unreal and the License Question
      50 mins
    • 3.2
      Build: A Platformer Character with Gravity and Collision
      50 mins
    • 3.3
      Game Feel: Controls, Input Devices and Usability
      55 mins
    • 3.4
      Build: The Rotate-and-Thrust Ship
      50 mins
    • 3.5
      Interactive Prototype and Engine Comparison Report
      50 mins
  • Unit 4: Worlds, Story, Art Style and Sound
    5
    • 4.1
      Story in Games: Structure, Character and World
      50 mins
    • 4.2
      Build: Animation, Parallax and Sound
      50 mins
    • 4.3
      Art Style, Mood Boards and the Rights to Every Asset
      55 mins
    • 4.4
      Storyboards, Sound Design and Original Assets
      50 mins
    • 4.5
      Narrative Concept, Mood Board and Semester Portfolio
      50 mins

Paper Prototype, Playtest and Design Document

Unit 2  ·  Culminating Portfolio Project  ·  Lesson 10 of 20

Paper Prototype, Playtest and Design Document

AME.D6.7RLP-GAMEA
Hands play a paper game while a designer compares notes and a revised board.
By the end of this lesson I can…

playtest my paper game in two sessions with family players (or a structured self-playtest), change rules based on evidence, and present the revised game with a design document, process flowchart and iteration log in a recording.

Instruction

This project is where you practice the habit that separates designers from people with ideas: changing your game because of what players actually did.

Who plays. Your playtesters are family members, or other adults or siblings you know, playing in person at home. Never recruit strangers online. Before you start, read a short consent script: “I’m testing a game I designed for my game design course. I’ll take notes on what you do and say, not on how well you play. You can stop at any time. Is that OK?” Take written notes; do not record video or audio of anyone under 18 without a parent’s OK. If no one is available for a session, run a structured self-playtest: set the game aside for at least a day, play both sides strictly from the written rules, and log every pause, guess and dead turn as if a stranger had made it.

Running the playtest. Explain the goal of the game in two sentences, hand over the rules and then stay quiet. Watch and write. Record what players did (“both players ignored the trade rule”), what they said (“wait, can I move twice?”) and when they looked bored or excited. Resist explaining: every time you want to explain, a rule is unclear, so write that down instead. After the game, ask three open questions: What was the most interesting decision you made? When were you bored or confused? If you could change one rule, which would it be?

From observations to changes. Sort your notes into three piles: clarity (players misunderstood a rule), balance (a strategy was too strong, a player was knocked out early, one side always won) and experience (the game felt different from what you intended). Choose at least two changes, and for each one write the evidence, the change and your prediction. Then test the revised game in a second session, with a different player if you can, and check whether your prediction came true. A change that made things worse is still a success if you can explain why; that is what the iteration log is for.

Change one thing at a time where you can. If you change four rules at once and the game improves, you will not know which change helped. Professional designers often test one change per session for exactly this reason.

The iteration log (400-600 words) covers: the original rule set in brief; what you observed in test 1; each change, with the evidence and prediction; what happened in test 2; and one challenge you expect in future iteration, such as a rule that still feels fragile. Write it as technical prose, not a diary: precise, past tense, evidence first.

The process flowchart shows the process you actually followed, not the ideal one, with the backward arrows labeled by the evidence that sent you back.

The presentation is recorded: five minutes to explain your design goal, your process and what changed and why, then a demonstration round, played with a family member or played by you while you narrate both sides. If a family member appears on camera, get a parent’s OK first; pointing the camera at the table so only hands and pieces show works well. Finish with a short written self-critique against the rubric.

📖 Read for this lesson

The reading opens over the lesson; close it to come back to exactly where you were. The checks below draw on it.

  • Playtest, Iterate, Present: Criteria, a Model Playtest and Iteration Log, and the Self-Check SheetSLS original; playtest log invented; simulation figures computed by SLS · about 3 min

    Four-level criteria, a model family playtest log with the three-pile sort, evidence-change-prediction entries with numbers you can check, a test 2 result and iteration log outline, and the self-check sheet.

Vocabulary in context

  • playtest — A session in which people play a game while the designer observes, to gather evidence for improving it.
  • iteration log — A record of each design change with its evidence, prediction and result.
  • clarity / balance / experience — Three kinds of playtest problem: misunderstood rules, unfair strategies or outcomes, and a gap between intended and actual feeling.

Formative check

Work through these before moving on. They are not graded — they tell you whether the standard below has landed yet.

+50 XP

In test 1, three of four players never used the trading rule. What is the best next step?

Find the cause (clarity or balance) before changing it, and change one thing so you can tell whether it worked.

Write the evidence, change and prediction for your first rule change, in three sentences.

0 words
Quick self-check

How confident are you that you can change a game’s rules based on playtest evidence and explain each change?

Not yetVery confident

Unit 2 checkpoint

Do this before you start the task. It covers the whole unit and tells you what to review first.

+50 XP

All content is in the game and the team is mainly fixing bugs. Which milestone?

Beta: content complete, focus on bugs. Alpha means every feature is in.
Myth or Fact?

A vertical slice is a rough prototype that tests one design question.

A vertical slice is built close to final quality to prove the full game can be made; a prototype is rough.
+50 XP

In a process flowchart, what shape stands for a decision such as “Is it fun?”

Diamonds are decisions; rectangles are steps; arrows show order.
+50 XP

Which node detects the player entering it without blocking them?

An Area2D detects bodies entering and emits body_entered.
Fill in the blank

The text “Final score: %d” % 9 displays Final score: . When the Timer runs out it emits the signal.

Myth or Fact?

Changing the sprite in Coin.tscn updates every Coin instance in Main.tscn.

A scene is a reusable template; editing the source updates every instance except properties overridden on one copy.
+50 XP

In a strategy game, the player with the most farms earns the most food, which buys more farms. This is…

Success brings more power: a positive loop, with a runaway-leader risk.
Fill in the blank

With two six-sided dice, a sum of 8 happens ways out of 36, and a sum of 2 happens way.

+50 XP

Which is a useful target audience for a design document?

Specific age, experience and situation let you make and test decisions.
Myth or Fact?

In a design document, it is better to use a different typeface for each section so readers can tell them apart.

Use one or two typefaces; hierarchy (size and weight) separates sections. Extra typefaces add noise.
+50 XP

A silent set-up tester asks, “Who goes first?” What does that tell you?

Every question in a silent set-up test marks a rule you had in your head but not on paper.

Submit: Paper prototype + design document + flowchart + iteration log (400-600 words) + presentation

Task: Playtest your paper game in two sessions, make at least two evidence-based rule changes, and present the revised game, its one-page design document, your process flowchart and your iteration log in a recording.

Submission workflow

  1. Stage 1 — Plan. Design document draft, prototype ready to play, and a playtest plan with your consent script and the three questions you will ask.
  2. Stage 2 — Self-reviewed draft. After test 1, set your observation notes aside for a day, then check each proposed change against the self-check sheet in the reading and strike any change that has no evidence behind it.
  3. Stage 3 — Revised final. Revised prototype and design document, results of test 2, the process flowchart and the 400-600 word iteration log.
  4. Stage 4 — Presentation. Five-minute recorded explanation and a recorded demonstration round (with a family player or narrated solo), plus a written self-critique against the rubric.

How it is scored

CriterionWhat proficient looks like
Design documents (AME.D6.7)One-page design document complete and specific; mechanics and their interaction clearly explained.
Paper prototype (AME.D2.8)Playable from the written rules alone; three or more interacting mechanics.
Iteration from evidence (AME.D6.2)At least two changes, each tied to observed evidence with a tested prediction.
Technical writing (WHST.9-10.2)Iteration log is precise, organized and evidence-first.
Process flowchart (AME.D6.1)Shows the actual process with labeled iteration loops.
Presentation and critique (SL.9-10.4)Clear explanation of goal, process and changes; demonstration round runs from the rules; honest self-critique against the rubric.

Missouri CTE — Multimedia (034356) objectives addressed: MM.EMT.4, MM.FND.4, MM.WRS.8, MM.COM.5, WHST.9-10.2, WHST.9-10.5, SL.9-10.4

Instructional focus: Iterative design from evidence

Reading

Playtest, Iterate, Present: Criteria, a Model Playtest and Iteration Log, and the Self-Check Sheet

SLS original; playtest log invented; simulation figures computed by SLS · SLS original

Why this reading. The project needs a rubric, a model playtest log and iteration log, and a self-check sheet. This reading gives them, built from the Dam Break game (Reading 2.4). The players, results and notes are invented for teaching; no real players are described.

Criteria (four levels)

BeginningDevelopingProficientAdvanced
EvidenceTests not recordedNotes without countsTwo tests with counts of what players did and saidCounts compared against arithmetic or simulation
ChangesChanges without reasonsReasons vagueAt least two changes, each with evidence, change and predictionOne change at a time; predictions checked
Document and flowchartMissing partsPartly clearOne page; flowchart shows the real processStrangers can play from the page alone
PresentationUnclearUnderstandableGoal, process and changes in 5 minutesDemonstration round runs smoothly from the rules alone

Playtest 1 log (invented; four family players at home)

PlayerWhat they didWhat they saidObserved
ALoaded 2 seeds, rolled 2 (moved 1)“Wait, does the water rise before or after I move?”Stopped play to ask
BLoaded 1 seed, delivered in round 4“Too easy.”Bored in rounds 3 and 4
CLoaded 3 seeds“That was unfair.”Dam broke in round 4; boat at 7
DLoaded 3 seeds—Dam broke in round 4; boat at 8

The three piles

Clarity: A asked about the order of water and movement. Balance: both 3-seed boats (C and D) failed; the 1-seed boat won easily. Experience: B was bored, so the game did not feel tense for the safe player.

Caution with counts. Two failures in two tries is weak evidence. If 3 seeds delivers 47.7 percent of the time (Reading 2.4), the chance that two separate 3-seed boats both fail is 0.523 × 0.523 = 0.274, about 27 percent. It could be bad luck. Run more tests before drastic changes.

Changes: evidence, change, prediction

  1. Clarity. Evidence: player A asked about order. Change: number steps (a) to (d) on the track sheet. Prediction: no player asks about the order in test 2.
  2. Balance. Evidence: two of two 3-seed boats failed. Change: dam breaks at 5 instead of 4. Prediction: 3-seed delivery rises from 47.7 percent to about 72 percent (simulation, 200,000 runs), and 1-seed delivery from 83.5 to about 95 percent, so players will take 2 or 3 seeds more often.

Test 2 result and iteration log excerpt (invented)

In test 2, no one asked about the order (prediction confirmed). Of four boats, two loaded 3 seeds and one delivered; two loaded 2 seeds and both delivered. The 1-seed choice disappeared, which is not what I wanted: the change made risk too cheap. Still an open challenge: the 1-seed choice is now rarely worth making. Next test: dam at 5, but a Surge card adds 3.

Write your log in this order: original rules in brief; test 1 observations; each change with evidence and prediction; test 2 result; one open challenge. Use past tense, evidence first, 400 to 600 words.

Self-check sheet (after a day away)

  1. What did the designer’s evidence show, in counts?
  2. Does each change follow from its evidence?
  3. Was each prediction checkable? Was it checked?
  4. Could a stranger play from the rules alone? Which step would they question?
  5. One thing that worked, one to change, one question.
Up NextComplete & Continue →

Leave a Reply Cancel reply

Building the Paper Prototype and One-Page Design Document
Prev
Choosing an Engine: Godot, Unity, Unreal and the License Question
Next

© 2026 The VR School | Career content by Wiley | Powered by Sejal Learning Systems.

Join free · Accreditation · Privacy Policy · Terms of Service

Modal title

Main Content