Video Game Design and Coding · PLECK lesson

PLECK lesson 56 · suggested week 12, day 1

Write choices that communicate intent

Objective. Align button labels with the action they perform.

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.

Original writing, clarity, UI scaling and a finished puzzle

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

A choice label is a promise about what the player will do. “Ask about the map” should not unexpectedly destroy the key. Ambiguity can be part of a story, but hiding basic control meaning is usually an interface defect. Revise each choice with a verb and object. Keep passages concise enough to fit the screen. Use your own writing or clearly attributed permitted material; replacing a famous character’s name does not make copied dialogue original.

Worked example

A long passage can become two short passages connected by Continue. This preserves readable text instead of shrinking the font until the interface technically fits.

Write choices that communicate intent — evidence task

  1. 1. Revise every choice label to communicate an action.
  2. 2. Compare two before/after labels and explain how the new wording reduces uncertainty.

Deliverable. Revised story text and two label comparisons.

Acceptance checks

Understanding question. What makes a choice label misleading?

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. Keep one complete path working while editing text. Limit the story to six to ten passages until every link is tested. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.

Optional extra. Add a nonessential lore branch that does not block either ending. Document one changed parameter, your prediction, and the observed effect; optional, not required for completion.

Name ____________________ Date ____________________