THE VR SCHOOL
  • Schools & Districts
    • License the academy
    • Free program for your students
    • Request a demo
  • Catalog
    • AI & Data
    • Cybersecurity & Web
    • Programming
    • Health Science
    • All Guilds
    • All courses
  • Families
  • Accreditation
  • Log In
  • Request a demo
  • Home
  • Courses

RLP Video Game Design A — Play, Prototypes, Engines and Worlds

Curriculum

  • 4 Sections
  • 20 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • Unit 1: Play, Players and the Designer’s Craft
    5
    • 1.1
      What Makes a Game a Game
      50 mins
    • 1.2
      Your First Godot Scene
      50 mins
    • 1.3
      Reading a Game: MDA and the Core Loop
      55 mins
    • 1.4
      Thinking Like a Designer: Roles, Paths and Habits
      55 mins
    • 1.5
      Three Games, One Question: Game Analysis Presentation
      50 mins
  • Unit 2: The Design Process: Concepts, Documents and Paper Prototypes
    5
    • 2.1
      From Idea to Ship: The Game Development Pipeline
      50 mins
    • 2.2
      Rules Become Code: A Coin-Grab Core Loop
      55 mins
    • 2.3
      Mechanics, Systems and Feedback Loops
      55 mins
    • 2.4
      Building the Paper Prototype and One-Page Design Document
      50 mins
    • 2.5
      Paper Prototype, Playtest and Design Document
      50 mins
  • Unit 3: Engines and Tools: Building in Godot 4
    5
    • 3.1
      Choosing an Engine: Godot, Unity, Unreal and the License Question
      50 mins
    • 3.2
      Build: A Platformer Character with Gravity and Collision
      50 mins
    • 3.3
      Game Feel: Controls, Input Devices and Usability
      55 mins
    • 3.4
      Build: The Rotate-and-Thrust Ship
      50 mins
    • 3.5
      Interactive Prototype and Engine Comparison Report
      50 mins
  • Unit 4: Worlds, Story, Art Style and Sound
    5
    • 4.1
      Story in Games: Structure, Character and World
      50 mins
    • 4.2
      Build: Animation, Parallax and Sound
      50 mins
    • 4.3
      Art Style, Mood Boards and the Rights to Every Asset
      55 mins
    • 4.4
      Storyboards, Sound Design and Original Assets
      50 mins
    • 4.5
      Narrative Concept, Mood Board and Semester Portfolio
      50 mins

Your First Godot Scene

Unit 1  ·  Technical Skills Lab  ·  Lesson 2 of 20

Your First Godot Scene

AME.D3.1RLP-GAMEA
Student assembles a connected node tree while a game sprite moves across a blank editor screen.
By the end of this lesson I can…

set up a Godot 4 project, build a scene from nodes, write a GDScript that moves a sprite with the keyboard at a speed that does not depend on the frame rate, and organize, import and back up the project’s files.

Instruction

Every game engine answers the same question: how do you describe a world, and how do you tell it what to do each moment? Godot 4 answers with two ideas, nodes and scenes. (This lesson’s build is adapted from the Godot documentation’s “Nodes and scenes” and “Creating your first script” pages, by Juan Linietsky, Ariel Manzur and the Godot community, CC BY 3.0.)

Nodes. A node is one building block with one job. A Sprite2D draws an image. A Camera2D decides what part of the world is on screen. A Timer counts down. An AudioStreamPlayer plays a sound. Nodes are arranged in a tree: each node can have children, and children move with their parent. If you move a spaceship node, its flame sprite and its engine sound come along.

Scenes. A scene is a saved tree of nodes, stored as a .tscn file. A player can be a scene; so can a coin, a level or a whole menu. Scenes can be placed inside other scenes, which is how a level fills up with fifty coins that all behave the same way. When you run the game, Godot runs one main scene, and everything else hangs from it.

Scripts. A script attached to a node gives it behavior. Godot’s own language, GDScript, reads like Python: indentation shows which lines belong together, and there are no semicolons. Every script begins with extends and the node type it controls. Here is the script you will write today:

extends Sprite2D

@export var speed: float = 200.0

