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

Interactive Prototype and Engine Comparison Report

Unit 3  ·  Culminating Portfolio Project  ·  Lesson 15 of 20

Interactive Prototype and Engine Comparison Report

MM.EMT.4RLP-GAMEA
Hands test a double-jump platformer beside a two-column abstract engine comparison sheet.
By the end of this lesson I can…

extend one of my Godot builds with a mechanic of my own, document the process, and write a sourced report comparing Godot with a professional engine.

Instruction

This project joins the two halves of the unit: making something with a tool, and judging tools. The prototype shows what you can build; the report shows that you can evaluate the technology an industry depends on.

The prototype. Start from your platformer (Lesson 3.2) or ship game (Lesson 3.4) and add one mechanic of your own design. Keep it small and testable: a double jump, a dash with a cooldown, a moving platform, a fuel gauge that limits thrust, a crystal that must be pushed rather than touched. Before building, write one sentence stating the design question the mechanic answers (“Does limited fuel make players plan their routes?”). After building, have it played by two testers, family members at home using the consent script from Lesson 3.3, or run two self-playtests on different days if no one is available, and note whether the answer is yes.

The build log is technical documentation, not a diary. For each session record: goal, steps taken, problems met (with the exact error message where there was one), the fix and the evidence the fix worked. A good entry: “Dash triggered twice when held. Cause: used is_action_pressed instead of is_action_just_pressed. Fixed; tested 10 presses, one dash each.” Future you, and any studio teammates you work with later, will rely on entries like that.

The comparison report. Choose one professional engine (Unity or Unreal Engine are the usual choices) and compare it with Godot for a named project: “a 2D mobile puzzle game by one student developer” leads to a different answer from “a 3D open-world game by a funded studio”. Compare on five criteria: license and cost (read the actual terms and give the date you read them), platforms supported and any extra requirements, language and learning curve, community and documentation, and fit for the named project. A comparison table is welcome but does not replace prose analysis.

Sources. Use the engines’ official documentation and license pages as primary sources. Developer interviews, postmortems and community discussions can show how the engine feels in use, but identify their perspective: a company blog is promotional; a forum post is one person’s experience. Cite at least four sources, at least two of them official, with dates.

The reflection. End with a paragraph on your own build: what did Godot make easy, what did it make hard, and would your mechanic have been easier or harder in the engine you researched? Base the second part on evidence from its documentation, not guesses.

The demonstration. Three minutes: state the design question, show the mechanic working and report what your testers did, recorded as a screen capture with your narration (free tools such as OBS Studio need no account). End by answering the three questions a reviewer would most likely ask.

📖 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.

  • Interactive Prototype and Engine Comparison Report: Brief, Criteria, an Exemplar Excerpt and the Self-Review SheetSLS original; facts cited from vendor pages read 2026-09-26 (see Reading 3.1); Godot export platforms and scripting languages from docs.godotengine.org; Unity 6.0 platform page from docs.unity3d.com · about 2 min

    The full brief, four-level criteria, an exemplar report excerpt with dated license facts and platform lists for a solo developer’s named project, a source-log format and a self-review sheet.

Vocabulary in context

  • build log — Technical documentation of each work session: goal, steps, problems, fixes and evidence.
  • evaluation criteria — The named standards against which options are compared, such as cost, platforms and learning curve.
  • postmortem — A developer’s published review of what went right and wrong on a finished project.

Formative check

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

+50 XP

Which source is best for the royalty an engine charges?

License terms change; the official current page, dated, is the primary source.

Write your named project in one sentence and your five comparison criteria as headings, with one piece of evidence under each.

0 words
Quick self-check

How confident are you that you can extend and document a prototype and compare engines with sourced evidence?

Not yetVery confident

Unit 3 checkpoint

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

+50 XP

Under Godot’s MIT license, a student who sells a game made with it owes…

MIT allows commercial use without fees, with the copyright and license notice kept.
Myth or Fact?

In 2024 Unity announced it was canceling the runtime fee it had announced in September 2023.

Unity revised the policy within weeks and canceled the fee in 2024.
+50 XP

Which free tool builds branching interactive stories with no programming?

Twine is made for branching stories.
+50 XP

Which body type should a wall that never moves use?

StaticBody2D never moves.
Fill in the blank

With gravity 980 px/s² and jump_velocity −280 px/s, the peak height is 280² ÷ 1960 = px.

Myth or Fact?

Doubling gravity while keeping jump_velocity the same doubles the jump height.

Height is v² ÷ (2g), so doubling g halves the height.
+50 XP

Every option in a menu works, but testers cannot find the volume slider. This is a problem of…

Usability is found by watching people use working features.
Fill in the blank

With coyote_time 0.1 s at 60 physics frames per second, a player has about frames of grace after running off a ledge.

+50 XP

A ship’s rotation is π (180°). Which way does transform.x point?

(cos 180°, sin 180°) = (−1, 0), left.
Fill in the blank

A ship moving at (0, 250) hits a floor with normal (0, −1). After bounce() and the 0.8 factor its velocity is (0, ).

Myth or Fact?

Editing Rock.tscn and saving updates every rock instance in the arena, except properties overridden on one instance.

A saved scene is a template; overrides on a single instance are kept.

