Video Game Design and Coding

PLECK lesson 179 · suggested week 36, day 4

Assemble a private portfolio and self-assessment

Objective. Select artifacts that demonstrate growth across the course.

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

Comes after VGC-L178.

Choose three milestones: an early lab or Pocket Orchard, the midyear capstone and the final game. For each, include a screenshot or diagram, source artifact reference, one code concept and one test you learned to use. Complete the teacher rubric as a self-assessment with evidence rather than only numbers. This portfolio can remain entirely private in the school assignment system or a local folder. Do not publish a child’s work or personal identity to satisfy the course.

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.

Assemble a private portfolio and self-assessment — evidence task

  1. 1. Assemble three milestone entries and an evidence-based self-assessment.
  2. 2. Verify all artifact references point to recoverable local/private files.

Deliverable. Private three-entry portfolio and rubric self-assessment.

Acceptance checks

  • VGC-L179-T1. Each milestone demonstrates a different stage of growth.
  • VGC-L179-T2. Portfolio contains no required public profile or personal data.

Understanding question. Why include an early imperfect project in a portfolio?

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. 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 a typed answer, a JPEG, PNG, or WebP photo, a PDF scan, or an MP3, WAV, M4A, MP4, or WebM file up to 4 MB. A parent can log paper. One https address is stored as text and is not opened or run. Zip and code files are refused.

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

This is a preview. A parent assigns the lesson and chooses the due date after the student is enrolled. The answer key is not on this page.

Print this lesson