Video Game Design and Coding · PLECK lesson

PLECK lesson 59 · suggested week 12, day 4

Evaluate a narrative playtest

Objective. Separate a reader’s interpretation from a software failure.

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

During a private test, ask the player to think aloud only if comfortable. Record whether they understand the goal, notice the key, interpret the gate feedback and reach an ending. A player choosing an ending you did not prefer is not automatically a bug. A button going to a nonexistent page is a software failure. A clue that nobody understands is a design issue. Classify findings so the fix matches the cause rather than rewriting the entire story after one unexpected choice.

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.

Evaluate a narrative playtest — evidence task

  1. 1. Run a local test or structured self-test with four observation questions.
  2. 2. Classify three findings as code, design, content or preference.

Deliverable. Anonymous narrative-test report and two prioritized revisions.

Acceptance checks

Understanding question. Is choosing the less cheerful ending necessarily a defect?

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 ____________________