func _process(delta: float) -> void:
	var direction := Input.get_vector("ui_left", "ui_right", "ui_up", "ui_down")
	position += direction * speed * delta
	if Input.is_action_pressed("ui_accept"):
		rotation += 2.0 * delta

Read it line by line. @export var speed: float = 200.0 makes a variable that holds a decimal number and shows it in the Inspector, so you can tune it without editing code. _process(delta) is a function Godot calls once every frame. Input.get_vector reads the four arrow keys and returns a direction: pressing right gives (1, 0), pressing up gives (0, −1), because in Godot’s 2D coordinates y grows downward. The last two lines spin the sprite while Space or Enter is held.

Why multiply by delta? delta is the time since the last frame, in seconds. At 60 frames per second it is about 0.0167 s, so the sprite moves 200 × 0.0167 ≈ 3.3 pixels per frame. On a slower computer running at 30 frames per second, delta is 0.0333 s and the sprite moves about 6.7 pixels per frame. Either way it covers 200 pixels each second. Without delta, the game would run twice as fast on a fast computer as on a slow one, which is a bug players notice immediately.

Indentation matters. GDScript uses indentation to mark blocks, and the Godot editor indents with tabs. Type the code rather than pasting it; if you paste, check that every indented line uses the same kind of indentation, or Godot will report a “mixed tabs and spaces” error.

Files and where they live. A Godot project is a folder, and every file in it has a job shown by its extension. project.godot holds the project settings, .tscn files are scenes and .gd files are scripts. Godot also writes a small .import file beside each asset and keeps its import cache in a hidden .godot folder, which it rebuilds by itself. Assets you bring in are imported by type. Godot’s documentation lists raster images such as .png, .jpg, .webp, .bmp and .tga, vector images as .svg, and sound as .wav, .ogg (Ogg Vorbis) and .mp3. Working files from paint programs, such as GIMP’s .xcf, Krita’s .kra or Photoshop’s .psd, are not on those lists: export a .png copy and import that.

Downloading assets. Asset packs usually arrive as one .zip archive. Godot cannot use a file that is still inside an archive, so extract it, then copy only the files you need into your project folder (a subfolder named art keeps things tidy) and keep the pack’s license file with them. Kenney’s packs at kenney.nl are free and released under CC0; the download button offers a donation, and you choose “Continue without donating”. No account is needed, and you never need to pay for anything in this course.

Storage and backup. Your project lives on your computer’s internal drive, which is one copy: a failed drive, a spilled drink or a lost laptop takes it with it. Keep a second copy on a different device. A USB flash drive or external drive is the simplest route: close Godot, zip the whole project folder with the date in its name (firstname-first-scene-2026-11-10.zip), copy the ZIP to the drive, open the copy once to check it runs, then eject the drive before unplugging it so no file is left half-written. A cloud folder is a second route only if a parent or guardian has approved the service; never upload project files to a site a stranger suggests. Keep one dated backup per work session and delete only the oldest.

Work safely. Screen work is still physical work. Sit with your feet flat and the top of the screen at about eye level, keep cables off the walkway, and follow the 20-20-20 habit: every 20 minutes, look at something about 20 feet away for 20 seconds.

📖 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.

  • First Scene: Frame-Time Numbers, a Hand-Trace and a Sample Build LogSLS original; Godot documentation quoted under CC BY 3.0 (Juan Linietsky, Ariel Manzur and the Godot Engine community); license per the Godot FAQ, read 2026-09-26 · about 2 min

    Delta and frame-rate arithmetic for 30, 60 and 144 fps, a five-frame hand-trace for the no-computer route, and a sample five-line build log.

Vocabulary in context

  • node — A single Godot building block with one job, such as drawing a sprite or playing a sound.
  • scene — A saved tree of nodes (.tscn file) that can be run on its own or placed inside other scenes.
  • GDScript — Godot’s built-in scripting language, indentation-based and similar to Python.
  • delta — The time in seconds since the previous frame; multiplying motion by it makes speed independent of frame rate.
  • @export — An annotation that shows a script variable in the Inspector so it can be tuned without editing code.

Build: A sprite that answers the keyboard

Question. Can you build a scene from nodes and write a script so a sprite moves at the same on-screen speed whatever the frame rate?

