The Life Starter
0 of 6 complete0%
Course Library · Lesson 4 of 6
Create · Guided lesson

Connect score and a finish state

About 36 minutes · 6 reading + 30 practice and checks
Time includes reading, practice, and questions. Extra videos or further study are optional.
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.
Open the full course project
Want more background?
Before you begin

The idea in everyday life

Build and refine Token Trail, an original four-token game with code-drawn shapes.

The idea

An event announces a change; a receiving function updates the part that cares about it.

Follow along

Connect score and a finish state — guided practice

Trace a signal from a collection event to the display and completion state.

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. 1. Find the signal

    Locate signal token_collected(total: int) and its connection in _ready.

    You should see: token_collected is connected to _on_token_collected.

    The declaration, connection and receiver form one event route.

  2. 2. Trace the payload

    Follow score +=1, token_collected.emit(score), and the receiver parameter total.

    You should see: After the first token, the emitted total is 1 and the HUD shows 1/4.

    The payload carries the new total, rather than asking the display to count shapes.

  3. 3. Finish the game

    Restart and collect all four squares.

    You should see: Score is 4/4, no squares remain, and Complete appears.

    The finish state follows tokens.is_empty(), keeping completion tied to the remaining work.

  4. 4. Check after completion

    Hold an arrow key after Complete. Record the stopped movement, then press R.

    You should see: Movement is stopped when won is true; restart returns Score:0/4 and four squares.

    A completion state needs a defined response to continued input.

Now change one thing

A different game has six tokens. Its signal emits the total after the fifth distinct collection. Enter the payload value.

Your work

What to finish

An event-route note and a completed-game test.

Common mistake

Watch for this

Connecting the same event repeatedly on restart can duplicate callbacks; this project connects once in _ready.

How can I tell I understand it?

Complete the changed case, explain your result, and pass the three application checks.

Try 3 questions

Quick knowledge check

Answer all 3 questions. Get at least 2 right and the lesson completes automatically.

Not yet passed

You’ll get an explanation for each answer. Signed in? Your results save to your account.

1A signal emits the new total 3. What does its receiving function’s total parameter represent?
2Where is the signal connection made in this project?
3All token entries are gone but the game still moves indefinitely. Which state check should you inspect?
0 of 3 answeredApply the lesson to a short question, then review the explanation.
4
Finish this lesson

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 check
Optional course overview video · same video as Lesson 1
BrackeysHow to make a Video Game - Godot Beginner TutorialYouTube
Optional course overview

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.

Godot: Your first 2D game
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.

Godot: Using signals
Source & access notes · checked 2026-09-12

Opened and inspected on 2026-09-12: Connecting a signal to a receiving function.

Access: Free public web page; no paid enrollment required.

Reuse: Public reference; link only. LifeStarter prose, exercises and files are independently authored.

Report a problem with this lesson

Tell us what went wrong. Please leave out personal information and private project contents.

No sign-in needed.