Skip to main content
Build distribution gets the game into a player’s hands: a short briefing explaining how to install and launch it, plus the URL the download button points at.

Take the guided tour

Turn build distribution on and fill in the download details.

What you need first

  • A build hosted somewhere with a direct link. Userplay points players at your URL; it does not host the binary.
  • A draft or unpublished playtest. The briefing and the URL both lock while the playtest is live.
  • Instructions that assume nothing. Where to extract, what to launch, which prompt to allow. This is the step where players get stuck.

The playbook

1

Turn build distribution on

Open the Config tab and find the Playtest Settings card.
  • Set Build Distribution to Enabled.
  • Click Save.
A Build tab appears.
2

Write the download briefing

Open the Build tab. This is what a player reads before they download anything.It ships pre-filled for your platform and takes headings, paragraphs, images, and video, up to 20 blocks.
Switch to Preview to read it as a player will.

Build distribution

The briefing, the URL, and when each one locks.

Session briefing

The other block editor players read, right before a session starts.
3

Paste the build URL

Below the briefing, set the Build URL and click Save.This is what the player’s download button opens.

Unpublishing a playtest

The only way to change this URL once the playtest is live.

Test a confidential build

Playbook: closing the leak paths around an unannounced link.
4

Preview the step

Click Preview in the editor header and walk to the build step.
The build step only appears once the setting has actually saved, so this doubles as a check that it did.

Previewing a playtest

Walk the build step yourself before players reach it.

Session flow

Where the build step sits in the run a player actually walks.

Players who also need a key

Build distribution runs right before key distribution in the player’s flow. Someone who needs both gets the game first, then the key that unlocks it.

Hand out game keys

Playbook: the step that runs right after this one.

Key distribution

The limits, and how the vault relates to the playtest.

How you know it worked

  • A Build tab appears, and Build Distribution reads Enabled on Config.
  • The preview reaches a build step showing your briefing and a download button, between the join and the key handoff.
  • The download button opens your build URL in a fresh browser, without a login you forgot about.
  • Sessions start arriving in your results. A player who cannot launch the game never reaches a session.

Build distribution

The briefing, the URL, and when each one locks.

Run a survey only playtest

A build and a survey make a complete playtest with nothing recorded and nothing reserved.

Previewing a playtest

Walk the build step yourself before players reach it.

Launch a playtest

Playbook: publish once the build step reads right.