What you need first
- A build that gives players something new on their second visit.
- A session count you have the balance for. The reservation is your player cap (or roster size) multiplied by the count, so check the Credits card under Settings > Billing before you start.
- Something for players to play: a build URL, a stock of keys, or a game they already own.
The playbook
1
Create the draft as Multi Session
Open Playtests in the sidebar.
- Click Create playtest.
- Choose the Multi Session card, then click Continue.
- Set the name, the Minimum Session Duration, and a Session Cooldown.
- Click Save Draft.
2
Set the session count
On the Playtest tab, click the Number of sessions card and drag the slider between 2 and 6.
3
Set the timing
The Minimum session duration and Session cooldown cards sit on the same Playtest tab. Set each one once, and it applies to every session.
The cooldown forces the gap between visits. Clear it to let a player start the next session right away.
Playtest types
Where the 2 to 6 range comes from, and what each type fixes.
Run a longitudinal study
Playbook: the same shape with the gap measured in days.
4
Decide who gets in
Open the Playtest Access card on Overview and set Access and Player Count.
5
Give players something to play
On the Config tab, in the Playtest Settings card:
- Set Build Distribution or Key Distribution to Enabled.
- Click Save.
A key is handed over once, on the player’s first session, not once per visit.
Builds
The URL field, the platform notes, and what players see at handoff.
Distribute a build
Playbook: the briefing and URL behind the build step.
6
Brief each session separately
On Config, set Session Briefing and Session Objectives to Enabled, then click Save.
Both tabs gain a session picker (Session 1, Session 2, and so on). Use it to point session 2 somewhere session 1 never went.
Session briefing
What a briefing can hold, and why it never freezes at publish.
Brief players and set objectives
Playbook: write a brief that points each session somewhere new.
7
Write a survey per session
On Config, set Session Survey to Enabled, then click Save.The Survey tab gets the same session picker, plus a per-session switch in its … menu.
You can ask after session 1 and skip after session 2.
Post session survey
The block editor, the per session switch, and what freezes at publish.
Write survey questions
Playbook: word a question so the answer still means something on visit three.
8
Preview, then publish
Click Preview in the editor header, then Publish.
Preview walks session 1 as the representative case. Publishing reserves cap (or roster) times session count in one go.
How you know it worked
- Your playtest reads as Multi Session with the count you set, for example 3 sessions.
- The Briefing, Objectives, and Survey tabs each show a session picker with one entry per session number.
- Your recording balance drops by cap times session count when you publish. A cap of 50 across 3 sessions takes 150.
- The results Sessions tab fills with more than one session per player. A player’s second session only appears after the cooldown elapses.
Related articles
Session timing
Every cooldown option and when the cards lock.
Run a longitudinal study
Uses the same session range but with the cooldown set in days.
Check what a playtest will cost
Playbook: size the run when a multiplied reservation exceeds your balance.
Hand out game keys
Playbook: a key is handed over once, on the first session, not every visit.