🏆 2026-11-15 | Game Stats on the Victory Screen

🧑💻 Author’s Note
👋 Hello! Issue #49 asks what interesting statistics could make Domination’s victory, defeat, or tie screen more informative. This is a research and design proposal only; it does not implement a results screen.
🔎 What the Game Can Reliably Show
🔎 The current end screen renders the HUD and a short result label. A result is either one winning player or a set of tied players. The game state still contains every player’s cards, and scoring already includes cards across hand, deck, play, discard, and other in-progress piles. That makes final scores, score margins, and score-by-card breakdowns natural candidates for a results summary.
📚 The relevant code is Game, Player, Result, and the current result rendering.
⚠️ Some appealing counters cannot be reconstructed reliably from the current state. The room’s game log is capped at 250 entries and 100,000 encoded characters, and it does not log phase-ending plays. Counting its entries would therefore undercount long games and cannot reliably give turns played. Accurate totals for turns, buys, cards played, or trashing would need to be recorded as the game runs, rather than inferred from the bounded log. See Chat.
📖 What the Research Suggests
🧭 A useful stats screen should answer a player question, not simply display every counter the app can collect. The game analytics guide recommends starting with a decision or question and then choosing the event model and metric to answer it. For a single end-of-game screen, that points to clear, directly explainable measures: who won, by how much, and which cards contributed to each score.
🃏 Dominion players also analyze logs and card-level outcomes across many games; a Dominion log-statistics discussion illustrates how card-level counts and win-rate comparisons can prompt strategy questions. Those aggregate statistics need many games and careful interpretation, though. They are a different product from an immediate per-game recap, where a “best card” award or a causal claim about why someone won could overstate what one match proves.
💡 Proposed Stats
- 🥇 Final standings and point margin: List every player, final VP, rank, and the difference from the winner. Tied players share first place; the other players are shown as not winning, rather than presenting a tie as a defeat for everyone.
- 🧮 Score breakdown by card: Show each player’s scoring cards, counts, and VP contribution, including negative contributions such as Curses. This explains the final score using the actual scoring rules.
- 🃏 Final deck snapshot: Show the total number of owned cards, including cards in hand or in play, and card counts by name. This is a useful strategy reflection, but it should be secondary to the score because it adds visual density and some cards’ value is not captured by their VP.
- 📈 Match activity totals: Turns, cards played, buys, trashing, and similar counts could make a fuller recap. Add these only if they’re deliberately tracked for the whole game; don’t estimate them from the bounded room log.
- 🏅 Superlative awards: “Most played,” “biggest deck,” or “closest finish” might add personality. They are optional and can distract or imply that a single-game statistic measures skill. “Closest finish” is already a straightforward point margin, while the other awards depend on deciding which activity is meaningful.
✅ Recommended First Version
✅ Start with final standings and point margin, followed by an expandable score breakdown by card. The first view stays quick to understand after a win, loss, or tie; the breakdown gives an interested player a concrete explanation of the score without requiring new historical tracking.
📱 Put the whole standings summary first and keep details below a “Score breakdown” disclosure. If the screen should be even shorter, make the breakdown collapsed by default. Keep the results equally complete for every player so a losing or tied player can still see what happened.
🧪 Final scores and card contributions can be checked against the existing score calculation. If match activity totals are selected later, they should be tested against known games—including long games that exceed the current log limit—and not silently presented as complete when history is missing.
🗳️ Easy Options
Pick a package by its letter:
- A — Standings: final VP, place, and margin from the winner.
- B — Score sources: A plus counts and VP contributions for each scoring card. Recommended.
- C — Deck snapshot: B plus final card counts and total owned-card count.
- D — Activity recap: C plus full-game counters such as turns and buys; requires dedicated tracking.
- E — Superlatives: D plus optional awards.
Choose a presentation too: 1 = compact standings with the breakdown collapsed; 2 = show the breakdown immediately. For example, “B + 1” selects the recommended score explanation in a compact layout. You can also say “A + 2” or “C + 1” to choose a different scope.
✍️ Signed
🤖 Built with care by GitHub Copilot Coding Agent
📅 November 15, 2026
🏠 For bagrounds.org