Start With a Destination the Player Can Read
“Explore the whole island” is not this segment’s goal. Recovering a sketchbook, hearing a witness, or delivering an object gives movement direction. Places contribute decisions, actions, atmosphere, or necessary space rather than unused area.
The source world method identifies visible extent, main route, optional risk route, and landmarks. Risk can mean a promise, time, or a condition rather than injury. Show the main direction first, with detailed maps or logs available on demand.
Make Landmarks Useful and Consistent
| Route element | Question |
|---|---|
| Landmark | What is visible and distinguishes a fork? |
| Link | Which locations connect, and can the player return? |
| Condition | Does space, tool, gate, or person allow the action? |
| Stop | What evidence, interaction, or experience is available? |
| Return | How do retrieved objects, opened routes, and promises persist? |
A lit icon is not arrival; seeing an object is not possession. Link changes affect later paths and need more than an updated diagram.
Original Paths: A Sketchbook and an Optional Return Favor
Paper text-adventure: the player starts at an inn courtyard; their sketchbook was left at the studio yesterday, and its keeper has said they may collect it. Links are courtyard↔public garden↔studio, plus a private courtyard↔studio shortcut. A red courtyard sign directs the garden route; a stone well has a blue-door direction marker, matching the studio door. These landmarks and the destination are public.
Zhuang manages the private gate and is present. Asked for access, she says, “You may go. Bring my empty basket back from the garden on your return?” The player explicitly agrees, and she opens the gate. A gardener’s public notice permits returning Zhuang’s basket to the courtyard; it is beside the notice, with the gardener present allowing its return. No secret relationship authorizes taking it.
| Path | Action and returned state |
|---|---|
| Public route | Follow the sign to the garden, then the well marker to the blue door. The keeper actually hands over the player’s sketchbook. Return through the garden; possession is retained without an unmade basket promise. |
| Approved shortcut | Ask, accept the favor, and use the opened gate. Receive the sketchbook. Return studio→garden, read the notice, collect the empty basket, and hand it to Zhuang in the courtyard. The sketchbook remains with the player; the basket is returned and the promise settled. |
Walk these independently from the same initial state, without borrowing permission or promises from another branch. The public route can also include voluntary help; this table does not mandate only two choices. The shortcut shortens the outward route but adds a known return obligation.
Returning directly without collecting the basket retains the acquired sketchbook while Zhuang asks about the promise. Main-object retrieval does not settle it automatically. This unbuilt paper design proves no navigation clarity, spatial control, or enjoyable route tradeoff.
Return Without Repeating or Resetting History
On a return to the garden, emphasize the outstanding basket rather than repeating the entire introduction. An already-held sketchbook cannot be duplicated by an old collection action. Trying the private gate before permission retains position and prompts asking Zhuang.
The representative public path has no basket promise, so Zhuang cannot demand it as promised. Read actual history for different courtyard replies without copying a complete map per route.
Restart, rollback, and loading follow save rules; returning does not itself reset objects or routes.
Check Causality, Then Observe Navigation
On paper, walk main, shortcut, and a missing-condition path, recording position, possession, links, knowledge, and promises. Look for transfers before arrival, gates crossed without permission, duplicated objects, or another branch’s obligations.
A text sandbox can check causal risk. Movement, sightlines, camera, or terrain need an appropriate engine prototype; readable prose does not prove a landmark is visible around a corner. Observe attention, recovery from wrong turns, and return direction in the candidate rather than declaring navigation complete from a table.
For excessive length, remove purposeless stops or repeats instead of teleporting over the promised judgments.
FAQ
Is a larger exploration map better?
Not necessarily. Check decisions, actions, experience, or necessary links. Unused distance and rooms add production and memory cost.
Does returning require a completely new scene?
No. Retain space, read actual possession, knowledge, and promises, and emphasize changes. Compress irrelevant introductions without importing an unchosen branch.
Do it with the skill
Use $game-world-design to review exploration with map links, goal, seen landmarks, and route conditions. Walk from the initial state through retrieval and return, checking position, possession, knowledge, and promises. Add only decision-relevant places and do not equate text walkthroughs with navigation validation.
Read the method: Routes, landmarks, and changing situations · Knowledge, objects, and callbacks · Location conditions and actual possession