iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A useful game refusal answers the player’s next question: “What can I do now?” State what is unavailable in this situation, explain the relevant rule or unmet condition, and give a valid next action when one exists. If the rule leaves no way to proceed, say so plainly rather than implying there is a workaround.
Build the refusal around the player’s next decision
Treat a refusal as feedback about a game rule, not merely a report that an input failed. A practical pattern has four parts: the constraint, the reason, a next action, and help or recovery when relevant. This adapts Unity’s problem-cause-solution guidance, Google’s problem-and-next-step approach, and the Government of Canada Design System’s recommendations for concise error messages (Unity guidance; Google developer guidance; Government of Canada Design System).
- Constraint: Say what cannot happen in this context.
- Reason: Name the relevant rule or unmet condition in language the player can understand.
- Next action: Offer one specific, legitimate action that can advance the player’s goal, if one exists.
- Help or recovery: Point to further help or a safe way to revise the action when that would help.
Do not promise a fix the game does not offer. When an action is genuinely unavailable, a clear final refusal can still explain what options remain.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesReplace vague blocks with specific information
“Failed” or “Not allowed” reports an outcome but gives the player little basis for deciding what to do. A stronger message identifies the constraint and, when possible, the condition that caused it.
#1 Best Overall
Illustrative example: “Can’t enter the arena yet. Your party needs one more member. Invite a player or return to the party screen.” The condition and suggested actions must match the game’s actual rules. If neither action is valid, do not include it. Xbox’s Gears 5 matchmaking example follows the same principle: it identifies that matchmaking could not be completed because the squad exceeds the maximum size (Xbox Accessibility Guideline 115).
Specificity does not mean disclosing every detail. The Xbox guideline’s password example gives an error and general criteria hints while avoiding details that could jeopardize password security; it also has the error narrated for players using screen narration. Explain enough for a useful decision without exposing sensitive information.
Put the message where the blocked action happens
Show necessary feedback close to the object, option, menu, or control that triggered it. Apple recommends placing error messages as close to the problem as possible, helping players connect the message to their attempted action rather than search elsewhere for an explanation (Apple guidance on writing).
Keep the language neutral, concise, and courteous. The Government of Canada Design System recommends one reason, one or two possible fixes, a clear call to action, and a predictable structure: what happened, why, and what to do. Adapt that structure to the game’s voice without hiding the rule or blaming the player.
Rank #3
Make feedback accessible and proportionate to the stakes
Do not rely on color alone to signal a refusal. Xbox Accessibility Guideline 115 says an automatically detected input error and its correction method should be conveyed in multiple ways—for example, through text or narration—and that errors should be visually distinguished and emphasized where they occur. Apple likewise notes that color, text, sound, and haptics can provide feedback through different channels (Xbox Accessibility Guideline 115; Apple guidance on feedback).
Match interruption to consequence. A routine unavailable action may need only brief, nearby feedback; it should not interrupt play with a generic notice when nothing can be done and the event is not significant. By contrast, an action that could delete or modify player-controlled data needs clear, prominent feedback and a meaningful opportunity to review and correct or reverse the action before commitment. Microsoft’s general error guidance similarly calls for messages that are relevant, actionable, brief, clear, specific, courteous, and rare (Microsoft error-message guidelines).
Rank #4
Review each refusal before it ships
Use these questions to compare alternative treatments. They are a design-review checklist, not a validated scoring system.
- Specificity: Does the message name the relevant constraint instead of saying only “failed” or “not allowed”?
- Actionability: Is there a legitimate next action, and is it clear? If none exists, does the message avoid implying otherwise?
- Proximity: Does the feedback appear by the object, control, or action that triggered it?
- Accessibility: Can players perceive the information through more than one channel, and is the error distinguishable from ordinary text?
- Interruption and consequence: Is feedback noticeable enough for the stakes, especially when progress or data could change or be lost?
- Tone and brevity: Is the message neutral, courteous, and short enough to understand during play?
For broader accessibility reviews, Xbox’s guideline catalog includes related areas such as text display, contrast, nonvisual and audio cues, subtitles and captions, screen narration, input, UI navigation, and communication experiences. These are neighboring areas to review, not all requirements specific to refusal messages (Xbox Accessibility Guidelines catalog). The exact wording should be checked against the game’s mechanics and player language. The cited standards and guidance offer design recommendations, not a measured estimate of how much a particular refusal improves player outcomes.
