Two features that matter once a project has been playtested more than once: capturing feedback against specific cards, and being able to go back.
These are deliberately scoped tools, not a whole-project undo. Notes belong to cards. The History panel opened for a selected card snapshots that card's data. Deck details → History snapshots that deck's membership and quantities. Restoring one does not restore layouts, properties or every card in the project.
Notes
The Notes tab in the side panel holds feedback attached to the selected card. The tab carries a count of unresolved notes across the project, and a card with open notes shows a small flag and count on its row number; click that flag to jump to the card's notes.
Scope toggle: This card / All. Start on This card to review one card, switch to All for a project-wide feedback sweep. All shows the number of unresolved notes beside it.
Category chips: BALANCE, WORDING, RULES, ART, BUG, OTHER. A note gets its category when it is flagged. Click a chip to show only that kind, and click it again to show every kind. That's how you triage: hand all the WORDING notes to an editor, all the BALANCE notes to a designer.
Show resolved: a checkbox that brings closed notes back into the list. Off by default, so the panel shows only outstanding work.
The empty state explains where notes come from:
No notes on this card yet. Flag cards during a playtable session to collect feedback here.
That's the intended loop: notes are raised during play on the Playtable, not typed in afterwards from memory. The Data workspace is where you process them.
If you have not used Playtable yet, start with a project and one or more decks, then return here after the session. The Notes panel is the review queue; it is not a separate copy of the card. Editing the card changes the source data, while resolving a note records that the feedback has been handled.
A workflow
- Run a session on the Playtable. Anyone at the table flags a card the moment something feels wrong.
- Afterwards, open Notes with scope set to All and work through the list.
- Fix the card in the spreadsheet.
- Resolve the note.
- Save a version snapshot (below) so you have a marker for "post-playtest-3 balance pass".
The reason to flag in the moment is that "this card felt swingy" is worth writing down within ten seconds of it happening and nearly worthless an hour later.
In the Notes panel, use Resolve when the issue is handled. Resolved notes disappear from the normal list and can be brought back with Show resolved, where Reopen puts one back in the queue. The bin icon deletes a note for good. A note with suggested value changes lists them as old value → new value with an Apply button (Apply all when there are several), which writes those changes to the card before you resolve the note.
Each note shows its category (or Flag for a bare flag with no text), how long ago it was made, and what was written. In the All scope each note sits under the name of its card. A note flagged during a recorded session also carries a during play · open in replay link, which opens the recording at the moment the card was flagged. Notes can include a picture of the table at that moment (click it to see it full size, titled Board at flag time) and a line of game state, such as the card's zone and hand sizes.
Version history
On the Card Details tab, the clock icon at the panel's top-right (its tooltip reads Show version history) opens the snapshot panel for the selected card. You can also right-click a card's row and choose Version history. While it is open it follows the row you select; with no row selected it reads Select a card to view its history. Click the icon again to go back to the preview.
- Save snapshot captures the current state. Type an optional label such as
post-playtest-3 balance passand click Save or pressEnter. - Filter narrows the snapshot list.
- The list, or
No snapshots yetif you haven't taken one. Each entry shows its version number, a badge for why it was made (Snapshot, Status, Pre-import, Pre-restore, Pre-AI edit), how long ago, and its label if it has one.
The list shows your manual snapshots by default, and they aren't the only safety net: ShuffleKit also captures automatic versions before imports (including an import that updates existing cards), before restores and before AI edits, and records status changes. Open Filter to see those too: tick All versions, or pick the kinds you want (Snapshots, Status changes, Pre-import, Pre-restore, Pre-AI edit). A number on the button counts the kinds ticked.
To go back, select a version in the list and review the preview underneath it. Use Data preview for a card or Deck composition for a deck. Then choose Restore this version and confirm with Restore. Restoring overwrites that card or deck, but ShuffleKit creates a backup snapshot before it does so. With the keyboard, Tab to a version and press Enter or Space to select it. Use Filter → All versions when the version you need was created automatically.
When to snapshot
Manual snapshots are for the moments you decide matter. Each one covers a single card, or a single deck's composition:
- Before a balance pass on a card. So you can compare what changed and, if the pass makes things worse, get back. (Imports and AI edits already snapshot automatically.)
- At each playtest build. Save a deck snapshot from Deck details → History, labelled for the session, so you know exactly which cards and quantities were on the table.
Snapshots don't cover deletion. A card's history is deleted with the card, and restoring a card doesn't bring back a deleted column. Layouts have no version history here either. Before deleting cards or a column, export a CSV (below), or archive the cards instead of deleting them.
Deck history
Decks keep their own version history. Open the deck's Deck details… dialog and switch to the History tab. Selecting a version shows its Deck composition, the cards and quantities the deck held then. See Decks.
The belt-and-braces backup
Snapshots live inside ShuffleKit. For card data you'd be upset to lose, also take a periodic File → All as CSV or All as JSON and keep the file somewhere else. Run it from All cards with the search box empty and no status filter: despite the name, it exports the rows the sheet is showing. Both carry your card data, one row per card with a ShuffleKit ID column and its property values, so a later import can update the same cards. They don't include status, layouts, decks or notes.
See Import & Export.