Submit: Extended prototype + build log + engine comparison report (700-900 words) + demonstration

Task: Extend your platformer or ship game with one original mechanic that answers a stated design question, document the build, and write a sourced report comparing Godot with one professional engine for a named project.

Submission workflow

  1. Stage 1 — Plan. Design question, mechanic sketch, task list with estimates, chosen comparison engine and named project, and a source list.
  2. Stage 2 — Self-reviewed draft. Leave the draft for a day, then check it against the review sheet in the reading: every claim has a source, every criterion has evidence. Optionally, a family member plays the prototype and tells you one thing that confused them.
  3. Stage 3 — Revised final. Working prototype (zipped project), complete build log, and a 700-900 word report with at least four dated sources and the reflection.
  4. Stage 4 — Demonstration. Three-minute recorded demo showing the mechanic and the tester results, ending with your answers to three likely reviewer questions.

How it is scored

CriterionWhat proficient looks like
Technical build (MM.EMT.4)Prototype runs; the new mechanic works reliably and answers its design question.
Programming concepts (AME.D3)Correct use of variables, conditionals, input and physics; code explained accurately.
Build documentation (WHST.9-10.2)Log records goals, problems, fixes and evidence precisely.
Engine comparison (AME.D6.6)Five criteria compared for a named project with accurate, dated evidence.
Sources (WHST.9-10.8, MM.COM.5)At least four sources, two official; perspective of each identified.
Demonstration (SL.9-10.4)Clear design question, working demo, tester results reported and likely questions answered.

Missouri CTE — Multimedia (034356) objectives addressed: MM.EMT.4, MM.ANI.6, MM.FND.7, MM.COM.5, WHST.9-10.2, WHST.9-10.8, SL.9-10.4

Instructional focus: Technical production and comparative research writing

Reading

Interactive Prototype and Engine Comparison Report: Brief, Criteria, an Exemplar Excerpt and the Self-Review Sheet

SLS original; facts cited from vendor pages read 2026-09-26 (see Reading 3.1); Godot export platforms and scripting languages from docs.godotengine.org; Unity 6.0 platform page from docs.unity3d.com · SLS original

Why this reading. The project needs the full brief, criteria, an exemplar of the comparison report’s argument, a source log format and the self-review sheet. The exemplar uses the dated facts in Reading 3.1 for a named project; the project and the report are invented (SLS original). Your report needs your own engine choice, your own dates and at least four sources, two of them official.

The task

  1. Extend the platformer or the ship with one mechanic of your own. State the design question first.
  2. Keep a build log: goal, steps, problems (exact error text), fix, evidence.
  3. Write a 700 to 900 word report comparing Godot with Unity or Unreal for a named project on five criteria.
  4. End with a reflection, then record a three-minute demonstration.

Criteria (four levels)

BeginningDevelopingProficientAdvanced
Prototype and logRuns, no logLog lists steps onlyDesign question, tested twice (family testers or self-playtests on different days), log with causes and evidenceLog entries let a stranger repeat the fix
SourcesUnofficial onlySome official, undated4 or more, 2 official, all datedOfficial terms quoted correctly, perspectives named
ComparisonOne criterionCriteria listed, no reasoningFive criteria with evidence for the named projectTrade-offs weighed toward a recommendation
ReflectionGenericSome detailSays what was easy and hard in GodotEngine claims backed by documentation

Exemplar (invented): named project, a 2D mobile puzzle game by one student developer

License and cost. As of Sept. 26, 2026, Godot is MIT-licensed with no fees or royalties (godotengine.org/license). Unity’s Personal plan is free for customers with up to $200,000 in revenue and funding (unity.com/products/pricing-updates, read Sept. 26, 2026), so for a solo student developer the cost is also $0 today. The difference is risk: the terms are the vendor’s to change, as Unity’s 2023 runtime fee, canceled Sept. 12, 2024, showed.

Platforms. Godot’s export guides list Windows, Linux, macOS, Android, iOS, visionOS, Web and dedicated servers; Unity 6.0’s platform page lists Android, iOS, Web, Windows and others, and marks console platforms as needing developer agreements (both read Sept. 26, 2026). Both reach phones, so this criterion does not separate them for this project.

Language. Godot supports GDScript and C#; Unity’s manual refers to C#. My prototype used GDScript.

Fit. A solo developer building a small puzzle game benefits from Godot’s small download and fixed terms; a team that needs a large asset ecosystem might choose Unity. (Now add community and documentation, with evidence.)

Source log format

SourceOfficial?Date readPerspective
godotengine.org/licenseYes2026-09-26Project’s own license text
A developer videoNo2026-09-27One developer’s experience

Self-review sheet (use it a day after drafting)

  1. Is the design question answerable by the mechanic?
  2. Is every license or price claim dated and from an official page?
  3. Are five criteria compared for the named project?
  4. Does the reflection say what was easy and hard, with evidence?
  5. One strength, one change, one question.

Sources: Godot documentation, Export (docs.godotengine.org); Unity 6.0 manual, Platform development (docs.unity3d.com)

Up NextComplete & Continue →

Leave a Reply Cancel reply

Build: The Rotate-and-Thrust Ship
Prev
Story in Games: Structure, Character and World
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