"Supports 6" Isn't the Same as "Good at 6"

Box copy has exactly one way to describe player count: a min/max range, printed once, never varying by how good the game actually is at any specific number inside it. That's a real limitation, and it's worth understanding precisely how a fit score fixes it — not as a vague “trust us,” but as an actual formula you can walk through by hand.

The formula, in plain terms

Our Player-Count Matcher scores every game in its curated list against whatever headcount you enter, using a simple rule: if your number falls outside the game's published min/max, it's excluded entirely — a score of zero, not shown at all. If your number falls inside the range, the game starts at a baseline and gets scored based on distance from its known best count(s): a perfect 100 if your number matches one of them exactly, and 20 points off for every step away from the nearest one, down to a floor of 40 so that anything technically playable never reads as a failing grade.

That's the entire mechanism. No hidden weighting, no fuzzy matching — just three plain rules: out of range is excluded, on a best count is 100, and everything else steps down predictably from there. It's deliberately simple enough to check by hand against any curated game's own listed min, max, and best counts, rather than a black box you have to take on faith.

Six players, worked by hand

Run six players through the curated list and the split is immediate. Codenames, Coup, and Dixit all land at a perfect 100 — six is a published best count for all three. 7 Wonders, whose best counts are four and five, still covers six comfortably inside its three-to-seven range, but sits one step away from its nearest best count, landing at 80. Catan doesn't appear in the results for six at all — its published range tops out at four without an expansion, so six is simply outside what the base game supports, not a low score but a real exclusion.

Three genuinely different outcomes, from the same headcount, depending entirely on which specific game you're asking about — which is exactly the nuance a min/max range alone throws away.

Two players, worked by hand

The picture looks completely different at the other end of the range. At two players, Azul is the only curated game that lands on a perfect 100 — two is one of its published best counts. A wide middle tier scores 80: Carcassonne, Pandemic, Splendor, Ticket to Ride, and Wingspan are all playable at two and one step away from their own best counts. Sushi Go! lands at 60, two steps off. And Codenames and Coup, both built around a socially rich table, drop to the 40 floor at two players — still technically playable (both list 2 as their minimum), but about as far from their intended experience as the scoring allows without excluding them outright.

That floor of 40 is doing real work here. Codenames and Coup at two players aren't broken — they'll run — but a fit score that let them show up at 100 right alongside Azul would be actively misleading. Forty communicates “this will technically work, but it's not what the game is for” in a way a min/max range never could.

Five players, the busiest middle ground

Five players lands in the thick of it: 7 Wonders and Coup both hit 100 (five is a published best count for each), while Codenames, Dixit, Sushi Go!, and Ticket to Ride all land at 80, one step off their own best counts. Carcassonne and Wingspan drop further to 60. No game gets excluded outright at five — it's inside every curated game's range — but the spread from 100 down to 60 still tells a meaningful story about which of those playable options is actually the strongest choice for tonight.

Reading a score honestly

A few practical rules follow directly from how the formula works:

• Treat 100 as a genuine recommendation, not just a pass. It means your headcount is one of the specific counts the game is known for, not merely inside the legal range.
• Treat 80 as a real option, not a compromise you should feel bad about. One step off a best count is still a normal, enjoyable way to play almost any of these games — the gap between 100 and 80 is much smaller in practice than it looks on paper.
• Treat 40 as a genuine warning, not a false positive. A game floored at 40 for your headcount is telling you it'll technically run but probably won't shine — worth having a backup in mind rather than committing the whole evening to it.
• Treat an absence as a hard no, not a low score. A game missing from your results at a given headcount isn't scoring poorly — it's outside the published range entirely, the one case the tool won't soften with a number at all.

Choosing between two games that both score 80

The formula only outputs one number, but a tie in score doesn't mean the two games are equally good choices — it means they're equally distant from their own best count, which is a narrower claim. At five players, Codenames and Dixit both land at 80. Codenames' range runs two to eight, so five sits comfortably in the middle of a wide window; Dixit's range runs three to six, so five sits right at the edge of a much narrower one. Both are one step from their respective best counts, but Codenames has more room on either side of five to still feel like itself, while Dixit is closer to its own boundary. When two scores tie, checking how wide the underlying range is — not just the distance from the best count — is a useful tiebreaker the raw number doesn't surface on its own.

A similar logic applies when comparing an 80 to a 60. The gap between them is real, but it's worth remembering both numbers describe "still playable, still a legitimate choice" — the practical difference between an 80 and a 60 is usually smaller than the difference between either of them and a 40, since the floor exists specifically to flag the count where a game structurally struggles rather than just missing its ideal by one step.

A few myths about player count worth retiring

• "More players is always more fun." Not for every game — games with real downtime between turns or tight resource competition often get worse, not better, as headcount climbs past their best range, which is exactly why a fit score can drop even for headcounts still inside the published max.
• "A game's minimum player count is its true best solo-adjacent experience." A published minimum is usually the floor the mechanics can technically support, not a recommendation — plenty of games list a minimum of two while being widely regarded as best at three or four instead.
• "If the box says it supports a count, any group that size will have a good time." This is the core misconception this whole piece is built around: supporting a count and being good at it are different claims, and only one of them is printed on the box in a way most people will notice.

Applying the same logic to a game that isn't in the list

Our curated list is deliberately small — a set of widely-owned titles, not an exhaustive database — so the exact same three-rule logic is worth applying by hand to anything on your own shelf that isn't included. Check the box's min/max first (the hard boundary), then ask separately whether your headcount is a count the game is specifically known for or just one it tolerates — often answerable from the box's own marketing copy, a quick note in the rulebook, or general reputation among people who own it. The formula above isn't unique to our tool; it's a genuinely reusable way to think about any game's player-count fit, curated list or not.

Why this matters more than it seems

A player-count mismatch is one of the most common, most avoidable reasons a game night underperforms. A game landing at 40 for tonight's headcount can still be fun, but it's rarely anyone's best possible choice, and when a better-fitting option exists on the same shelf, reaching for it first tends to produce a noticeably better night with zero extra cost. Checking fit before checking anything else — genre, theme, how long the box has been unopened — is a small habit that consistently pays off. Our Game-Night Planning Reference shows this same best-fit logic across several common headcounts side by side, which is a fast way to see where the curated list's strongest options sit before you even open the matcher.

The next time you're standing in front of a shelf trying to decide what to bring to the table, it's worth resisting the pull of whatever game is most visually appealing or most recently played, and starting instead from the one question a fit score answers directly: out of everything on this shelf, what's genuinely built for tonight's exact headcount, not just technically able to survive it.