Skip to main content
Most of a playtest stays editable forever. A handful of settings lock while it is live, and a smaller handful freeze permanently at the first publish. Knowing which is which saves you from unpublishing when you did not have to.

Playbooks

Change a live playtest

Unpublish, edit, republish, and what the reservation does in between.

Reuse a playtest setup

Duplicate rather than edit, when the change is really a new study.

The three tiers

Everything on a playtest sits in exactly one of these.
1

Always editable

Change it in any stage, including while players are mid-session.
2

Locked while published

Unpublish, edit, republish. Reversible, and nothing is lost.
3

Frozen at the first publish

Draft only. Unpublishing does not bring it back.

Always editable

Switching a component toggle on or off never destroys its content. Turn Session Briefing off and the briefing you wrote is still there when you turn it back on.

Locked while published

Unpublish and these open up again. Each carries the studio’s own reason text. Gameplay Recording is the one with a cost attached: it decides the size of the reservation taken at publish, which is why it cannot move while the playtest is live. Session timing is locked for a different reason: it shapes every session a player runs, so it must not change under someone who is midway through the playtest. Every message in that table comes from the server, not just the button state. Scripting against the API or the CLI does not get you around any of them.

Frozen at the first publish

These are draft-only for the rest of the playtest’s life. Unpublishing does not reopen them.
The exact wording differs by control. Screening reads “The screening is locked once a playtest has been published.”; the roster reads “The player list is locked once a playtest has been published. Players can no longer be removed.”

The edit loop

1

Unpublish

Click Unpublish in the editor header and confirm. Unused recorded gameplay sessions come back to your balance at this point.
2

Make the change

The locked tabs and cards open up. Frozen settings stay grey.
3

Republish

Click Publish. The reservation is recalculated against whatever the cap or roster says now, net of what players already used.
The link does not rotate across this cycle, so anything you already shared keeps working. Anyone you added while it was offline can join as soon as it is live again.

When to duplicate a playtest instead

Some settings are permanently locked after a playtest is published. If you need to change one of them, duplicating the playtest is usually the right move.

Duplicate the playtest

Creates a new draft with the same setup, where all draft-only settings are editable again.

Keep results separate

Running a second wave in a new playtest gives you a clean set of submissions, sessions, and results.
Duplicate a playtest when you want to:
  • Rewrite screening or survey questions.
  • Change the session count or playtest type.
  • Run another wave of testing with different requirements.
  • Compare results across two versions of a playtest.
If players are effectively participating in a different study, create a new playtest rather than modifying the old one.

Unpublishing a playtest

What the refund actually returns.

Duplicating a playtest

When the setting you need is frozen.

Publishing a playtest

How the reservation is sized in the first place.

Change a live playtest

Playbook: work out whether you need to unpublish at all.