
add a title screen, a pause menu and a version number to my game, and produce a desktop or web build that passes a release checklist.
Instruction
A prototype becomes a product when a stranger can start it, pause it, change settings and quit without help. Menus are unglamorous, but they are the first and last thing every player touches. (Adapted from the Godot documentation’s “Pausing games” and “Exporting projects” pages, CC BY 3.0.)
The title screen. Build it as a scene with a Control root, a VBoxContainer holding the title Label and Buttons for Start, Settings and Quit, and a small label showing the version:
extends Control
@onready var start_button: Button = $VBoxContainer/StartButton
@onready var quit_button: Button = $VBoxContainer/QuitButton
@onready var version_label: Label = $VersionLabel
func _ready() -> void:
start_button.pressed.connect(_on_start_pressed)
quit_button.pressed.connect(_on_quit_pressed)
quit_button.visible = not OS.has_feature("web")
version_label.text = "v" + str(ProjectSettings.get_setting("application/config/version"))
start_button.grab_focus()
func _on_start_pressed() -> void:
get_tree().change_scene_to_file("res://levels/level_1.tscn")
func _on_quit_pressed() -> void:
get_tree().quit()Three details are professional habits. grab_focus() puts keyboard and gamepad focus on Start, so the menu works without a mouse, which matters for accessibility and for console-style play. The Quit button is hidden on the web, where a game cannot close the browser tab. The version number comes from Project Settings (Application > Config > Version), so testers can report which build they played; set it to something like 0.9.0 and raise it with every release.
Pausing. Godot can pause the whole scene tree with get_tree().paused = true. Paused nodes stop processing, so the pause menu itself must be told to keep running: set its Process > Mode to Always in the Inspector. Add an input action pause (Escape and the gamepad Start button), then:
extends CanvasLayer
@onready var resume_button: Button = $Panel/VBoxContainer/ResumeButton
func _ready() -> void:
hide()
resume_button.pressed.connect(toggle_pause)
func _unhandled_input(event: InputEvent) -> void:
if event.is_action_pressed("pause"):
toggle_pause()
get_viewport().set_input_as_handled()
func toggle_pause() -> void:
get_tree().paused = not get_tree().paused
visible = get_tree().paused
if visible:
resume_button.grab_focus()A CanvasLayer draws on top of the game regardless of the camera, which is what a menu needs. Being able to pause at any time is itself an accessibility feature: players may need to stop for pain, fatigue, a phone call or a younger sibling.
Release builds. Export presets exist for Windows, macOS, Linux, Android and the web. A desktop export produces an executable and a .pck data file (or one file, if you choose to embed the data). Untick Export With Debug for a release. Before any release, run a release checklist: the game starts from the exported build, not just the editor; every menu path works; the game can be completed; settings save; there are no errors in the Output panel during a full play-through; credits list every asset and license; the version number is updated; and a dated backup of the project exists. Studios run checklists like this because the last-minute bug is always the one nobody tested.
Follow the rules of the platform. Platforms have requirements, from icon sizes to content rules. For your capstone, the platform is your portfolio folder: follow the capstone brief’s rules (a dated folder, the version number in the file name, credits included).
📖 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.
Build: Menus, pause and a release build
Question. Can a first-time player start, pause, adjust settings, resume and quit your game using only a keyboard or gamepad, and does the exported build pass the release checklist?
Materials
- Your capstone project in the Godot 4 desktop editor (4.3 or later) with export templates installed
- Kenney UI pack (CC0), optional
- A gamepad, if available
- The release checklist from this lesson
- Keep ergonomic habits and 20-20-20 breaks.
- Export to a dated folder outside the project, and back up the project before exporting.
- Run only your own builds; do not download or run executables from unknown sources.
Procedure
- Set Application > Config > Version in Project Settings. Build the title screen scene, attach the script, and set it as the main scene.
- Add the pause input action. Build the pause menu as a CanvasLayer scene with a Resume button and a Settings button (the settings screen you built in Unit 2, Lesson 2.4), set its Process Mode to Always, and instance it into each level.
- Test the whole flow with the keyboard only, then with a gamepad if you have one: start, pause, open settings, resume, finish or fail, return to title, quit.
- Export a release build (Windows, macOS, Linux or Web) with Export With Debug unticked into a dated folder.
- Run the exported build (not the editor) through the full release checklist, recording each item as pass or fail.
- Fix every failed item you can, re-export, and ask a family member to run through the flow on your build without help while you watch silently; if no one is available, run it yourself after a day away, following only what the screen shows.
Data
| Release checklist item | Pass / fail | Notes |
|---|---|---|
| Starts from exported build | ||
| Every menu path works (keyboard only) | ||
| Pause and resume at any moment | ||
| Game can be completed | ||
| Settings saved after relaunch | ||
| No errors in a full play-through | ||
| Credits complete; version updated; backup made |
Analysis
- Which checklist item failed first on the exported build, although it worked in the editor? Why might builds behave differently?
- Why must the pause menu’s process mode be set to Always? What happened before you set it?
- What did your tester (or your own fresh-eyes run) struggle with in the menus, and what did you change?
If you cannot do this build in person: Without Godot, design the full menu flow as a paper prototype (one card per screen, with arrows for each button), test it with a family member who ‘presses’ arrow keys by pointing, and complete the release checklist on the paper prototype, marking which items you could check on paper and which need a real build.
Formative check
Work through these before moving on. They are not graded — they tell you whether the standard below has landed yet.
If the game runs correctly from the editor, the exported build does not need testing.
Calling start_button.() in _ready() lets players use the title menu with only a keyboard or gamepad.
How confident are you that you can add menus, pausing and versioning and ship a build that passes a release checklist?
Practice
Work these on paper or in your notebook, then open Check your answer. Aim for all of Fluency and Application; try at least one Challenge.
Printable version: this unit’s practice workbook (PDF)
Fluency
Build speed and accuracy with the core skill.
- What does each line on the title screen do? (a) start_button.grab_focus(); (b) quit_button.visible = not OS.has_feature(“web”); (c) the version_label line.
Check your answer
Answer: (a) Puts keyboard and gamepad focus on Start so the menu works without a mouse. (b) Hides Quit on the web, where a game cannot close the browser tab. (c) Shows the version from Project Settings so testers can report which build they played.These are three professional habits. - Why is the pause menu a CanvasLayer, and what process mode must it have?
Check your answer
Answer: A CanvasLayer draws on top of the game regardless of the camera. Its process mode must be Always, or it pauses along with everything else.get_tree().paused = true stops processing for every node whose process mode does not allow running while paused. - List five items on the lesson’s release checklist.
Check your answer
Answer: Any five: starts from the exported build; every menu path works; the game can be completed; settings save; no errors in the Output panel during a full play-through; credits list every asset and license; version number updated; dated backup exists.The last-minute bug is always the one nobody tested.
Application
Use the skill in context. Show your reasoning.
- Code reading: in toggle_pause(), what is the value of get_tree().paused and of visible after the first press of Escape? After the second?
Check your answer
Answer: First press: paused true, visible true (and Resume gets focus). Second press: paused false, visible false.The function flips paused with not, then sets visible to match. - Find the bug: a student’s pause menu opens, but pressing Escape again does nothing and the game stays paused forever. The menu’s Process Mode is still Inherit. Explain and fix.
Check your answer
Answer: When the tree pauses, the menu inherits the pause and stops processing, so _unhandled_input never runs to unpause. Set the pause menu’s Process > Mode to Always.This is why the lesson says the pause menu must be told to keep running. - Your version is 0.9.0. You fix two bugs and release, then add a new options screen and release again. Give both version numbers (using the major.minor.patch scheme from Unit 1).
Check your answer
Answer: 0.9.1, then 0.10.0.A fix raises the patch number; a new feature raises the minor number and resets the patch to 0. - Explain why being able to pause at any time is an accessibility feature, with two examples from the lesson.
Check your answer
Answer: Players may need to stop for pain, fatigue, a phone call or a younger sibling; forcing them to keep playing creates a barrier.Pause at any time also appeared in the cognitive area of the Unit 2 audit. - The game works perfectly in the editor but the exported build shows a missing-texture error. Which checklist item caught it, and why can builds behave differently?
Check your answer
Answer: “Starts from the exported build” / “no errors in a full play-through” on the exported build. Exported builds can differ through missing files, export settings and platform behavior, so always test the build you release.Export with Export With Debug unticked for a release, into a dated folder outside the project.
Review
Keep earlier skills sharp.
- Review (Lesson 2.4): the settings screen must be reachable from the pause menu, not only the title. Why, and what one call makes it keyboard-usable?
Check your answer
Answer: Players may need to change settings, such as game speed or text size, in the middle of play. grab_focus() on the first control lets arrow keys move between options.Design the settings screen for access too.
A Filled Release Checklist, a Menu-Flow Test and a Version Scheme
SLS original technique sheet; the build and results are invented · SLS original
Why this reading. The lab asks you to run a release checklist on an exported build and to test menu flow with keyboard or gamepad. This sheet gives a filled checklist with failures, a version-number scheme and the exact menu-flow test sequence with expected focus, so you can see what a passing and failing record look like. SLS original.
Version numbers (a common scheme, SLS original)
Use three numbers, major.minor.patch: 0.9.0 is the first release candidate, 0.9.1 fixes bugs only, 0.10.0 adds features, 1.0.0 is the showcase build. Bug reports name the version, so raise it every time you export.
Menu-flow test with keyboard only
| Step | Input | Expected |
|---|---|---|
| Launch | none | Title screen; focus on Start |
| Start | Enter | Level 1 loads |
| Pause | Escape | Pause menu shows; focus on Resume; game stops |
| Open settings | Down, Enter | Settings shows; first control focused |
| Resume | Escape | Game continues from the same frame |
| Quit (desktop only) | Down x2, Enter | Game closes; no Quit button on the web build |
Filled release checklist (invented build 0.9.0, exported Windows folder 2026-11-20)
| Item | Pass or fail | Note |
|---|---|---|
| Starts from exported build | Pass | |
| Every menu path works (keyboard only) | Fail | Settings does not show focus; first control needs a grab_focus call |
| Pause and resume at any moment | Pass | |
| Game can be completed | Pass | |
| Settings saved after relaunch | Pass | |
| No errors in a full play-through | Fail | One missing file error for a sound in the exported build |
| Credits complete; version updated; backup made | Pass | Credits list Kenney CC0 assets |
Result: 5 of 7 pass. The audio failure only appeared in the export, because the sound file was excluded by the export filter; that is why you test the exported build, not the editor. Fix both, raise the version to 0.9.1, re-export and record the second run.