Video Game Design and Coding · PLECK lesson

PLECK lesson 174 · suggested week 35, day 4

Audit licensing, privacy and submission safety

Objective. Check the final package before sharing it privately with a teacher.

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: Paper and pencil or a private text document, Local course folder and prior checkpoint, No paid assets or public account required.

Comes after VGC-L173.

Review every bundled asset and engine notice requirement, then remove unused files, private recordings and accidental personal metadata. Keep original project source and only necessary test evidence. The course never requires public publication. A submitted HTTPS reference should point to a private downloadable artifact the teacher is permitted to access; it is stored as text, not executed by the assignment page. If ZIP upload is unavailable, keep the local artifact and use the approved private hand-in process rather than exposing files publicly.

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.

Audit licensing, privacy and submission safety — evidence task

  1. 1. Complete final asset/privacy/package checklist.
  2. 2. Verify any submitted link resolves to the intended downloadable source with appropriate access.

Deliverable. Final rights/privacy checklist and clean source artifact.

Acceptance checks

Understanding question. Why should the site store a project link as text instead of executing its contents?

Submit readable text or photos/scans of each numbered design page. Audio explanation may supplement a diagram or text, not replace requested artifacts.

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 ____________________