PLECK lesson 29 · suggested week 6, day 4
Observe a private playtest
Objective. Collect anonymous observations without coaching every action.
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.
Functions, parameter experiments, original challenges and evidence
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-L028.
Ask a willing family member to try the game locally; if nobody is available, replay after a break using the written instructions only. Explain what will be observed and let them stop. Do not record a face, full name or personal information. Watch where they hesitate, miss feedback or misunderstand controls. Avoid directing their hands; a confused action is useful evidence about the interface. Separate observations from interpretations: “pressed Space three times” is an observation; “wanted to jump” is an interpretation.
Worked example
Two parameter trials can use the same start and route while changing only speed. Record an observation such as two wall contacts rather than an unsupported claim such as more fun.
Pocket Orchard starter, as text files. Open the files in Godot on the family computer. This page does not download a zip or run the project.
Observe a private playtest — evidence task
- 1. Conduct a five-minute local test or structured self-test.
- 2. Record three observations and rank two improvements by impact.
Deliverable. Anonymous playtest sheet and prioritized issue list.
Acceptance checks
- VGC-L029-T1. Notes contain no identifying player data.
- VGC-L029-T2. Each proposed improvement links to an observed problem.
Understanding question. Why avoid explaining every confusing part during the test?
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 the three-coin version working. Duplicate the project folder before experimenting with one parameter at a time. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.
Optional extra. Make one alternate layout with the same rules and compare route clarity. Document one changed parameter, your prediction, and the observed effect; optional, not required for completion.
Turn in a typed answer, a JPEG, PNG, or WebP photo, a PDF scan, or an MP3, WAV, M4A, MP4, or WebM file up to 4 MB. A parent can log paper. One https address is stored as text and is not opened or run. Zip and code files are refused.
- Godot step by step: nodes, scenes, GDScript, input, signals
Free public documentation, no account. Same class help is available within the desktop editor.
· Opening this link does not submit the lesson.
This is a preview. A parent assigns the lesson and chooses the due date after the student is enrolled. The answer key is not on this page.