Publishing and player links

Publishing freezes the current validated draft as an immutable revision. Existing playtests and player runs keep the version they started with. Further authoring begins by deriving a new draft from a published revision.

Publish a revision

Finish saving the draft and resolve validation blockers.
Test the intended paths in an author-only playtest.
Open Campaign settings or Manage campaign, then choose Publish revision.
Review the new published status and revision number.

If the campaign has a portal card, its player-facing fields are frozen with the revision. A portal preview also remains subject to the Portal Alpha gate.

Manage player links

Open Player links in the campaign workspace. The production link manager lists published campaigns and their runs. A newly created or rotated invite URL is revealed for copying and as a QR code. Store it privately until you intend to distribute it.

Rotating a link replaces its invitation secret; revoking access disables that invitation. Neither action rewrites the published campaign revision. Production player access is a Studio workflow and is not exposed by the current MCP authoring tools.

Continue editing

Choose Edit revision to derive a mutable draft from a published source. The source remains read-only. Duplicate a campaign when you want an independent draft; archive and restore manage library visibility and lifecycle. A campaign with published revisions, playtests, or runs may be protected from deletion and should be archived instead.

Runs and rewards

The Studio header links to Runs for author oversight. Player progress, uploads, choices, and reward claims belong to individual runs. Manual reward delivery is a separate trusted action after a claim; publishing a reward node does not deliver an in-game item automatically.