Playtest Report — Round 2 — Mae (First-Time Coop Partner)

Resolution Audit — My Round 1 Top 5

#	Issue	Round 2 Response	Verdict	Notes
1	Lisp key nomenclature is a barrier to entry	On-screen verbs replace Lisp names. “[ENTER]” not “[CAR]”. Diegetic tutorial teaches in context.	RESOLVED	Verb hints make keys intuitive. Lisp jargon hidden from UI. This should remove the “why is it called CAR?” friction.
2	No visibility into partner’s location or state	Status bar shows “[LINKED: ALEX (Temple Quarter)]”. LINK key opens partner menu. Shared map access. Message system.	RESOLVED	Multi-channel partner visibility is strong. Status bar makes Alex’s whereabouts clear. The in-room chime for partner arrival is nice.
3	CONS is overloaded and context is ambiguous	Context-aware hints: “[COMBINE: merge items]” vs. “[COMBINE: prepare offer]” vs. “[COMBINE: secure rope]“	RESOLVED	Hints are specific and learnable. Watching the hint change per context teaches you the operation. Good teaching surface.
4	Multiplayer sync is invisible, failures are mysterious	Sync indicator ”✓” or ”⚠” in status bar. Pre-puzzle sync check. Clear error messages. Graceful degradation to solo variant.	RESOLVED	The sync protocol is now explicit. Cable-loosening won’t surprise you. Clear recovery paths reduce blame-blaming.
5	No early coop moment (everything solo-able for first 45 min)	Dual-lock puzzle at minute 15–20. Both keys required. Both CONS simultaneously. Both feel essential. First shared reward.	RESOLVED	This is the critical fix. By minute 20, Mae feels like a partner, not a passenger. The vault-opening moment is earned.

Tally: 5/5 RESOLVED. All top-line issues addressed with substance, not lip-service.

The First 30 Minutes (Round 2 Re-Walk)

Let me walk through what this actually feels like now.

Minute 0–5: Boot and Sync

I turn on my KN-86 with Alex. The screen is amber and calm. Cipher’s voice greets us: “THRESHOLD SYNCHRONIZED.” I see “[LINKED: ALEX ✓]” in the status bar. We’re both in Market Square.

Good: I immediately feel the connection. The device is telling me “Alex is here with you right now.” This is coop, not solo.

Clear: No ambiguity about whether we’re linked. The status bar is crisp.

Minute 5–10: Tutorial with Keeper

We walk into the Inn. The KEEPER NPC has a task: teach us the controls.

KEEPER: “Press ENTER to go deeper into a room. Here, try entering that back door.”

Alex nudges me. I press CAR + numpad 8. A new room renders. I didn’t know it was “enter,” but the on-screen hint said “[ENTER: drill in].” I tried it. It worked.

KEEPER continues: “Press NEXT to move between rooms here. Try it.”

I CDR. I’m in another room. The hint said “[NEXT: sibling].” I don’t yet know what “sibling” means, but I pressed the key and moved sideways through the inn. Intuitive.

Good: I’m learning verbs by doing, not by reading a manual. The Keeper is patient. The hints on-screen reinforce the Keeper’s instructions.

What still could confuse me: I still don’t know what “ENTER” means why (the Lisp metaphor is silent). But I don’t need to know yet. I can learn by repetition.

No quit moment here. I’m curious about the next room.

Minute 10–15: Independent Exploration

KEEPER: “Alright, you’re ready. Go explore. I’ll stay here.”

Alex says, “I’m going to talk to the Quest-Giver. You go poke around the Temple.”

We split up. I press ENTER (CAR) and explore. I NEXT through some Temple rooms. I find a locked vault with a description: “This vault is sealed. A keyhole glows faintly. A plaque reads: ‘Two keys required. One hidden, one guarded.’”

I find a pedestal with a puzzle above it. Cryptic runes. A scroll next to it says “Solve this to claim the Eastern Key.”

I’m not trying to solve it yet—just getting the lay of the land.

Alex is in Market Square talking to the QUEST-GIVER. I can’t see Alex’s screen, but the status bar tells me “[LINKED: ALEX (Market Square)].” I know exactly where he is. No “where are you?” interrupting the flow.

We reunite in 5 minutes and compare notes.

Alex: “The Quest-Giver wants both keys to open a vault. One is in the Temple (where you are), and one is held by a merchant on the docks.”

Me: “I found a puzzle. Want to help?”

Good: We’re comparing knowledge. We already have context for a two-part objective. Neither of us has all the pieces. This is emergent coop—not scripted, but structured.

Minute 15–20: The Vault Puzzle

Alex and I go back to the vault together. The puzzle I found earlier requires a dexterity check—pressing a sequence of directional keys in 20 seconds. I get hung up on the third sequence. Alex reads the scroll aloud while I attempt it. On the third try, I nail it. The Eastern Key is mine.

Alex meanwhile negotiated with a merchant NPC and obtained the Western Key (it cost 50 credits, but the merchant liked his offer).

We stand in front of the vault. The screen shows: “DUAL-LOCK VAULT. TWO KEYS REQUIRED. INSERT SIMULTANEOUSLY.”

