Video Game Design and Coding · PLECK lesson

PLECK lesson 168 · suggested week 34, day 3

Rank beta findings by impact

Objective. Distinguish blockers, barriers and preferences.

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

Classify each finding as crash/data risk, blocked goal, major usability barrier, minor defect or preference. Frequency and severity both matter. One reproducible data-loss bug may outrank several cosmetic complaints. A preference is not automatically a defect, but repeated confusion can justify a design change. Select three repairs in priority order and define a verification test for each. Keep suggestions that exceed scope on the future list rather than rebuilding the entire game at release time.

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.

Rank beta findings by impact — evidence task

  1. 1. Classify all beta findings and choose three repairs.
  2. 2. Write a verification test and regression area for each.

Deliverable. Beta triage table and three-repair plan.

Acceptance checks

Understanding question. Should every tester suggestion become a feature?

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 ____________________