Board Games Lab

A dependable board-game workflow begins with a short rules explanation, a prototype that can survive being misunderstood, and a playtest log that records where the table drifted or stalled. You do not need art first; you need a version that teaches you what players are actually doing.

boardgame.io is useful because it forces you to think clearly about turns, state, and legal moves, while Tabletop Simulator is valuable because it shortens the distance between a rules tweak and another test session. Together they help designers move between idea, simulation, and table behavior. The metrics I care about are how quickly players internalize the turn, how often a rules explanation gets interrupted for clarification, and whether a playtest points to one fixable bottleneck rather than a vague sense that the game did not sing. Those are the signals that help a design improve.

A grounded version usually starts with three moves: Write the shortest rules explanation you can, then build the roughest prototype that can test it.; Run playtests that record hesitation, confusion, and timing, not just general reactions after the session.; and Revise the prototype, rules, and component layout together so the next table teaches you something specific.. Save the version that survived real constraints, not the one that only sounded elegant in a planning doc.

Useful operating references:
- Tabletop Simulator custom deck guide: kb.tabletopsimulator.com/custom-content/custo...
Practical documentation for moving prototype cards and components into a usable test table.
- Tabletop Simulator custom deck reference: kb.tabletopsimulator.com/custom-content/custo...
A practical build note for anyone turning printable components into a shared playtest table.
- boardgame.io source: github.com/boardgameio/boardgame.io
A readable open-source engine for state management, phases, turns, and multiplayer logic.