Deck & Stack Builder
The Deck & Stack Builder lets you assemble reusable groupings of your components:
- A deck is an ordered grouping of cards.
- A token stack is an ordered grouping of tokens.
The key idea: a component isn't locked to a single deck. One card can belong to many decks (and one token to many stacks), and the component is the single source of truth — edit or re-import it once and every deck/stack it's in updates automatically.
You'll find it in the Components page under the Decks & Stacks section.
Building a Deck or Stack
- On the Components page, open Decks & Stacks and click + New Deck or + New Token Stack.
- Give it a name.
- From the left pane, click components to add them. The picker shows only the matching type — cards for decks, tokens for stacks.
- On the right, fine-tune each entry:
- Count (×N): how many copies of that component go into the deck/stack when it spawns in the room.
- Facing: an optional default orientation for that entry (or leave it on Facing to inherit the component's own setting).
- Order: drag-free up/down arrows set the sequence.
- Add again: the same component can appear more than once as separate entries if you want.
- Click Save.
Note
Decks hold only cards and stacks hold only tokens. Editing a card once (its art, name, size, etc.) updates it in every deck that contains it — you never copy a card between decks.
Note
A deck or stack must be uniform in shape — every card in a deck shares the same card mask, and every token in a stack shares the same shape. This keeps piles shuffling, flipping, and stacking cleanly on the table. The picker only offers matching pieces, and an import won't drop a mismatched-shape component into an existing group.
Using Them in the Playtest Room
Saved decks appear in the room sidebar under Cards, and token stacks under Token Stacks. Spawn a whole deck or stack onto the table with one click; copies, order, and facing follow what you set in the Builder. From there they behave exactly like any deck or stack — draw, shuffle, flip, and deal all work normally (see Cards & Decks and Token Stacks).
Tip
Reusing components across games? Add another of your projects as a project dependency in the room — its decks and stacks (built in that project) show up in the sidebar alongside this game's.
Importing Into Decks & Stacks
CSV, JSON, The Game Crafter, and Dextrous imports can place a component into groups automatically:
- Cards: a
deck_namecolumn, ordeck_namesfor multiple decks separated by a pipe (|), e.g.Base Game|Tutorial. - Tokens: a
stack_namescolumn, pipe-separated for multiple stacks.
Importing is idempotent and rename-friendly within a run: re-importing the same rows won't create duplicate memberships, matching groups by name (case-insensitive) and creating any that don't exist. A row with no group name just updates the component and leaves its existing memberships alone.
Note
Import manages its own membership entries. If you've also added the same component to a deck by hand in the Builder, a later import that lists that deck may add its own entry alongside your manual one — both are kept.
Related: Components · Component Types · Cards & Decks · Token Stacks