playtest

Lumina — Playtest

Confirm the game actually runs and looks right. "Compiles" is not "works" — you must observe the running scene.

What to check (from the GDD/plan, or $ARGUMENTS): the core loop is reachable and the scene contains what was promised.

Steps

1. Enter Play mode via the engine MCP (mcp__unity).
2. Capture evidence:
   • A screenshot of the game view (engine MCP viewport/game-view capture).
   • The runtime console log (errors, warnings, and any Debug.Log from systems like the win/lose manager).
3. Read the screenshot yourself. Confirm the expected objects are present and positioned sensibly (e.g. player capsule + the right number of pickups + visible HUD). Don't just trust that play mode started.
4. Exit Play mode.

Output

PLAYTEST: ok | issues
Observed: <what the screenshot shows>
Runtime log: <0 errors / list errors>
Matches plan: <yes / what's missing or wrong>
For the user to judge: <"fun"/feel questions you cannot answer automatically>

Rules

• Report runtime exceptions even if the scene "looks" fine — NullReferenceExceptions in Update are the classic silent failure.
• You can verify working, not fun. Always hand fun/feel/balance back to the user explicitly.
• If play mode throws immediately, capture the stack trace and hand it to the orchestrator's self-correct loop rather than declaring failure.