Playtesting Your Design
Start a playtest on Main or on a workspace and take actions one at a time as a new player would.
Playtesting Your Design
Playtest lets you play your design as a brand-new player, one action at a time, and see exactly what each action changes — the quickest way to check that your systems, custom operations and events behave the way you intended. Open it from the Playtest tab in the header.
What Playtest Plays
Playtest plays your saved design as a brand-new player. Nothing is deployed; the run's actions are recorded in the environment you choose. What you can play depends on your project's work mode:
- When you edit Main directly, Playtest plays Main as you see it, or one of Main's earlier versions.
- When your project uses workspaces, Playtest plays Main as it was merged — "Playtest runs a commit on main — not your unsaved edits, and not a workspace." — or, while you're in a workspace, that workspace's saved changes. Merge your workspace to play its changes from Main.
If your project uses workspaces, you're on Main and nothing has been merged into it yet, Playtest shows "There is nothing to play yet" — merge a workspace and try again.
Step-by-Step Breakdown
Step 1: Open the Playtest Tab
Click Playtest in the header. The start screen reads Play your design.
Step 2: Choose What to Play
The Playing picker chooses what to play.
- When you edit Main directly, Main · current changes is listed first and selected for you. It plays Main as you see it. When you press Start, Leap checks Main and adds your latest saved changes to Main's list below, as Changes on main; anything that needs fixing is listed there, with how to fix it. Unsaved edits are not included.
- In a workspace, This workspace is listed first and selected for you. It plays your saved changes: they are checked when you press Start, and anything that needs fixing is listed there, with how to fix it.
- Main's history, under Main, lists every merge into Main, numbered in order: Main #3 (latest), Main #2, and so on. Each also shows, when it happened in this browser, the workspace it was merged from — or, if you edit Main directly, the version it was made for, such as Version 1.0.0, or Changes on main when a playtest added it — and otherwise how many elements it changed, followed by when it was merged.
The Environment picker beside it chooses the environment the run logs in to: the one Build & Deploy deploys to, unless you pick another. The run's actions are recorded there, and show in Analyse.
While a playtest runs, both pickers are locked to what it started on. To play something else, click End session first. If the run plays a version of Main while you're in a workspace, the page says so and offers End this run and play the workspace; when you edit Main directly, it offers End this run and play the current changes.
Step 3: Start a Playtest
Click Start a playtest. You begin as a brand-new player, so anything that happens to every new player has already happened — the GameSetup system, for example, has already run.
Step 4: Take an Action
The Next action panel lists every action a player could take:
- custom operations that are Callable by game clients, marked Custom operation;
- events that are Callable by game clients, marked Event · drives state machines;
- achievements your game can unlock directly.
The actions are grouped by whether they can run right now:
- Available — the action's conditions pass. As the panel's help puts it, "Available" means the action's condition holds — not that it will do what you expect.
- Blocked — the action's conditions don't pass. You can still play it, to see it refused.
- Undecidable — "We could not evaluate the condition from the client. The runtime may still accept these."
Click an action to play it. When an action moves a system, it shows the system's current state and where it would go, e.g. Main Quest · Chapter 1 → Chapter 2. Hover it to see the system's map and which exits would be taken — this is a prediction: the changes the action actually made appear in the next turn.
Step 5: Keep Playing or Start Over
Keep taking actions to play through your design. Start over begins again as a new player, and End session returns to the start screen. Neither asks for confirmation.
Tip: Your playtest stays open while you switch to other tabs and back, but reloading the page ends it.
Next Steps
Continue to Reading a Playtest to understand what each turn changed.