The Versions tab is where you keep a running record of how a game has evolved, v0.1, v0.2, v0.7, v1.0, etc., with notes on what changed at each step.

What this page helps you do

Bump a game to a new version.
Record what changed in plain language.
Look back at what v0.6 vs v0.7 actually changed when a playtester asks.

Open the Versions tab

On the game's page, click Versions. You see a chronological list of every version you've recorded.

Each entry shows:

Version label (v0.1, v0.7, v1.0, "Convention demo build").
Date the version was created.
Notes about what changed.

Add a new version

Click Add version. Fill in:

Version label: your numbering convention. Common patterns: Semantic-ish (v0.1, v0.2..., v1.0): increments imply scale of change. Date-based (2026-04-15): less ambiguity but harder to talk about casually. Named (Pre-Gen-Con build, Print-and-play 2): readable but inconsistent.
Date: usually today; can backdate if you're recording history.
Notes: what changed since the previous version, in plain language.

Save. The version appears at the top of the list.

What to write in notes

Be specific. Useful note styles:

v0.7, Reduced scoring track from 50 to 40. Added "treasure chest" action card. Removed "Royal Decree" mechanic, it slowed the midgame too much.

Bad note styles:

v0.7, Various tweaks.

The notes are for future-you trying to remember why you made a decision six months from now, and for collaborators or publishers asking "what changed since the version we saw?"

Linking versions to playtests

When you set up a playtest (see Set up a playtest), one of the fields is Game version. Pick the right version from the dropdown, that's the version playtesters tested. Later, when reviewing results, you know exactly which version the feedback applies to.

This is the main reason version tracking is worth doing: it disambiguates playtest feedback over time.

Editing or removing a version

In a version's menu, you can Edit to update the label, date, or notes, or Delete to remove it. Deletion is permanent.

If a playtest was linked to a deleted version, the link reverts to a free-text version label so the historical record isn't broken.

Tips & common questions

Should I bump version every change? No. Bump when the change is significant enough that you'd want to call it out, a balance change, a new mechanic, a UI overhaul. Small typo fixes don't need a version bump.

What about versioning the rules separately? The Rules editor itself doesn't expose per-version snapshots in the UI. For now, export the Rules to PDF when you bump a version, the PDF preserves a snapshot.

Can two people work on different "branches" of a game? Game versions are linear (one timeline). For experimental forks, copy the game (see Copy or archive a game) and version each independently.

Can I rename a version after the fact? Yes, edit the version's label.

What happens if I delete the most recent version? The previous one becomes the current. Anything that referenced the deleted version (playtests etc.) reverts to free-text.