
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.
Formative check
Work through these before moving on. They are not graded — they tell you whether the standard below has landed yet.
Which source is best for the royalty an engine charges?
Write your named project in one sentence and your five comparison criteria as headings, with one piece of evidence under each.
How confident are you that you can extend and document a prototype and compare engines with sourced evidence?
Unit 3 checkpoint
Do this before you start the task. It covers the whole unit and tells you what to review first.
Under Godot’s MIT license, a student who sells a game made with it owes…
In 2024 Unity announced it was canceling the runtime fee it had announced in September 2023.
Which free tool builds branching interactive stories with no programming?
Which body type should a wall that never moves use?
With gravity 980 px/s² and jump_velocity −280 px/s, the peak height is 280² ÷ 1960 = px.
Doubling gravity while keeping jump_velocity the same doubles the jump height.
Every option in a menu works, but testers cannot find the volume slider. This is a problem of…
With coyote_time 0.1 s at 60 physics frames per second, a player has about frames of grace after running off a ledge.
A ship’s rotation is π (180°). Which way does transform.x point?
A ship moving at (0, 250) hits a floor with normal (0, −1). After bounce() and the 0.8 factor its velocity is (0, ).
Editing Rock.tscn and saving updates every rock instance in the arena, except properties overridden on one instance.
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
- Stage 1 — Plan. Design question, mechanic sketch, task list with estimates, chosen comparison engine and named project, and a source list.
- 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.
- 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.
- 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
| Criterion | What 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. |
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
- Extend the platformer or the ship with one mechanic of your own. State the design question first.
- Keep a build log: goal, steps, problems (exact error text), fix, evidence.
- Write a 700 to 900 word report comparing Godot with Unity or Unreal for a named project on five criteria.
- End with a reflection, then record a three-minute demonstration.
Criteria (four levels)
| Beginning | Developing | Proficient | Advanced | |
|---|---|---|---|---|
| Prototype and log | Runs, no log | Log lists steps only | Design question, tested twice (family testers or self-playtests on different days), log with causes and evidence | Log entries let a stranger repeat the fix |
| Sources | Unofficial only | Some official, undated | 4 or more, 2 official, all dated | Official terms quoted correctly, perspectives named |
| Comparison | One criterion | Criteria listed, no reasoning | Five criteria with evidence for the named project | Trade-offs weighed toward a recommendation |
| Reflection | Generic | Some detail | Says what was easy and hard in Godot | Engine 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
| Source | Official? | Date read | Perspective |
|---|---|---|---|
| godotengine.org/license | Yes | 2026-09-26 | Project’s own license text |
| A developer video | No | 2026-09-27 | One developer’s experience |
Self-review sheet (use it a day after drafting)
- Is the design question answerable by the mechanic?
- Is every license or price claim dated and from an official page?
- Are five criteria compared for the named project?
- Does the reflection say what was easy and hard, with evidence?
- One strength, one change, one question.
Sources: Godot documentation, Export (docs.godotengine.org); Unity 6.0 manual, Platform development (docs.unity3d.com)