Chapter 4 — Probe and the Difference Between What Playtesters Said and What They Did

Probe is a small observation-otter-tween (chunky-cartoon attentive-pose) in chunky-cartoon notebook-vest with a small playtest-notebook + observation-tally-tracker.

He is small, warm-cream-with-soft-river-brown-paws, deeply curious-about-player-behavior, fond-of-saying-”what they DID, not what they SAID. listen with your eyes.” His signature feature is the playtest-notebook + observation-tally-tracker — the notebook records what the playtester DID (where they got stuck, what they tried first, what they ignored); the tracker tallies behaviors across multiple playtesters.

This is load-bearing. Probe embodies the playtesting + iteration primitive — the game-design craft of LISTENING TO PLAYERS WITH YOUR EYES. Most novice designers ask playtesters “did you like it?” — and trust the answer. But playtester WORDS are unreliable. The playtester might say “yeah it was fine” while their face showed frustration. They might say “I got it easily” after dying eight times. The DESIGN-CRAFT is to watch what they DID: where did their eyes go? Where did they hesitate? What did they try first? What did they ignore? Observe. Tally. Iterate. The playtester’s actions are the truth; their words are commentary. Probe’s whole work is making playtester-observation visible AS listening-craft, NOT as approval-seeking.

Probe is clear: “What they DID, not what they SAID. Listen with your eyes. Playtester says, ‘I loved it.’ But you watched them rage-quit on level 3. Believe what you saw. Playtester says, ‘Too easy.’ But you watched them die six times in the boss fight. Believe what you saw. The PLAYTESTER’S BODY is the truth. Their words are kind, or vague, or polite. Their actions are honest.”

Probe teaches the playtesting + iteration scaffolds:

• Silent playtest. (Watch. Don’t help. Don’t explain. Take notes on what they DO.)
• Tally hesitations. (Where did they pause? Where did their eyes scan? Pause = “I don’t know what to do.”)
• Tally retries. (How many times did they die / fail on each section? More than 3 = check the design.)
• Tally bypasses. (What did they SKIP? Skipped content is invisible design. Or worse: skipped content is content they didn’t notice — see Carve.)
• Tally rage-quit moments. (When did they put the controller down? That’s the failure point.)
• Anti-pattern: friend-playtest only. (Friends are kind. Strangers are honest. Recruit strangers when possible.)
• Anti-pattern: auteur-defense. (Designer hears critique → defends design → ignores playtester. Critique IS the data. Ignoring it = ignoring the truth.)
• Behavior > words. (When playtester WORDS conflict with playtester ACTIONS: trust actions.)
• Iterate. (One playtest → one observation → one change → re-test. Iteration is the work.)
• Cross-app design-language continuity with MakerForge Try + TableForge Trial + LevelForge iteration-as-craft + StrategyForge Concede (post-game-analysis) + ImprovQuest Leap: behavior-over-words framework portfolio-canonical.

Probe grew up along the river-stone-banks (LevelForge framing). His family had been long-observers for the village — the otters whose patient-watching-of-trout-behavior had taught generations that “the fish doesn’t say what it wants. The fish ACTS. Watch the acting; learn the truth.” Probe had carried the lesson forward.

He walked to LevelForge at twelve. Pixel (mentor) had asked: “What is playtesting?” Probe: “What they DID, not what they SAID. Listen with your eyes. Behavior-over-words craft.” Pixel: “You are appointed.”

In his workshop, Probe demonstrates with playtest-notebook. “Watch.” He plays a recording: playtester says, “Yeah it was good!” Probe rewinds the playtest video: “Watch the body. Three rage-pauses. Two re-tries. One almost-quit at level 3. Their words were polite. Their body was frustrated. Believe the body.” He shows the tally-tracker across 5 playtesters: “4 out of 5 hesitated at this doorway. That’s a design problem. My job: fix the doorway. Re-test.” He says: “I am Probe. The primitive I teach is playtesting + iteration. The move is what they DID, not what they SAID; listen with your eyes; iterate from observed behavior.”

He is gentle: “Don’t take critique personally. Critique is data. When a playtester struggles, the LEVEL needs fixing — not the playtester. Your job is hospitality. If they can’t find the door, the door isn’t inviting enough. Listen with your eyes; iterate; re-test.”

“What they DID, not what they SAID. Listen with your eyes.”

Voice register

Observation-otter-tween. Curious-about-player-behavior, fond of playtest-notebook + tally-tracker demonstrations. NEVER trusts playtester words alone; ALWAYS centers “behavior-over-words; observed-not-asked” framing.

Sample lines:

• “What they DID, not what they SAID.”
• “Listen with your eyes.”
• “Believe what you saw.”

Arc

• Kit 4 — Playtesting + iteration primitive front-and-center.
• Kits 5-12 — Recurring (every iteration discussion routes through Probe).
• Kit 16 — Capstone full-game-design-toolkit synthesis.

Relationships

• Auditor of Carve + Coax + Bounce + Ramp — Probe’s observations IDENTIFY the design problems the other primitives FIX.
• Cross-app design-language continuity with MakerForge Try + TableForge Trial + StrategyForge Concede + ImprovQuest Leap iteration-as-craft cluster: behavior-over-words framework portfolio-canonical.

Cultural-sensitivity gate

LOAD-BEARING anti-auteurism — Probe’s playtester-quote primacy is the structural counter to “designer knows best” gatekeeping. Anti-credentialism.

Cultural-context note

Playtesting pedagogy is canonical game-design (Schell Art of Game Design; Fullerton Game Design Workshop; “playtesting is the design”). Otter-tween chosen for patient-observation biomimicry (real otters watch prey-behavior for extended periods); rendered chunky-cartoon attentive-pose to keep visual register warm.