Can Players Understand Resource States Without Exact Numbers?
Yes, but “Intact,” “Strained,” and “At Risk” must correspond to consistent limits on available actions. A review table linking text-based tiers, actions, and transition cues helps players understand costs before choosing—including the handoff opportunity lost by detouring for repairs—and understand changes afterward.
Introduction
Yes. When you hide exact numbers, retain three things: what players can still do, what taking another risk will change, and what warns them before that change happens. Players do not need to know precisely how much durability a sail has left, but they should be able to judge whether rushing through now will cost them the chance to rush through again. Tier names without commitments about actions still leave players guessing.
Define What Each Tier Promises First
This article uses the fictional teaching story Delivering Lanterns Through Mist Gorge: players deliver lanterns by boat and must balance reaching a lantern-receiving ceremony on time against preserving their sail. The characters, plot, rules, and wording are original demonstrations, not real user cases, measured test results, or product features. They are not real-world sailing guidance, either.
The story resolves sail-state changes only at discrete choice points. “Intact” means the sail can withstand one rush through the gorge whose consequences have been disclosed. “Strained” means normal travel remains possible, but another rush will put the sail At Risk. “At Risk” means rushing is unavailable; players can only lighten the load and continue or take a sheltered side route. These tiers summarize the actions available, rather than offering arbitrary judgments about how the sail looks.
Write these meanings before adding literary description. “The sail looks like an exhausted bird” can establish atmosphere, but cannot explain the state on its own. If “Strained” sometimes permits another rush and sometimes means rushing immediately fails, add conditions players can see or split the state into separate tiers. Do not quietly change what the same word means.
Authors can keep numbers internally or use tiers alone. What matters is consistency: with the same tier and the same visible conditions, an action's availability and its promised consequences must remain the same. Otherwise, hiding numbers becomes hiding the basis for decisions.
Link Tiers, Actions, and Cues in a Review Table
The following table can serve as a first-draft review aid. “Transition cues” are information that must appear before a choice is confirmed; the results column sets requirements for the narration afterward. Neither can replace the other.
| Text-Based Tier | Available Actions and Costs | Transition Cues Before Confirmation | Results After Confirmation | Review Focus |
|---|---|---|---|---|
| Intact | Normal travel preserves the tier; rushing earns an earlier arrival in the story | Beside the rush button, state: “This will leave the sail Strained” | After rushing, display Strained and describe the seams beginning to pull tight | Do not imply that Intact means any risk can be taken without damage |
| Strained | Normal travel preserves the tier; rushing again puts the sail At Risk | Display: “After another rush, you will no longer be able to rush through” | Change to At Risk; disable rushing at the next choice point and explain why | Players can identify the action opportunity they will lose before choosing |
| At Risk | Lighten the load and continue, or enter the sheltered bay for repairs; repairs cost one handoff opportunity; rushing is unavailable | Display: “Lightening the load leaves the sail At Risk; detouring to the sheltered bay for repairs costs one handoff opportunity and returns the sail to Strained” | Lightening the load leaves the sail At Risk; choosing repairs costs one handoff opportunity and returns the sail to Strained after repairs | Distinguish maintaining a state from repairing it; disclose the specific repair cost beforehand |
When reusing this table, keep all five columns and replace the sail with lighting, supplies, or another resource. Do not merely swap out three adjectives: every row must answer which action players gain or lose. Consider merging adjacent tiers that make no difference to available actions.
The table also needs a global rule: only explicitly stated actions or events change a tier. In this example, dialogue and checking the map do not worsen the sail's condition, and normal travel does not secretly accumulate wear. A story with continuous consumption needs separate rules; it cannot reuse this promise.
Follow One Choice All the Way to the Next
At the first gorge entrance, the sail is Intact. The lantern recipient is about to leave, and players see two options: “Travel normally and miss this handoff” and “Rush through to make the handoff; the sail will become Strained.” The choice matters because of a visible trade-off in the story; no durability bar is needed.
After players rush through, the result reads: “You hand over the lantern box before the bell falls silent. The seams along the sail's edge pull tight. Sail: Strained.” The reward and resource change appear in the same result paragraph, avoiding a success scene followed by a surprise cost several choice points later.
Someone then asks players to bring back another lantern along the way. Rushing remains available at the second gorge entrance, but the button reads: “Rush through to retrieve the lantern; the sail becomes At Risk, after which you can only lighten the load or detour for repairs. Detouring for repairs costs one handoff opportunity.” Players know that this choice also narrows their later options and that restoring those options will come at a cost.
If players rush again, the next choice point should enforce the promised restriction: “Sail: At Risk. The seams have split; you cannot rush through again.” Before the next choice is confirmed, the menu explicitly offers: “Lighten the load and continue; the sail remains At Risk” and “Detour to the sheltered bay for repairs and miss the next handoff; the sail returns to Strained.” “Take a detour” cannot substitute for explaining this specific loss.
If players lighten the load, the story continues and the sail remains At Risk. If they choose the sheltered bay, the result explicitly states that they missed that handoff and displays Strained after repairs. Full recovery is reserved for an explicit sail-replacement event later on.
This path lets players knowingly accept wear and gives repairs a clear value and cost. It does not require players to calculate hidden thresholds; it requires enough information before a choice to explain the subsequent result and menu changes.
Use Counterexamples to Check Whether the Wording Breaks Its Promises
Differences within the same tier are the easiest to overlook. Suppose two paths both display Strained. Rushing on one puts the sail At Risk, while rushing on the other immediately tears it apart, with no additional warning beforehand. That fails the review criteria: players receive the same information but face different limits on their actions.
There are three ways to fix this: standardize the result of rushing at that tier; add a persistently visible condition describing additional damage and explain its consequences for actions; or subdivide the tier. If the difference does not create a meaningful choice, standardizing the result is usually simpler than adding another cue.
Another counterexample is writing “The wind weakens” and then changing At Risk to Intact. A change in wind can explain reduced pressure now, but cannot explain why existing damage has disappeared. Keep the sail At Risk, or explicitly describe the repair process and the tier the sail returns to. In this example, repairs can only return the sail to Strained.
Also check whether cues arrive in time to be useful. Saying “You should have known the sail would not hold” after confirmation cannot make up for missing information beforehand. A vague warning cannot replace “You will no longer be able to rush through”; “Repairs require a detour” cannot replace “You will miss the next handoff,” either.
During review, examine the tier page, choice page, and result page separately. Check whether players can answer three questions: What can I choose now? What will this choice cost me? Why will my next choice be restricted? This is a review method, not evidence that real players have already understood this wording.
Choose the Precision the Task Needs, Then Decide Whether to Publish
Text-only tiers suit stories built around a small number of key trade-offs. If players need to compare many small expenditures or budget across several consecutive steps, three tiers may be too coarse. In that case, add an action-count cue such as “One rush remaining,” or show numbers directly. There is no need to keep them hidden solely for narrative atmosphere.
You can also retain tiers and add explicit consequences beside costly options. This suits situations where the usual reading load should remain light but key choice points need careful judgment. Place the extra information near the relevant choice, rather than hiding it solely in the initial tutorial.
If you deliberately write a story in which a character misjudges the sail, distinguish “The character believes it is Intact” from the state information players use to decide. Suspense can come from unknown details of the consequences, but do not present tiers as reliable guidance while punishing players who trust them with undisclosed rules.
Before publishing, check the review table row by row. Examine every transition from Intact to Strained, from Strained to At Risk, and from At Risk to the post-repair state. Also verify that the handoff opportunity lost to repairs is disclosed beforehand and actually lost afterward. Revise any instance of an action being disabled without warning, recovery without an action, a cost added after the fact, or conflicting consequences under identical conditions. The final deliverable is a set of verifiable textual promises: exact numbers are omitted, but every choice still has a basis.
