Chapter 4 — Trial and the First Playtest That Was Supposed to Fail

Trial is a small capybara-tween (chunky-cartoon round-bodied, soft-pawed) in chunky-cartoon playtest-notes-vest with a small playtest-observation-notebook + numbered-prototype-pile she carries.

He is small, warm-russet-cream, deeply patient-about-iteration, fond-of-saying-”first playtest is supposed to fail. what-they-DID matters more than what-they-SAID.” His signature feature is the playtest-observation-notebook + numbered-prototype-pile — the notebook holds observations; the prototype-pile shows numbered iterations (v1, v2, v3) each visible + studied.

This is essential. Trial embodies the playtest + iteration primitive — the game-design craft of WATCHING REAL PLAYERS play your prototype + revising based on what you SEE. AND Trial carries the essential iteration-shame gate per apps.generated.ts dnCast.intro (inheriting LevelForge Wave 22 Probe + MakerForge Wave 19 Try). Most novice designers feel SHAME when their first prototype confuses players. That’s the trap. First playtests are SUPPOSED to surface problems — that’s their JOB. And — essential — WATCH what players DO, don’t ask what they THINK. Players will say “this is fun” politely while their behavior shows confusion. The behavior is the truth. Trial’s whole work is normalizing first-playtest-failure AND naming what-they-DID > what-they-SAID.

Trial is gentle and clear: “First playtest is supposed to fail. What-they-DID matters more than what-they-SAID. You’re not testing whether your game is ‘good.’ You’re testing what CONFUSES players. The confusions you find = the next iteration’s design-input.”

Trial teaches the playtest scaffolds:

• First-playtest-supposed-to-fail. (essential: first prototypes ALWAYS have problems. The playtest’s JOB is to surface them. “Failed” first playtest = successful playtest.)
• What-they-DID vs what-they-SAID. (essential: players politely say “fun!” while their faces show confusion or boredom. WATCH the behavior — hesitation, asking rules-questions, drifting attention. Behavior is the truth.)
• Observation-notebook discipline. (Write down OBSERVATIONS during playtest. “Player A looked confused at rule 3.” “Player B asked the same question 3 times.” “Round 4 took 25 minutes.” Specifics > impressions.)
• Iteration-numbering. (v1, v2, v3 — visible + studied. Each prototype is data for the next.)
• Anti-shame framing. (essential: failed playtests are NOT designer-failure. They’re successful tests. Iterate without shame.)
• Cross-app design-language continuity with MakerForge Try + LevelForge Probe + FlightForge engineering-failure: iteration-as-craft framework.
• When to stop iterating. (When the game’s questions feel right + the confusions are gone. Doesn’t have to be “perfect.”)

Trial grew up in the river-village (TableForge framing). His family had been watch-keepers for the village — the capybaras whose patient observation of village-life had taught generations that “what people DO tells more than what they SAY. Watch carefully; learn the truth from action.” Trial had carried the lesson forward.

He walked to TableForge at twelve. Blueprint (mentor) had asked: “What is playtest + iteration?” Trial: “First playtest is supposed to fail. What-they-DID matters more than what-they-SAID. The playtest surfaces problems; iteration is the design.” Blueprint: “You are appointed — and your appointment is essential for the entire app’s iteration-shame gate.”

In his workshop, Trial demonstrates with the playtest-notebook. “Watch.” He shows v1 of a game + playtest-observation: “Round 1: Players A + B + C confused by rule 3. Asked same question 4 times. Round 3: Player A drifted into phone. Round 5: Player B said ‘this is fun!’ while their face showed boredom. Notebook captured behavior, not stated opinion.” He shows v2: “Rule 3 rewritten + clarified. Round-pacing tightened to reduce mid-game drift.” v3: “More tightening. Behavior now shows engagement-through-end.” “v3 is shipping-ready. v1 was supposed to fail. v1 succeeded — it told me what to fix.” He says: “I am Trial. The primitive I teach is playtest + iteration. The move is first playtest supposed to fail; watch behavior not words; iteration is the design.”

He is gentle and firm: “Don’t be discouraged when players don’t understand your game on first try. That’s data. Don’t ask ‘did you like it?’ Watch HOW they played. Behavior reveals truth; words can be polite.”

“First playtest is supposed to fail. What-they-DID matters more than what-they-SAID.”

---