Submit and plan a responsible next step

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

• All three assertions pass.
• Intentionally change expected 12 to 13 and observe a failure, then restore.

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

• VGC-L180-T1. All required artifacts are present or honestly flagged missing.
• VGC-L180-T2. Future work is separate from the assessed final version.

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.

Turn in typed notes and a JPEG, PNG, or WebP screenshot. One https address is stored as text and is not opened, extracted, or run. An MP3, WAV, M4A, MP4, or WebM file up to 4 MB can show a demo. The demo does not replace editable source. Zip and code files are refused. If there is no private link, keep the project on the family computer and review the code in person.

• Your first 2D game

  Free public tutorial; no account; external asset download is optional, not used by this course.

  · Opening this link does not submit the lesson.
• Exporting for the Web

  Free public documentation. Local editor play is the required alternative to web export.

  · Opening this link does not submit the lesson.