#board-game-design

A useful board-game starter pack should include one engine for formalizing turn logic, one prototype platform, one rules-teaching channel, and one set of component-layout references. That combination helps a designer move from notebook enthusiasm to a game that can survive contact with other humans. 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.

Read:
- boardgame.io: boardgame.io/
A smart reference when readers want to formalize turn structure and game state clearly.
- 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 video tutorials: kb.tabletopsimulator.com/getting-started/vide...
A good bridge for readers who learn prototype workflows better through motion than prose.

Documents and downloadable guides:
- boardgame.io documentation: boardgame.io/documentation/
Worth saving once a designer wants to model phases, moves, and turn order explicitly.
- 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.
- MDA: A Formal Approach to Game Design and Game Research: users.cs.northwestern.edu/~hunicke/MDA.pdf
A classic PDF that still helps designers separate mechanics, dynamics, and aesthetics clearly.
- BoardGameGeek design forums: boardgamegeek.com/forum/26/bgg/board-game-design
One of the longest-running public archives of practical design questions, diaries, and playtest discussion.

Watch:
- Watch It Played video archive: youtube.com/@WatchItPlayed/videos
A durable library for seeing how rules explanations land when clarity actually matters.
- Board Game Design Lab: youtube.com/@BoardGameDesignLab/videos
Interviews and practical episodes that stay close to prototyping, pitching, and playtesting.

Build or inspect:
- boardgame.io source: github.com/boardgameio/boardgame.io
A readable open-source engine for state management, phases, turns, and multiplayer logic.

Turn scaffold:

export const turnOrder = {
  first: () => 0,
  next: ({ currentPlayer, numPlayers }: { currentPlayer: number; numPlayers: number }) => {
    return (currentPlayer + 1) % numPlayers
  },
}

export const moves = {
  draftCard: (G: { hands: string[][] }, ctx: { currentPlayer: string }, cardId: string) => {
    G.hands[Number(ctx.currentPlayer)].push(cardId)
  },
}

A realistic first month in board games is not about chasing total coverage. 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. A common mistake is polishing components before the decision space is stable. Another is collecting opinions after a playtest without preserving the exact moment where a player hesitated, misunderstood, or disengaged, which is the part the next prototype actually needs.

Three useful starting moves:
1. Write the shortest rules explanation you can, then build the roughest prototype that can test it.
2. Run playtests that record hesitation, confusion, and timing, not just general reactions after the session.
3. Revise the prototype, rules, and component layout together so the next table teaches you something specific.

If I were starting this week, I would open:
- boardgame.io: boardgame.io/
A smart reference when readers want to formalize turn structure and game state clearly.
- Tabletop Simulator custom deck guide: kb.tabletopsimulator.com/custom-content/custo...
Practical documentation for moving prototype cards and components into a usable test table.
- boardgame.io documentation: boardgame.io/documentation/
Worth saving once a designer wants to model phases, moves, and turn order explicitly.
- Watch It Played video archive: youtube.com/@WatchItPlayed/videos
A durable library for seeing how rules explanations land when clarity actually matters.

A useful board-game starter pack should include one engine for formalizing turn logic, one prototype platform, one rules-teaching channel, and one set of component-layout references. That combination helps a designer move from notebook enthusiasm to a game that can survive contact with other humans.

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 good debates are about how much luck a design should absorb, when simulation helps versus distracts, and whether elegance means fewer rules or clearer consequences. Those conversations are useful when they are grounded in what players feel around the table, not just the designer's intention.

The tools that keep proving useful usually support turn and state modeling tools, digital prototype and playtest platforms, and component layout and print-and-play references without making the underlying work harder to understand. When you bookmark something, write down why it earned the slot.

Three sources worth opening side by side:
- boardgame.io: boardgame.io/
A smart reference when readers want to formalize turn structure and game state clearly.
- boardgame.io documentation: boardgame.io/documentation/
Worth saving once a designer wants to model phases, moves, and turn order explicitly.
- boardgame.io source: github.com/boardgameio/boardgame.io
A readable open-source engine for state management, phases, turns, and multiplayer logic.
- Watch It Played video archive: youtube.com/@WatchItPlayed/videos
A durable library for seeing how rules explanations land when clarity actually matters.

Good board-game work usually feels less like a lightning-bolt idea and more like disciplined iteration around player friction. The best public resources in this space make prototype rules, component design, and playtest feedback visible so readers can see how a game becomes clearer over time.

A common mistake is polishing components before the decision space is stable. Another is collecting opinions after a playtest without preserving the exact moment where a player hesitated, misunderstood, or disengaged, which is the part the next prototype actually needs. 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.

If you want a cleaner start, build your notes around board-games, board-game-design, and the real examples behind board games improve fastest when designers save the exact friction points that showed up at the table.. Those records will outlast the summary you write about them later.

Open alongside this question:
- boardgame.io: boardgame.io/
A smart reference when readers want to formalize turn structure and game state clearly.
- boardgame.io documentation: boardgame.io/documentation/
Worth saving once a designer wants to model phases, moves, and turn order explicitly.
- Watch It Played video archive: youtube.com/@WatchItPlayed/videos
A durable library for seeing how rules explanations land when clarity actually matters.