Below that: “Sync check: ALEX ready? [CONFIRM]”

Alex presses CONFIRM on his deck. The screen counts down: “3… 2… 1…”

We both press CONS (context hint: “[COMBINE: insert key into lock]”). We both press EVAL (context hint: “[COMMIT: execute]”).

The vault door swings open. Cipher announces: “VAULT OPENED. PARTNERSHIP SYNCHRONIZED. BOTH OPERATORS GAIN REPUTATION.”

Emotional beat: This is it. We did something neither of us could do alone. The sync check made it feel ceremonial, not accidental. The shared reward (rare item inside, +25 rep each) is tangible.

Me (genuine): “That actually worked.”

Alex: “Yeah. This is why multiplayer is better than solo.”

By minute 20, I’m hooked. I want to see what comes next.

Minute 20–30: Momentum

Inside the vault, we find a rare item (Obsidian Shard) and a clue: “The Obsidian Shard is a key to deeper mysteries. Seek the Archive if you wish to understand its purpose.”

We head toward the Archive. We know there’s more to uncover. The game has given us a breadcrumb, but we’re not forced to follow it. We could explore the docks instead, or rest at the inn. But we’re curious.

Good: The first 30 minutes have a strong narrative thread. We’re not just solving puzzles for points—we’re uncovering a mystery. And we’re uncovering it together.

By minute 30: Would I continue? Absolutely. I’d play for another 90 minutes without hesitation.

Readability Recheck

My Screen — Can I tell what I’m looking at?

Status bar (top): “[LINKED: ALEX (Market Square)] REP: 320 CREDITS: 1,200¤ HEALTH: 40/50”

Yes. I know Alex’s location, my reputation, my money, my health. All essentials at a glance. The link status is clear—solid ✓ or flashing ⚠.

Room description:

MARKET SQUARE
The heart of Threshold. Merchants hawk wares...
EXITS: N: TEMPLE QUARTER  E: DOCKS  S: SLUMS  W: ARCHIVE
NPCS: * QUEST-GIVER  + MERCHANT_ARLIN  = SCHOLAR_JAI
ITEMS: - copper coin  - torn scroll  - wineskin

Clear. I can see where I can go, who’s here, what I can pick up.

Action hints (bottom):

“[ENTER: drill in] [NEXT: sibling] [COMBINE: interact] [EXAMINE: inspect]”

These are contextual and plain English. I no longer see “[CAR: enter].” The Lisp names are gone from the UI. Good design.

Alex’s Screen — Can I tell what Alex is doing?

If Alex and I are in different rooms, my status bar shows “[LINKED: ALEX (Temple Quarter)].” That’s clear. I can press LINK to open a partner status menu and see his health, inventory count, current quest. That’s sufficient visibility.

If we’re in the same room, I see his avatar (a simple character marker, implied by the design) and can coordinate directly.

No more “Where are you?” interruptions. The design solved this.

One small note: The design says “In-room notifications: When a linked partner enters your room, a chime plays (YM2149 tone). Cipher announces: ‘ALEX has entered.’” This is excellent for asynchronous play. If I’m searching for a key and Alex shows up, I’ll hear it before seeing the change. Immersive.

Verb Jargon — Did the Diegetic Teaching Land?

The design promises “contextual on-screen hints and a tutorial NPC.” Does it deliver?

The Tutorial NPC (KEEPER)

Yes. The KEEPER walks me through each verb in the first 10 minutes with live examples. “Press ENTER to explore this door. Now you try.” I press CAR. I enter. I didn’t have to know the verb was called ENTER—I just followed instructions and learned by doing.

By minute 5, I’ve pressed each verb once or twice. By minute 10, I’m confident enough to split up from Alex.

This is teaching by immersion, not by manual. Good.

The On-Screen Hints

“[ENTER: drill in]” is better than “[CAR: enter].” But here’s what I notice:

ENTER teaches “drill in” (active, spatial imagery).
NEXT teaches “sibling” (confusing until I learn that rooms have structure).
COMBINE teaches context (“merge items” vs. “prepare offer” vs. “interact”).
EXAMINE teaches “inspect” (clear).

I don’t need to know why they’re called these things. The hints are concrete enough that I can use them without understanding the Lisp metaphor. And over time, if I play more, I might notice the pattern: “ENTER drills into structure, NEXT traverses siblings, COMBINE constructs new state.” That’s mastery. But I don’t need it to start.

Do I Still Hear Jargon?

No. The on-screen labels use plain English. Cipher voice uses descriptive language (“You’ve entered deeper into the network.”). The physical keycaps still say CAR/CDR/CONS, but I don’t look at those during play.

The Lisp jargon is hidden. This works.

New Red Flags for New Players

I read the Round 2 draft carefully. Here’s what might still trip up a newcomer:

1. EXAMINE vs. APPLY Is Not Obvious

The design introduces EXAMINE as a new verb distinct from APPLY. EXAMINE is “deep inspection of an object.” APPLY is “execute a stored LAMBDA sequence.”

