Video Game Design and Coding · PLECK lesson

PLECK lesson 180 · suggested week 36, day 5

Submit and plan a responsible next step

Objective. Close the course with a complete artifact and realistic learning plan.

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.

Code defense, design evidence, portfolio and future learning

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

Submit the final source artifact, readme, credits, twelve-test contract/results, richer-system evidence, playtest/repair reports, demo and reflection. Keep a restore-tested local backup. Choose one future skill, such as more advanced level design, navigation or deeper GDScript data structures, and define a small experiment with a pass condition. Do not modify the frozen final artifact to begin that experiment. Completion here records evidence of learning; the parent/teacher determines evaluation without an automatic credit or accreditation claim.

Worked example

A final explanation predicts a changed input, runs it and compares results. An unexpected result becomes a debugging opportunity rather than something to conceal. 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.

Submit and plan a responsible next step — evidence task

  1. 1. Submit the final evidence checklist and confirm backup restoration.
  2. 2. Write one next-step experiment with objective, materials, risk and measurable result.

Deliverable. Final capstone evidence bundle, backup confirmation and next-step plan.

Acceptance checks

Understanding question. What should you do before experimenting beyond the final release?

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. Use the submitted source, not memory alone. Choose one event and one boundary test you can explain clearly. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.

Optional extra. Propose a future feature with explicit tests and risks, without implementing it into the frozen final artifact. Document one changed parameter, your prediction, and the observed effect; optional, not required for completion.

Name ____________________ Date ____________________