How do I design a game state that players can understand at a glance?
Quick answer
Show the information players need for their next decision first, and group it in predictable places. Make different kinds of information distinguishable with more than color alone, and make changes easy to notice. Then test a rough version: ask a player what they can do, what matters now, and what changed. If they must hunt or ask, simplify or reorganize the display.
The question, the details, the next step.
How do I decide what belongs in the visible game state? I keep wanting to show every rule and number.
Start from the next decision, not from the full rulebook. List the questions a player must answer on their turn. For a hypothetical small card game, those might be: “What cards can I play?”, “How many actions remain?” and “What is the current round goal?” Put answers to those questions in the most noticeable area. Keep background information—such as a rule that rarely applies—in the rules reference or a clearly labeled secondary area.
For each piece of information, ask: Can a player make a legal, meaningful choice without seeing this? If yes, consider moving it out of the main display. If no, keep it visible or make it easy to find. Avoid showing the same changing number in several places; duplicate values can disagree or make players unsure which one to trust.
Once I know what to include, how should I arrange it so players can scan it quickly?
Group information by the question it answers, then keep those groups in consistent locations. For example, a prototype might have a personal area for a player’s resources and available actions, a shared area for the round goal and turn marker, and a discard area for completed plays. Give each group a short label if its purpose is not obvious.
Within a group, put the most decision-relevant item first or make it the most prominent. Use spacing, headings, shape, icons, and text to create distinctions. Don’t rely on color alone: a symbol plus a label, or different shapes, can help distinguish categories when colors are similar or hard to see. Keep labels brief, but use wording players already encounter in the rules. Consistent placement matters more than decorative complexity.
Players still miss when something changes. What can I do to make updates clearer without cluttering the board?
Make the change legible at the moment it happens. Use a simple, consistent update action: move a marker, turn a card, add a token, or replace a number. If a value changes often, keep the current value in one stable spot and make the update visible there. A brief turn reminder can also say what changes now, such as “resolve the action, then advance the round marker.”
For a hypothetical example, suppose a player has three actions and spends one. A clear state might show Actions: 2 in the same place each turn, with one action token removed. That gives players both a readable number and a visible change. Avoid temporary effects that vanish before players have a chance to notice them; if an update is important to the next choice, leave its result visible. Test any symbols or shorthand with people who have not learned your intended meaning.
What’s a practical way to test whether the whole state is understandable at a glance?
Make a rough paper version and ask someone unfamiliar with it to look at the game state briefly. Then cover the rules explanation and ask three concrete questions: “What can you do now?”, “Which information affects that choice?” and “What changed since the previous turn?” You are checking whether the display communicates, not whether the player can guess a hidden rule.
Note where they look, what they overlook, and which words or symbols they interpret differently from your intention. Change one layout or label issue at a time, then try again with a fresh glance. If they can answer only after you explain the board, that is useful evidence that the display needs clearer grouping, labels, or update cues—not proof that the player did something wrong. This quick check cannot establish that every player will understand it, so treat it as a way to find confusing spots, not a guarantee.
A practical checklist
Write down the decisions players make and the information needed for each one.
Move rarely needed rules and background details out of the main display.
Group related information and keep each group in a consistent location.
Distinguish categories with labels, shapes, or symbols as well as color.
Choose a clear, repeatable way to show each important state change.
Test a rough version with an unfamiliar player and note what they miss.
A few more useful answers
Should every player see the same information?
Show shared information where everyone can consult it, and keep private information in each player’s area. Make the distinction clear in the layout so players know what is common and what belongs to them.
How much text should a game-state display use?
Use enough text to make labels and choices understandable, but keep long explanations in a reference players can consult. Test short labels with someone unfamiliar with your intended meaning.
What if important information changes frequently?
Keep the value in one stable, easy-to-find place and use a consistent way to update it. If the change affects a decision, leave the resulting state visible rather than relying only on a brief announcement.