Video Game Design and Coding · PLECK lesson

PLECK lesson 160 · suggested week 32, day 5

Complete a content-ready integrated build

Objective. Create a stable candidate before expanding level or story content.

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.

Validated data, state behavior, integration and restart consistency

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

Run the complete twelve-test contract against the integrated game. Any remaining minimum defect becomes a blocking task. If tests pass, name the build content-ready and save a restore-tested snapshot. This is the base for adding the promised amount of content, not a reason to add unrelated features. Update architecture diagrams if actual code has changed. A technical design document is useful only when it reflects the artifact being assessed.

Worked example

A richer-system table can pair valid values with safe fallback behavior. Unknown checkpoint IDs map to a known start marker rather than a path loaded from input. 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.

Complete a content-ready integrated build — evidence task

  1. 1. Run all twelve acceptance tests.
  2. 2. Package a content-ready checkpoint and update diagrams to match code.

Deliverable. Content-ready source artifact, twelve-test report and updated technical design.

Acceptance checks

Understanding question. Why update diagrams after implementation changes?

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 focused test scene from week 30 to compare isolated behavior with the main game. Keep one explicit state owner. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.

Optional extra. Add one validated field, AI cue or generation constraint only after existing tests pass. Document one changed parameter, your prediction, and the observed effect; optional, not required for completion.

Name ____________________ Date ____________________