Game versions
Log each numbered version of a game with its date and changes, so playtest feedback always points at the right build.
Last reviewed October 11, 2026
Versions is a game's change history: a numbered entry for each build, with the date and what changed. When a playtester asks "which version did we play?", this is where the answer lives.
What this page helps you do
- Log a new version with a number, a date and a description of the changes.
- Edit or delete an entry.
- Pick the version a playtest was played on.
You'll start from a game's page: click Versions in the header.
Open Version Tracking
Click the Versions badge next to the game title, or the Versions button under the description. A side panel titled Version Tracking opens with the form at the top and the list below it.
Helpful details
- Key areas: the form is Log New Game Version; the list below it is Your Game's Design Journey.
- What you can do: keep the panel open while you read the Rules or Components tab to describe what changed.
- Good to know: the badge is visible on every tab, so the version history is one click away wherever you are on the game.
Log a new version
Fill in Version, pick a Date, describe the Changes, and click Add version.
Helpful details
- Key areas: Version is a number, for example 1.0, 2.5 or 0.7 (the placeholder says "e.g. 2.5"). Names like "Convention build" do not fit here; put them in Changes.
- What you can do: backdate the entry if you are catching up on history. The date picker opens with Pick a date.
- Good to know: write the change and the reason: "Scoring track cut from 50 to 40; games ran 20 minutes too long." Future you, and publishers asking "what changed since we saw it?", will thank you.
Edit or delete a version
In the list, click Edit on an entry. The Edit Version dialog lets you change the number, date and changes, then Save. The same dialog has Delete, which asks you to confirm Delete Version.
Helpful details
- Key areas: deleting is permanent and cannot be undone.
- What you can do: fix a wrong date or merge two entries by editing one and deleting the other.
- Good to know: the game's version list is copied along when you copy the game to another team (tick Version History in the copy dialog).
Link versions to playtests
When you log a playtest, the form has a Version field that lists the versions you logged here. Pick the one that was on the table.
Helpful details
- Key areas: this is the main reason to keep versions: feedback stays tied to the build it was about.
- What you can do: when you review results, filter or compare by version to see whether a change worked.
- Good to know: see Log a playtest. If the list shows "No versions available", add a version here first.
Tips & common questions
How often should I bump the version? Whenever the game on the table is meaningfully different: a balance change, a new mechanism, a removed component. Typo fixes do not need one.
Can I use dates or names instead of numbers? The field accepts numbers only. Use a scheme like 0.1, 0.2, 1.0 and put names and dates in Changes.
Can I keep a snapshot of the rules per version? Download the rules as a PDF when you log a version (Rules tab, Download > Download PDF) and keep it with your files. See Drafting rules.
Can two people work on different branches? Versions are one straight line per game. For an experimental fork, copy the game to another team or keep the variant in a second rule document and note it in Changes.