Teach the Present Action Before the Whole System

Background, every system, and the present action answer different questions. Orient players to role, immediate goal, and an actionable object, then teach what this step needs.

The source calls for a primary opening focus and a complete action-feedback-state beat. The action may be observation, a reply, delivery, placement, or movement. Adaptations need not all begin with walking, combat, or inventory.

Use a character request, an environmental marker, or a short prompt. State necessary instructions clearly instead of hiding them for immersion, while avoiding encyclopedic dialogue about ten future systems.

Write a Complete First-Action Card

Present stepDesign detail
GoalAn observable task now.
Needed evidenceWhere the player sees objects, conditions, or rules before acting.
InputActual clicking, choice, movement, or another action beyond reading.
SuccessWorld response and confirmed state change.
Recoverable mistakeCause, retained state, and what can change next time.
Next useA later read of the learned rule.

This is an editorial card. Length, option count, and time follow the game. A displayed tutorial does not establish comprehension. Gesture, collision, and spatial risks need a prototype on the target platform; paper text checks logic.

Original Opening: One Delivery Before the Next

“Letters at the Station” is an original paper adaptation led by text and choices. Its core action is choosing a recipient from delivery information and seeing whether they actually accept. The new courier does not begin with the town’s secrets, every relationship value, or the entire schedule.

Opening: “Deliver the storeroom letter to Lin.” The envelope names Lin and the storeroom. Two present characters have visible names and roles: Lin handles the storeroom; Fang handles the wharf. One letter remains undelivered. Actions are “Give the storeroom letter to Lin,” “Give it to Fang,” or inspect the envelope. Goal and recipient information stay near the choices.

Complete path with a mistake:

The player offers it to Fang.

He reads the address. “I don’t receive storeroom mail. Lin’s by the counter.” He does not take it.

Feedback: “Not delivered; still holding the storeroom letter.” The delivery actions remain available according to state.

The player inspects the envelope and selects Lin.

Lin checks the recipient, takes it, and signs. “This one’s mine. Received.”

The goal completes and possession clears. The wrong first choice did not reveal the letter’s contents to Fang.

Lin hands over a new envelope addressed “Wharf, Fang.” After acquisition, a second task appears without repeating the full explanation; envelope information and valid actions remain.

Second actionSame learned rule
Deliver to FangHe checks and accepts; actual transfer completes this task.
Offer to Lin againShe identifies the different recipient and refuses; the player can redirect.
Select stale storeroom-letter actionThat letter is gone; no duplicate transfer or receipt.

The player practices reading information, choosing a recipient, and checking acceptance. A different recipient tests reuse. This design makes a first error recoverable without hidden disclosure or destruction. Games with costly mistakes need appropriate advance information. The paper path does not establish player comprehension; observe it after building.

Observe What Players Actually Do

ObservationFirst repair
Goal cannot be foundOpening focus and present goal.
Chooses without seeing addressEvidence placement near action, not another lore panel.
Thinks rejected delivery lost the letterAccurate possession feedback and retry actions.
Always selects the first recipientUnderstanding of the recipient rule and clarity of new information.
Instructions cover controls or require long scrollingShorten the present beat; make long records optional.

Record first action, response after mistakes, and the completed path. One success may be a guess; seeing a refusal does not establish all story understanding. Feeling, willingness to continue, and control quality require actual observation rather than an automated PASS.

Shorten Long or Overbearing Tutorials

Defer future rules until useful while retaining this beat’s goal, evidence, input, and response. Reduce prompts after demonstrated understanding; new objects, exceptions, or controls may still need guidance.

If skipping is allowed, define position, possessions, and events that did not occur. Offer optional help without claiming a letter was received unless deliberate automatic completion updates results consistently.

Do not add timers, enemies, currency, and random punishment merely to make teaching exciting. Test whether the core action sustains interest before choosing pressure. A short opening may be unclear and a longer one worthwhile; assess this game through actual play.

FAQ

Must an opening tutorial finish within one minute?

No. An opening goal focuses design rather than imposing a universal time gate. Structure teaching by input risk, player background, and pacing; observe understanding and continuation as well as time.

Can dialogue alone carry the tutorial?

Dialogue may give goals and rules, but players still need to act and see results. Reading “delivered” without choosing a recipient does not teach this example’s core action.

Do it with the skill

Use $game-world-design to design the opening tutorial from core actions, player role, platform, and source constraints. Teach the current step’s rules with visible evidence, actual input, success feedback, a recoverable mistake, and another use. List questions for real playtesting without claiming the design proves understanding, feel, or enjoyment.

Read the method: Opening goal, teaching actions, and rule variation · Guidance and action labels · Complete paths and actual playtest evidence

About Novel to GameThe game-world-design skill on GitHub

All guides