Board Game Design Notes

A board games video cross-check is only worth saving when it changes the worksheet, not when it repeats the source list. Start with Watch It Played video archive, then use the attached Board game playtest form to capture the exact visible step that should affect the board games playbooks playbook.

The document fields are reader problem, source checked, claim to verify, decision affected, missing context, and next test. That keeps the post from becoming a video dump: each observation has to land in a source checked, decision affected, or next test row.

boardgame.io documentation is still the primary reference. It decides the baseline claim before any video example gets treated as a rule, template, tracker entry, or checklist item.

boardgame.io is the comparison source. Use it to catch the place where the video demonstration is narrower than the written guide, repository, dataset, API, or document.

boardgame.io source gives the folio a second artifact path. For board games, the source card should say whether it supports a repeatable setting, route, policy, metric, material choice, or workflow step.

Topic labels for the saved note are board-games, board-game-design, playtesting, print-and-play. Keep them because they describe how the worksheet should be filed, not because the post needs extra keywords.

Two sources to open first: boardgame.io/documentation/ and youtube.com/@WatchItPlayed/videos. Use the attached file to record which claim each source supports, which claim remains opinion, and which detail should be removed if nobody can verify it.

A useful reply would replace a weak source, add a missing screen or example, or mark one claim as opinion. That is enough to make the post a living resource instead of a static summary.