Game versions and release channels
Working files, playable versions, and release channels answer different questions.
| Item | What it identifies |
|---|---|
| Working files | The saved draft you are editing and previewing. |
| Commit | A built snapshot that can be played. |
| Private playtest | A committed version available to permitted game members. |
| Public playtest | The committed version chosen for public testing. |
| Published release | The version available through the published channel. |
| Framework version | The API contract used to build and run the game. |
Which changes players receive
Saving a file does not update a running match. A match keeps the commit it started with. Changing a public playtest's selected version affects new matches, while ongoing matches continue with their original version.
Use Commit a game version to build a snapshot, then Open a public playtest to choose its public availability. Framework upgrades are a separate technical task.