Refine, playtest and package the game
See this course’s project requirements
A playable original Godot game with movement, token collection, score, pause, restart and a tested source-project handoff.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Complete importable Godot 4 source project.
- Movement and boundary calculations.
- Single-award collection and 4/4 completion tests.
- Pause/resume and restart from three states.
- Two intentional design choices with a playtest log.
Review and revise
Use these criteria to check your work and choose what to improve.
- Project opens with all required files.
- Collection, score and finish agree.
- Controls and restart behave consistently.
- Design changes and evidence are clearly explained.
Want more background?
The idea in everyday life
Build and refine Token Trail, an original four-token game with code-drawn shapes.
A small finished game pairs intentional design choices with evidence that its rules still work.
Refine, playtest and package the game — guided practice
Make two explainable design changes and hand off a reproducible project.
Install the free Godot 4 editor suitable for your computer. Extract project.godot, main.tscn and main.gd into one new folder, keeping the names unchanged. In Godot Project Manager choose Import, select project.godot, then Import & Edit. Open main.tscn; use Run Project (F6 runs the current scene, while F5 runs the configured project). The game is a 640×480 top-down collection activity with no external assets. Arrow keys move; Space pauses; R restarts. Finish each changed case, then restore the supplied baseline before the next lesson.
1. Choose two changes
Preserve a baseline copy. Change SPEED to 150.0 and change the first token position from(200,100) to(240,120). Keep four tokens and the original bounds.
You should see: The game has two named changes with a predicted effect.
A slower speed and moved target affect play without changing the rule contract.
2. Run the core checks
Play the changed project: move against all bounds, collect once, revisit, pause/resume, finish and restart.
You should see: No duplicate score; finish at 4/4; every restart restores four tokens.
Changes need regression checks on behavior that should remain reliable.
3. Explain one result
In README.md state why the changes suit your intended experience and record one observed consequence.
You should see: The design note connects a choice to a testable effect, such as longer travel time.
A design claim is stronger when it names evidence instead of taste alone.
4. Package the source
Close the editor. Zip project.godot, main.tscn, main.gd, README.md and playtest.md. Import a copied folder to check it opens. Leave generated .godot cache out.
You should see: A recipient with Godot 4 can import the source project with no missing art files.
A complete source handoff needs referenced files and operating instructions.
What to finish
A complete original source project, two documented design choices and a playtest log.
Watch for this
Changing the token count without updating the displayed total and expected tests.
How can I tell I understand it?
Complete the changed case, explain your result, and pass the three application checks.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkOptional course overview video · same video as Lesson 1
How to make a Video Game - Godot Beginner Tutorial
From Brackeys. Watch here or open it on YouTube .
Optional course overview. Follow the written steps below at your own pace.Tools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-12
Opened and inspected on 2026-09-12: A playable 2D project, game state and restart workflow.
Access: Free public web page; no paid enrollment required.
Reuse: Public reference; link only. LifeStarter prose, exercises and files are independently authored.
Source & access notes · checked 2026-09-12
Opened and inspected on 2026-09-12: Engine license attribution and separate asset obligations.
Access: Free public web page; no paid enrollment required.
Reuse: Link only. Godot uses the MIT license; retain applicable notices when distributing an engine build. All course game code and shapes are original.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.