Publish and updates
Draft until you are ready. Publish when you want it in the library.
First publish
- Fix any Studio warnings
- Playtest the important routes, you can share a playtest URL with friends
- Open the Publish tab
- Apply for publishing
Cover, title, and description are what people see before they hit Play.
Version bumps
Stories have an integer version (starts at 1). When you ship meaningful new content, bump it. Players who already played see an Update badge when story.version > progress.playedVersion.
Update notes
On Publish you can post short "what's new" messages (a few hundred characters). Optionally bump version when you post so the badge lights up.
Players with unread notes see a callout above the description. They can dismiss it; the Update badge stays until they actually play the new version. Full history lives in an Updates tab on the story sheet when notes exist.
After you publish
Ink and Studio data live in the shared database. You do not FTP story files to a server. Save in Studio, players get it on the workers automatically.
If someone is mid-play on an old knot, be careful with destructive Ink rewrites. Additive chapters and new side content are safer than rewriting early knots out from under people. Offer a note when a restart is the honest fix.