Video Game Design and Coding · PLECK lesson

PLECK lesson 167 · suggested week 34, day 2

Observe beta play without leading the player

Objective. Collect task outcomes and concrete usability evidence.

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.

Consent, observation, severity, focused fixes and regression

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

Run the test locally with a willing family member or conduct a labeled self-test after a break. Record completed, difficult or failed for each task and note observable actions. Ask neutral questions such as “What did you expect?” rather than “Was that button confusing?” Let the player stop. Do not upload recordings publicly. Capture the candidate version, but not the tester’s real identity. A test can be useful even when it reveals that your favorite feature is hard to understand.

Worked example

A neutral beta task asks the player to find and use a comfort setting. Notes record what they tried before proposing an interface repair.

Observe beta play without leading the player — evidence task

  1. 1. Conduct the five-task beta test.
  2. 2. Record at least five observations and separate interpretation from fact.

Deliverable. Beta observation report.

Acceptance checks

Understanding question. Why is “What did you expect?” less leading than “Was that bad?”

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. Test locally with an anonymous script. If no tester is available, label a structured self-test and follow the same tasks. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.

Optional extra. Ask for one optional qualitative preference only after task observations are recorded. Document one changed parameter, your prediction, and the observed effect; optional, not required for completion.

Name ____________________ Date ____________________