Materials

  • A computer with the Godot 4 desktop editor (version 4.3 or later, standard build) unzipped to a folder on your computer; no installation or account needed
  • The icon.svg image every new Godot project includes, or one character sprite (.png) from a free Kenney asset pack (kenney.nl, CC0; choose “Continue without donating”; no account)
  • Headphones (optional for this build) and a notebook or document for the build log
  • A USB flash drive or external drive for backup (or a cloud folder a parent or guardian has approved)
Safety.
  • Set up ergonomically: feet flat, wrists straight, top of screen near eye level; use the 20-20-20 break habit during long builds.
  • Keep power and USB cables tucked away from walkways and chair wheels.
  • Save with Ctrl+S after every step, and zip a dated copy of the project folder at the end of the session and copy it to your USB drive, so a lost laptop never means lost work.

Procedure

  1. Open Godot and, in the Project Manager, create a new project named firstname-first-scene in a folder named game-design inside your Documents folder. Choose the Compatibility renderer, which runs on more machines and exports well to the web.
  2. In the Scene dock choose 2D Scene. Godot creates a Node2D root; rename it Main. Add a child node (Ctrl+A) of type Sprite2D and drag icon.svg (or a Kenney .png you extracted from the pack’s ZIP and copied into an art subfolder of the project) from the FileSystem dock onto its Texture property in the Inspector. Move the sprite near the center of the screen. Save the scene as main.tscn.
  3. Select the Sprite2D, click the Attach Script button, keep the default name and choose Create. Type the script from the lesson exactly, with tabs for indentation.
  4. Press F5 to run the project; when asked, choose Select Current to make main.tscn the main scene. Test the arrow keys and hold Space. Close the game window.
  5. Select the Sprite2D and change Speed in the Inspector to 100, then 400. Run each time and time how long the sprite takes to cross the window, which is 1152 pixels wide by default.
  6. Deliberately break it: delete “* delta” from the movement line, run, and describe what happens. Then restore it. Record each run in your build log (what you changed, what you predicted, what happened).
  7. Back up and check your files. Close Godot, open the project folder in your file manager and list in your build log each file type you see (.godot, .tscn, .gd, .svg or .png, .import) and what it is for. Zip the folder with today’s date in the name, copy the ZIP to your USB drive (or parent-approved cloud folder), open the copy in Godot to check it runs, and eject the drive before unplugging it.

Data

Speed (px/s)Predicted time to cross 1152 px (s)Measured time (s)Notes
10011.5
2005.8
4002.9
200, delta removed?

Analysis

  1. Did your measured crossing times match 1152 ÷ speed? Give one reason a hand-timed measurement might differ.
  2. Explain in your own words what went wrong when you removed delta, and why a player on a different computer would see something different.
  3. Which node would you add next to make this feel like a game, and what would it do?
  4. Which file types in your project folder did you create, and which did Godot create for you? Why would a backup that left out the .gd file be useless?

If you cannot do this build in person: If the desktop editor cannot be installed on your device, open the Godot web editor (editor.godotengine.org) in a desktop Chrome or Edge browser, create the project there and follow the same steps; before you close the tab use the Project menu’s option to download or pack the project as a ZIP, because the web editor stores files only in that browser. If neither works, trace the script by hand: for delta = 0.0167 and delta = 0.0333, compute how far the sprite moves in one frame and in one second, and explain the result.

Formative check

Work through these before moving on. They are not graded — they tell you whether the standard below has landed yet.

Simulation & tools

Godot web editor (backup route)

Use this only if the desktop editor is unavailable. Open the link in desktop Chrome or Edge, choose Start Godot editor, create a new project with the Compatibility renderer, and complete steps 2-6 of the build. Before you close the tab, use the Project menu’s option to download or pack the project as a ZIP, because the web editor keeps files only in this browser. Record in your build log the speed you tested and the crossing time you measured. If you cannot use a computer at all, complete the hand-trace described in the build’s alternative instead.

Open Godot Engine web editor ↗  ·  Godot Engine web editor · MIT open source

Fill in the blank

A sprite has speed 300 px/s. At 60 frames per second, delta is about 0.0167 s, so the sprite moves about pixels per frame and pixels per second.

+50 XP

In Godot 2D, you press the up arrow and Input.get_vector returns (0, -1). Why negative?

