Validation and playtests

Validation gives authors actionable findings while they edit. A playtest then freezes one validated draft version for an author-only run.

Read the validation tray

The campaign route and each mission graph show findings. Open a finding to focus the affected object. Common blockers include an unreachable node, an exit without a destination, a broken resource reference, a missing required setting, or an incomplete route to an ending.

The canvas rejects some invalid connections immediately, including cycles and incompatible ports. Other findings can remain on a draft while you work. Resolve every blocking finding before creating a ready playtest or publishing.

Create a playtest

Wait for pending changes to save. Choose Test campaign in the workspace or campaign settings. A successful request creates a snapshot of the exact draft version and opens an administrator playtest workspace. It does not publish a revision or create a production player invite.

If you change the draft afterward, the earlier playtest becomes stale relative to the draft. Create a new playtest to check the new version; the old snapshot stays unchanged.

Inspect a run

The playtest workspace pairs a player-facing run with an author inspector. The inspector can show available and completed nodes, choices, attempts, uploads, and an event journal. Object links return to the corresponding mission graph so you can correct the draft quickly.

Play through important branches, incorrect and correct answers, upload requirements, mission transitions, and endings. The uploaded image's storage status is observable; the system does not automatically decide whether its visual contents satisfy a puzzle.

MCP equivalents

An MCP client can call studio_validate_campaign, studio_preview_node, and studio_create_playtest. Previewing a node does not create or advance a run. See MCP tool reference.