Skip to main content
Key distribution hands each player a key as they join, drawn from a vault belonging to this playtest alone. That vault is created by the first batch of keys you load.

Take the guided tour

Turn key distribution on and load the first batch of keys.

What you need first

  • Keys in hand. A vault holds up to 1,000, and a single import takes up to 300 at a time.
  • A decision on key type. A vault started from a playtest defaults to the Steam Playtest variant. A custom key is any code you issue yourself, up to 200 characters.
  • A player cap or a roster so you know how many keys to load.

The playbook

1

Turn key distribution on

Open the Config tab and find the Playtest Settings card.
  • Set Key Distribution to Enabled.
  • Click Save.
A Keys tab appears with an empty table.
2

Load the keys

On the Keys tab, click Add keys, then pick how the keys come in.
Type or paste keys directly, one per line.
Load two to three times your player cap. A late joiner who shows up after the vault runs dry cannot continue. Duplicates are skipped, so over-loading is safe.

Stock a key vault

Playbook: loading keys and picking the right Steam variant.

Migrate your key inventory

Playbook: bring a pile from elsewhere over in 300-key batches.
3

Change the key type if it is not a Steam key

The first batch creates the vault as a Steam vault.
  • Open the overflow menu on the Keys header.
  • Choose Change key type, and switch it to a custom key.

Keys

Every key type, Steam variant, and status a key can hold.

Hand out DLC or bundle keys

Playbook: when the key grants something other than the base game.
4

Preview the handoff

Click Preview in the editor header and walk to the key step.
It lands after the build step and before the session briefing. The player gets the game, then the key that unlocks it, then their instructions.

Preview the flow

What preview covers, and the stages it silently skips.

Session flow

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

Watching the keys move

Every key carries a status, and status only moves forward.

When you want a custom vault instead

The vault created here belongs to this one playtest. It has no redeem link and no screening of its own, since it inherits the playtest’s. If the keys are a studio-level inventory, build a custom vault from Vault in the sidebar instead. A custom vault:
  • Is reusable across every playtest you run.
  • Gets its own redeem link and its own screening.
  • Can assign keys straight to a player group, with no playtest involved.
The kind is fixed for the life of the vault, so choose before you load 1,000 keys into the wrong one.

Key vaults

System vaults against custom vaults, and what each one can do.

Redeem links

The public link only a custom vault can carry.

How you know it worked

  • A Keys tab appears, and Key Distribution reads Enabled on Config.
  • Userplay stops warning you about key supply once the vault is deep enough for your cap.
  • The preview reaches a key step after the build step and before the briefing.
  • Once players start joining, keys move from Available to Assigned to Redeemed, and the available count stays well clear of zero.

Key distribution

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

Stock a key vault

Walks through loading keys and picking the right Steam variant.

Give keys away with a redeem link

The custom-vault path, outside any playtest.

Keys

Every key type, Steam variant, and status a key can hold.