Video Game Design and Coding · PLECK lesson

PLECK lesson 80 · suggested week 16, day 5

Review scope using evidence

Objective. Adjust the plan before expanding the implementation.

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.

Scope, acceptance criteria, architecture and first playable integration

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

Review the slice against your eight-test contract. Mark pass, fail or not yet implemented for each test. A failed minimum requirement takes priority over optional particles, extra levels or online features. If the project is too large, reduce content while preserving the stated learning goals and a complete loop. Record the scope decision rather than quietly deleting tests to claim success. A parent may approve a reduced minimum; the final readme must describe the actual game honestly.

Worked example

A minimum one-room collector can be described by one action, one obstacle, visible progress, one ending and restart. Extra rooms are optional until that loop works.

Review scope using evidence — evidence task

  1. 1. Complete the eight-test status table.
  2. 2. Choose the next three tasks in dependency order and identify one feature to defer.

Deliverable. Scope review and three-task build plan.

Acceptance checks

Understanding question. When is changing an acceptance criterion legitimate?

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. Choose one earlier genre and one room. Keep one player action, one obstacle type and one goal until the loop works. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.

Optional extra. Propose an optional mechanic but do not build it before the minimum tests pass. Document one changed parameter, your prediction, and the observed effect; optional, not required for completion.

Name ____________________ Date ____________________