Reading a Playtest

Read the player state, the run history and the changes each action made during a playtest.

Reading a Playtest

As you play, Playtest records every action and what it changed. This guide covers the three parts of the Playtest screen: the run on the left, the turn details and player state in the middle, and the next actions on the right.

The Header

Across the top, the header shows the merge you're playing, the player's profile number with how many turns have been played, and the Start over and End session buttons.

The Run

Run lists every turn in order. The first is always New player; each action you play adds a turn, and the latest is marked now. Each turn shows how it went:

• Ran — the action was accepted and applied.
• Refused — the action was refused, for example because its conditions didn't pass. Nothing changed.
• Unknown — the request failed after it may already have run. Playtest doesn't send it again, and shows the state as it found it afterwards.
• Not sent — the action was never sent.

Turn Details

Select a turn in the run to see what it changed:

• the first turn reads "A new player profile was created";
• each changed value is shown from old to new, e.g. 25 → 15 (−10);
• each system that moved is shown from state to state, e.g. Chapter 1 → Chapter 2.

A turn that ran but changed nothing is a valid result — for example, firing an event no state was waiting for. Select an earlier turn to look back at it, and click Back to now to return to the latest one.

Player State

Player state shows everything the player has right now: every resource, flag and achievement by its slug, and the state each system is in, by name. Values the player has never changed show the value they start with, followed by an asterisk (*). Hover the value to read "never written — showing the model default".

Turn on Changed only to show just the values the selected turn changed.

When Something Goes Wrong

If Playtest can't continue, it tells you why:

• "Couldn't reach the Leap runtime. Check your connection and try again."
• "This playtest session has ended. Start a new one to keep playing."
• "The player profile behind this session no longer exists."
• "That commit is not available to play."

In each case, Start over — or End session and then Start a playtest — begins a fresh playtest.

Next Steps

Continue to Versions and Deployments to ship your design.