Skip to content
Tutorials Center
My learning

Topics

Lesson 36 of 36 ยท Projects and Practice

Godot Practice Challenges

Test your Godot 4 skills with graded challenges for 2D, 3D, UI, audio and optimization, runnable Python logic exercises, a debugging checklist, project ideas and a mixed review quiz.

Reading about game development is not the same as building games. This lesson gives you graded challenges, a debugging checklist, project ideas and a mixed quiz. Work through them in the Godot editor: the more you build, the faster the node and signal patterns become automatic.

Godot cannot run on this site, so the challenges themselves are read-only descriptions. The Python blocks are stand-ins for game logic you can practice here (a stand-in is just the maths and rules, not the engine). Each challenge links the lesson that teaches the idea.

How to practice

  1. Pick a challenge slightly above your level.
  2. Write down what the result should look like before you start.
  3. Build the smallest version first; get something moving in 20 minutes.
  4. When stuck, use the Remote tab in the scene tree, print(), and the debugger before searching for answers.
  5. Commit to version control after each working step.

Level 1: single features

  • Moving square. One CharacterBody2D that moves with WASD at constant speed (no diagonal speed-up). See player movement.
  • Jump feel. Add variable jump height (release the button early to cut the jump), coyote time and a jump buffer.
  • Coin counter. An Area2D coin that increases a Label through a signal.
  • Tilemap room. Build a room with TileMapLayer, collisions on walls and terrain autotiling (tilemaps).
  • Pop-in menu. A main menu with three buttons that pop in with a tween one after the other (tweens).
Python Practice (Python stand-in): variable jump height by cutting upward speed on release

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Level 2: small systems

  • Health system. A reusable Health component (a Node with max_health, health_changed and died signals) attached to the player and to enemies.
  • Camera juice. Smooth follow, limits, look-ahead and trauma-based shake (camera).
  • Layers. Create a hitbox/hurtbox system where player attacks hurt enemies but not the player (collision layers).
  • Settings screen. Music and SFX sliders that control bus volume in dB (audio), saved to user://settings.cfg.
  • Responsive HUD. A health bar and score that stay correctly placed at 16:9, 21:9 and portrait (themes and responsive UI).
Python Practice (Python stand-in): a reusable Health component

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Level 3: whole games

  • Flappy-style game (one input, scrolling obstacles, score, restart).
  • Breakout (paddle, ball with reflection, bricks from a grid, levels).
  • Top-down shooter (project) with a boss and upgrades.
  • Platformer (project) with moving platforms, a key and door, and a level select.
  • 3D collectathon: a third-person character collecting items in a lit scene with a day-night cycle (lighting).
  • Tower defense: enemies follow a path (Path2D and PathFollow2D), towers choose targets in range.
Python Practice (Python stand-in): ball reflection for a Breakout game

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Level 4: polish and production

  • Add pause, game over and a title screen with scene transitions (fade with a ColorRect and a tween).
  • Make the game playable with gamepad and keyboard using the Input Map only (no raw key checks).
  • Find the slowest frame with the Profiler, fix it, and write down the numbers (profiling).
  • Export a Windows build and a web build and test them on a clean machine (exporting).
  • Add a save system with versioned data (save and load).

Debugging checklist

When something does not work:

  1. Read the red text. Errors in the Debugger > Errors tab show the file and line.
  2. Is the node what you think it is? Use the Remote scene tree while running and inspect properties live.
  3. Signals not firing? Check the connection, that the emitter exists, and the collision layer and mask (the most common cause for body_entered).
  4. Nothing visible? Check visible, z_index, the camera, modulate alpha, and whether the node is under a CanvasLayer.
  5. Moving wrong? Print velocity and delta; confirm that code is in _physics_process and that y is down in 2D.
  6. Works in the editor, not in the export? Resource filters, res:// writes, case-sensitive file names on Linux, missing user:// data.
  7. Slow? Profile; do not guess.
Python Practice (Python stand-in): a bug hunt, why does the score never change?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Mixed review quiz

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. A coin's Area2D never emits body_entered when the player touches it. What do you check first?

    Layers and masks plus the signal connection are the usual reasons that overlap signals stay silent.
  2. 2. Which is the best first step when a game runs at 25 FPS on a laptop?

    Measure first; the Profiler and Visual Profiler point at the cost.
  3. 3. Which node type carries a HUD that must not scroll with the camera?

    CanvasLayer draws independently of the camera.
  4. 4. You want the same enemy to appear 200 times cheaply in 3D. Which node?

    A MultiMesh draws many instances of one mesh in one call.
  5. 5. Where do saved games belong in an exported game?

    user:// is the writable per-project location; res:// is read-only.

Summary

  • Practice in small steps: single features, small systems, whole games, then polish and shipping.
  • Keep a debugging routine: read errors, inspect the Remote tree, check signals, layers and masks, then profile.
  • Rebuild classic games (Flappy, Breakout, shooter, platformer, tower defense) to learn the patterns that every genre reuses.
  • Keep a project journal of what you built, what broke and how you fixed it.

Next: Return to the Godot Engine track page to review the whole course.