A choice screen has a simple job: help a player decide. That becomes harder when one action changes several things, an ability adds a conditional bonus, and some of the result is deliberately uncertain.

Stupid People puts that problem inside a satirical internet argument. You choose a response and an ability card, inspect the consequences, then commit the post. Building that loop made the relationship between a preview and its eventual result an explicit design requirement.

This is an implementation note from the current demo. It describes the design and its checks; it does not claim that an uncoached player study has established the best interface.

A bigger number needs a meaning

The game tracks people, reactions, heat and credibility. A large reaction count does not mean the same thing to every employer. The Bureau wants to contain panic; the Engagement Department wants attention.

That difference means a preview cannot reduce the decision to a single universal green number. It has to show which quantities change and leave the player to judge the tradeoff against the assignment.

The general lesson is to connect feedback to the user's objective. If two missions reward different behavior, their decision surface needs to preserve that distinction.

Separate choosing from committing

Selecting a card prepares a play. It does not immediately resolve the turn. The player can inspect the card, compare a response and read the consequences before pressing Play.

That separation is especially useful with a small fanned hand: the player gets a visible selection state without losing access to the full rules. A mistaken selection remains reversible until the action is committed.

The game uses an explicit transition path for player commands. The renderer reads the state rather than modifying gameplay. That boundary gives the preview, controls and simulation a shared point of reference.

Show the arithmetic at the right depth

The default preview needs to be readable quickly. The full calculation can carry the detail.

In the current game, card bonuses and separate one-turn bonuses contribute to the displayed total. They are shown distinctly so the player can inspect why the result changed. A temporary bonus should not look like a permanent property of the card.

This suggests a useful sequence for any consequence display:

  1. Show the quantities affected by the pending action.
  2. Show whether each result is exact, a range or unknown.
  3. Let the user inspect the contributing rules.
  4. Resolve the action through the same rules used for the preview.

The fourth step is what makes the earlier presentation trustworthy. A polished preview that uses a different calculation can confidently explain the wrong result.

Preserve uncertainty where it belongs

An exact number communicates a stronger claim than a range. If the outcome depends on information the player does not have, displaying false precision makes the interface misleading.

Stupid People uses exact values, faithful ranges or ??? where information is unknown. A range must include the outcomes the resolver can actually produce. An unknown must stay unknown instead of quietly becoming an optimistic estimate.

This does not mean revealing every hidden mechanic. It means being accurate about the knowledge the preview is offering.

Automation still needs stopping points

Manual control is the default. Suggested and Auto are available, but major decisions wait for a person. Inspection and returning to the game can also hold automatic play until Resume.

These stopping points protect the moment of decision. A person who opens a rule explanation should have time to read it before the surrounding state changes.

Automation is consequently a choice about pace and delegation. It does not remove the importance of an employer selection, a critical opening or a chapter decision.

What the checks establish

The campaign's verification exercised card and response combinations, consequence calculations, saved-run replay and complete browser journeys. Those checks can find a mismatch between preview and resolution or a control that advances at the wrong time.

They cannot establish that the game is enjoyable or that a new player immediately understands its vocabulary. Those questions need observed play. Our next useful evidence is where an uncoached player hesitates, what result surprises them and whether they can explain why a card helped.

If you try the demo, those moments make particularly useful feedback. The first-campaign guide explains the current controls, and the project record describes the broader game.

Sources and version

This note is based on the Stupid People v5 transition, preview and player-agency implementation, reviewed September 6, 2026. It is a project observation and design interpretation, not a claim about all players or all deckbuilders.