Video Game Design and Coding · PLECK lesson

PLECK lesson 2 · suggested week 1, day 2

Model a turn before using a computer

Objective. Write and execute an unambiguous algorithm.

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.

Rules, decisions, feedback, consent and an offline workspace

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

An algorithm is an ordered set of steps with enough precision for another person to follow. Give a paper “computer” only the instructions you wrote; it must not guess your intention. In Paper Courier, decide first whether the requested move is legal, then spend energy if needed, then move the token, then check delivery. The order matters: moving before checking energy allows an illegal action. Use numbered steps and explicit if/otherwise branches instead of vague words such as “handle the turn.”

Worked example

A tiny paper model: start with position 1 and energy 2. A safe move adds one position without changing energy. State is written before and after an action, so another person can replay it.

Model a turn before using a computer — evidence task

  1. 1. Write a turn algorithm for the two movement choices.
  2. 2. Ask a parent or act as a literal computer and execute safe move, affordable fast move, and unaffordable fast move.

Deliverable. Numbered algorithm and three traced examples.

Acceptance checks

Understanding question. Why should validation happen before changing position?

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 a paper token, six squares and a single delivery goal. Say each rule aloud before adding another. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.

Optional extra. Compare two different rule choices without adding more components. Document one changed parameter, your prediction, and the observed effect; optional, not required for completion.

Name ____________________ Date ____________________