Screen coordinates start at the top-left corner and grow down and to the right, so up is negative y.
Make a prediction

You delete “* delta” from the movement line and run the game at 60 frames per second with speed 200. What happens?

Without delta the sprite moves 200 pixels every frame. At 60 frames per second that is 12,000 pixels per second, so it vanishes off-screen in a fraction of a second, and it would move at a different speed on a machine with a different frame rate.

Missouri standard: MM.FIL.1, MM.FIL.3

+50 XP

You downloaded a free asset pack as pixel-pack.zip. Which file can you use directly as a Sprite2D texture once you extract the archive and copy the file into your project folder?

Godot imports .png (and .jpg, .svg, .webp and other listed image types). It cannot read inside a .zip, so extract first, and a GIMP .xcf working file must be exported as .png before Godot can use it. Keep License.txt with the art, but it is not an image.

Missouri standard: MM.FIL.5, MM.FIL.6

+50 XP

The only copy of your project is on your laptop. Which backup plan protects it best?

A backup must be a complete, checked copy on a different device. The desktop is the same drive, a scene without its scripts and assets will not run, and you never upload work to a site a stranger suggests; a cloud folder is fine only if a parent or guardian has approved it.
Quick self-check

How confident are you that you can build a Godot scene from nodes and script frame-rate-independent movement?

Not yetVery confident

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.

  1. Match each file to its job in a Godot project: project.godot, main.tscn, player.gd, coin.png.import.
    Check your answer
    Answer: project.godot holds the project settings; main.tscn is a scene; player.gd is a script; coin.png.import is the small file Godot writes beside an imported asset.
    The hidden .godot folder holds the import cache, which Godot rebuilds by itself.
  2. In Godot 2D, what does Input.get_vector(“ui_left”, “ui_right”, “ui_up”, “ui_down”) return when only the left arrow is held? When only the down arrow is held?
    Check your answer
    Answer: Left: (−1, 0). Down: (0, 1).
    x grows to the right and y grows downward in Godot’s 2D coordinates, so left is negative x and down is positive y.
  3. Which of these can you drag straight onto a Sprite2D’s Texture once they are in the project folder: hero.png, hero.kra, sprites.zip, logo.svg, hero.psd?
    Check your answer
    Answer: hero.png and logo.svg.
    Godot imports raster images such as .png and vector .svg. A .kra or .psd is a paint program’s working file: export a .png copy. A .zip must be extracted first.

Application

Use the skill in context. Show your reasoning.

  1. A sprite has speed 150 px/s. How far does it move in one frame at 60 frames per second (delta ≈ 0.0167 s)? At 30 frames per second (delta ≈ 0.0333 s)? How far in one second in each case?
    Check your answer
    Answer: About 2.5 px per frame at 60 fps; about 5.0 px per frame at 30 fps; 150 px per second either way.
    150 × 0.0167 ≈ 2.5 and 150 × 0.0333 ≈ 5.0. Per second: 2.5 × 60 = 150 and 5.0 × 30 = 150. That is why motion is multiplied by delta.
  2. The default window is 1152 pixels wide. How long does a sprite moving at 320 px/s take to cross it?
    Check your answer
    Answer: 3.6 seconds.
    time = distance ÷ speed = 1152 ÷ 320 = 3.6 s.
  3. Fix the bug. A student’s sprite races off-screen on a fast computer and crawls on a slow one:
    func _process(delta: float) -> void:
        var direction := Input.get_vector(“ui_left”, “ui_right”, “ui_up”, “ui_down”)
        position += direction * speed
    Check your answer
    Answer: Change the last line to position += direction * speed * delta.
    Without delta the sprite moves speed pixels every frame, so its speed depends on the frame rate. Multiplying by delta (seconds since the last frame) turns it into pixels per second.
  4. The lesson’s script spins the sprite with rotation += 2.0 * delta while Space is held. How much does the rotation value grow if you hold Space for 1.5 seconds?
    Check your answer
    Answer: 3.0 (radians).
    The line adds 2.0 per second because it is multiplied by delta, so 2.0 × 1.5 = 3.0.
  5. Godot refuses to run a script and reports a “mixed tabs and spaces” error. What caused it, and how do you fix it?
    Check your answer
    Answer: Some indented lines use tabs and others use spaces, usually after pasting code. Re-indent every line the same way (the Godot editor uses tabs), ideally by typing the code.
    GDScript uses indentation to mark which lines belong together, so it must be one consistent kind.