In the first 20 minutes, I won’t encounter APPLY (that’s for advanced macros). So EXAMINE feels like a random key, not a verb I need.

When would I press EXAMINE? The design says “Read this scroll, talk to Keeper at length, analyze trap mechanism.” But the on-screen action hints don’t say when to use EXAMINE. I’d have to experiment or read the manual.

Fix (optional): In the first 30 minutes, EXAMINE is rarely needed. But if the tutorial includes “Read this scroll” as an action, the KEEPER should say: “Press EXAMINE to read it.”

This is minor. Not a blocker, but an edge case.

2. Procedural Wilderness Might Feel Abstract

The design talks about “biome seeding by cipher_seed” and “deterministic wilderness.” This is clever, but it’s not visible in the first 30 minutes. All my exploration is handcrafted (Market Square, Temple, Archive, Docks).

Later, if I venture into the forest and find Clearing 3 (procedurally generated), I might feel a tonal shift. “This room doesn’t have personality. It’s just a room.” But the design acknowledges this risk and proposes handcrafted encounter tables to vary the biomes.

This is a late-stage risk, not a first-30-minutes problem. I won’t bounce in minute 20 because the forest is procedural.

3. Knowledge System Is There but Not Immediate

The design says you learn things, and they appear in a SYS menu. But in the first 30 minutes, I probably won’t trigger knowledge acquisition (no books read, no puzzles solved “at length”). The system is silent.

By hour 2, if I’ve read an archive book or solved a cipher, I’ll notice: “KNOWLEDGE ACQUIRED: Cipher rotation pattern.” That’s good. But a new player won’t see the system at work until later.

Not a red flag, just a note: knowledge progression is subtle.

4. Message System Might Go Unused

The design talks about leaving messages at NPCs (“ALEX left a note at the Inn: ‘Key found in east tower.’”). This is useful for asynchronous play, but two players in the same session won’t use it. They’ll just talk to each other.

The system is there if we unlink and reconnect later. Nice, but not first-30-minutes relevant.

5. Multiplayer Sync Edge Cases Are Complex

The design specifies: “If cable loosens mid-puzzle, screen shows ‘Connection unstable.’” But what if the cable is so loose that it disconnects and reconnects repeatedly? What if the latency is flaky but not over 500ms?

I trust the error recovery (retry, degrade to solo, etc.), but a first-time player might feel anxious: “Is the cable bad, or is this normal?”

The design mitigates this by showing sync status explicitly. That’s good. But I’d recommend a very clear in-game message: “Latency high. Cable may be loose. Check connection and continue.”

Not a blocker, but worth a usability test.

Verb Disambiguation — Tested at Minute 10–15

In the Inn, I pick up a rope. The hint says “[COMBINE: interact]” (context-aware, not specific). I thought: “What does interact mean here?”

Then I CDR-ed to another room and found an NPC. The hint changed to “[COMBINE: prepare offer to INNKEEPER].” Ah. Different context, different meaning.

By the time I left the Inn, I understood: COMBINE is context-sensitive. Same key, different operations.

This is actually elegant. The hints teach you through repetition, not through a manual.

Did I stumble? Once or twice (“Is COMBINE for talking or for picking up?”), but not enough to break the flow. By minute 15, I was confident.

Final Call

I’m going with: YES I WILL PLAY IT WITH ALEX — ship the final spec.

Here’s why:

The first coop moment lands. By minute 20, I feel like a partner, not a passenger. The vault-opening sequence is earned and emotional. This is the hook that makes multiplayer essential.
Onboarding is solid. The KEEPER tutorial is diegetic and natural. Verb hints are context-aware and teach by doing. I’m not confused about controls by minute 15.
Partner visibility works. I can see where Alex is, check his status, coordinate in real-time. The “[LINKED: ALEX ✓]” status bar eliminates the “where are you?” friction.
Verb jargon is hidden. Lisp names don’t appear on-screen. Hints use plain English verbs. I don’t need to know what CAR means to play the game.
Multiplayer sync is explicit. Cable issues are no longer mysterious. Sync checks, status indicators, and graceful degradation give me confidence.

Caveat: I haven’t played the 2-hour session yet. If the middle game (minute 30–90) loses momentum, I might bounce. But the first 30 minutes are strong.

Condition for final approval: Run a full 2-hour playtest with an experienced and a new operator. If the early coop moment sustains momentum through hour 2, ship it. If players report confusion about sync or verb meanings in the second hour, iterate once more before final.

Summary

Final Call: YES, SHIP THE FINAL SPEC

Resolution Count: 5/5 top-line issues resolved.

Onboarding: Now works. Diegetic tutorial, context-aware hints, verb jargon hidden.

Coop Feel: By minute 20, multiplayer feels essential. The vault puzzle is earned and emotional.

Would I Play: Yes. I’d sit down with Alex tomorrow and play for 2 hours without hesitation. The first 30 minutes hook me. If the middle game sustains, this is a good game.

Absolute path of this report:
/sessions/wonderful-tender-faraday/mnt/kinoshita/docs/gameplay-specs/drafts/playtest-round2-mae.md