Welcome to Gamepiece Studio
Gamepiece Studio keeps the pieces of a tabletop game together: the layouts you design, the words and numbers that change from card to card, the artwork you use, and the files you send to a printer or playtest group.
You do not need to prepare a complete game before starting. A rough list of cards, a folder of artwork, or a single paper prototype is enough.
The four parts of a project
- A project is the home for one game. Some older URLs and file names call a project a “game”; they mean the same thing.
- Designs are reusable layouts for cards, boards, tokens, rules sheets, and other pieces.
- Datasets hold the content that changes between pieces, such as a card name, cost, image, or rules text.
- Exports turn the current state of your project into images or print-ready sheets.
Your Images, Variables, and Fonts libraries are shared by every design inside the project. The Scratch Pad gives the team a looser place to arrange ideas before committing them to a final design.
A good first path
For a small card deck:
- Create a project.
- Build one card layout.
- Create a dataset with a row for each card.
- Bind text and image layers to dataset columns.
- Preview and check the deck.
- Export a small playtest before preparing the full print run.
Make two or three representative cards first: the shortest, the longest, and the most visually complex. They reveal layout problems sooner than a complete data import.
Saving and reconnecting
Studio saves as you work. A green Saved state means the latest changes have reached the project. If the connection drops, keep the tab open and wait for the reconnect state to clear before closing it. The Designer can offer a recovery copy when a local edit and the saved project no longer agree; read both choices before replacing either version.
Exports use a snapshot taken when the export starts. Changes made after that point belong to the next export, which keeps a long export predictable.