Challenge

Stretch problems. Expect to think before you write.

  1. You want a sprite to cross the 1152-pixel window in exactly 4 seconds. What value should speed have, and what would the crossing time be if you then halved it?
    Check your answer
    Answer: 288 px/s; halving it to 144 px/s doubles the crossing time to 8 seconds.
    speed = 1152 ÷ 4 = 288. 1152 ÷ 144 = 8.

Review

Keep earlier skills sharp.

  1. Review (Lesson 1.1): in tic-tac-toe, which formal element are the empty squares, and why?
    Check your answer
    Answer: The resource: they are scarce, and both players compete to use them.
    A resource is whatever players must manage because there is not enough of it.

Missouri CTE — Multimedia (034356) objectives addressed: MM.ANI.6, MM.EMT.4, MM.FND.3, MM.FND.1, MM.FND.7, MM.COM.5, MM.FIL.1, MM.FIL.3, MM.FIL.5, MM.FIL.6, RST.9-10.3

Extends beyond Missouri Multimedia (enrichment): content Missouri places after Multimedia

Instructional focus: Technical skill: engine interface, scenes, nodes and a first script

Reading

First Scene: Frame-Time Numbers, a Hand-Trace and a Sample Build Log

SLS original; Godot documentation quoted under CC BY 3.0 (Juan Linietsky, Ariel Manzur and the Godot Engine community); license per the Godot FAQ, read 2026-09-26 · SLS original; quoted Godot documentation is CC BY 3.0

Why this reading. The build asks you to script movement that does not depend on the frame rate and to keep a five-line build log; this sheet gives the numbers to check your work and a hand-trace for the no-computer route.

What the Godot documentation says

The Godot documentation (CC BY 3.0, attributed to Juan Linietsky, Ariel Manzur and the Godot Engine community) says that a scene is composed of one or more nodes and that nodes are your game’s smallest building blocks, arranged into trees. That is the whole idea of this lab: small parts, arranged, each with one job.

Frame time and speed

At 60 frames per second, each frame lasts 1 ÷ 60 = 16.67 milliseconds, so delta is about 0.0167 s. Movement per frame is speed × delta.

Frame rateDelta (s)Pixels per frame at speed 200Pixels in one second
300.03336.67200
600.01673.33200
1440.006941.39200

Without * delta the sprite would move 200 pixels every frame: 6,000 pixels per second at 30 fps, 12,000 at 60 fps, and 28,800 at 144 fps. It would also run 4.8 times faster on a 144 fps machine than on a 30 fps one.

Hand-trace (no computer needed)

Start with the sprite at (100, 100), speed 200, the right arrow held, 60 fps. Each frame: new x = old x + 1 × 200 × (1 ÷ 60).

Framexy
0100.00100
1103.33100
2106.67100
3110.00100
4113.33100
5116.67100
60300.00100

Now hold up-arrow instead: get_vector returns (0, −1), so y falls by 3.33 each frame: 96.67, 93.33, 90.00. Up is negative y. Hold right and up together and the vector is normalized to length 1, about (0.707, −0.707), so diagonal movement is not faster.

A five-line build log (example)

  1. Created Sprite2D with the Godot icon; script attached; speed 200.
  2. Typed the movement lines; got a “mixed tabs and spaces” error.
  3. Retyped the indented lines with tabs; the error cleared.
  4. Tested: 60 frames of held right moved the sprite 200 pixels (measured on the debug overlay).
  5. Removed * delta as a test; the sprite left the screen in under a second. Restored it.

Each line says what you did, what broke, and the evidence it worked. This log is SLS original.

Sources: Godot documentation, Nodes and scenes (docs.godotengine.org); Godot FAQ (documentation license) (docs.godotengine.org)

Up NextComplete & Continue →

Leave a Reply Cancel reply

What Makes a Game a Game
Prev
Reading a Game: MDA and the Core Loop
Next

© 2026 The VR School | Career content by Wiley | Powered by Sejal Learning Systems.

Join free · Accreditation · Privacy Policy · Terms of Service

Modal title

Main Content