Video Game Design and Coding · PLECK lesson

PLECK lesson 171 · suggested week 35, day 1

Package source so another person can inspect it

Objective. Create a clean source archive and clear launch instructions.

Godot Engine Standard desktop editor 4.7.2-stable, GDScript (Godot 4), Compatibility renderer. Headless Godot 4.7.2.stable.official.ed1daf0bf passed 106 assertions on the supplied scaffolds, including malformed JSON saves. Audio used the Dummy driver and a synthetic WAV, not a speaker. The visual editor, browser export, and signed-in submission were not tested. The desk still does not run a student's own upload.

About 55 minutes. The due date is chosen by a parent.

Source artifacts, local export, optional web and final checks

Suggested pace: Recall and predict 5 min; Read instruction and scaffold 12 min; Build or design the assigned artifact 25 min; Run acceptance tests 8 min; Explain and checkpoint 5 min.

Materials: Godot Standard 4.7.2 desktop editor (GDScript, Compatibility renderer), Local course folder and prior checkpoint, No paid assets or public account required.

Comes after VGC-L170.

The source artifact must include project.godot, all referenced .tscn and .gd files, original assets and required notices. Exclude regenerable .godot cache and unrelated personal files. Keep filenames stable and paths relative. Write a readme with engine version, renderer, main scene, controls, goal, richer system, comfort features, known issues and credits. Extract into a fresh local folder and run through the editor. A ZIP that contains only an executable is not an editable source submission.

Worked example

A source archive contains editable scenes and scripts. A runnable export may contain a binary and pack, which is useful for play but not a substitute for editable evidence. Scaffold C-TESTS — A tiny pure-function test harness Setup: Attach to Node TestLab. If using command line, create a separate SceneTree harness rather than running this Node script with --script. Run current TestLab scene in editor; assert reports a failed condition in Debugger. No external test framework or package is needed. ```gdscript extends Node func bounded_score(old_score: int, change: int) -> int: return clampi(old_score + change, 0, 999) func _ready() -> void: assert(bounded_score(10, 2) == 12) assert(bounded_score(0, -3) == 0) assert(bounded_score(998, 9) == 999) print("3 score checks passed") ```

A tiny pure-function test harness

GDScript (Godot 4, not Scratch, Python, JavaScript or C#). Scaffold C-TESTS. Copy starts from this text. The desk does not run it.

Scene and node setup

Attach to Node TestLab. If using command line, create a separate SceneTree harness rather than running this Node script with --script. Run current TestLab scene in editor; assert reports a failed condition in Debugger. No external test framework or package is needed.

extends Node
func bounded_score(old_score: int, change: int) -> int:
    return clampi(old_score + change, 0, 999)
func _ready() -> void:
    assert(bounded_score(10, 2) == 12)
    assert(bounded_score(0, -3) == 0)
    assert(bounded_score(998, 9) == 999)
    print("3 score checks passed")

Checks to run in the editor

Native Godot 4.7.2.stable.official.ed1daf0bf headless compile and representative node-tree/runtime tests passed; see native-qa-results.json. Visual UI, audible output, exports and website submission still need separate checks.

Package source so another person can inspect it — evidence task

  1. 1. Create the clean source ZIP and complete readme.
  2. 2. Restore it and inspect every referenced resource.

Deliverable. Final source package and readme.

Acceptance checks

Understanding question. Why exclude unrelated personal files and caches?

Include a downloadable project ZIP with project.godot, .tscn, .gd and original asset files when code changes. A private, teacher-accessible download link to that ZIP is equivalent. Screenshots or a playthrough do not replace editable source.

If this is still shaky. The required deliverable is an editor-runnable source ZIP. Native or web export is optional if templates or hardware are unavailable. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.

Optional extra. Compare an optional export with editor play and report one platform-specific limitation. Document one changed parameter, your prediction, and the observed effect; optional, not required for completion.

Name ____________________ Date ____________________