Turn a character need into player action
game-world-design connects current state, player action and world rule to a new state, readable feedback and changed opportunities. A quest needs a starting path and understandable resistance, not just background plus a completion button.
Original greenhouse: restore supply before sunset; valve order affects storage. The gardener holds a key. The administrator wants repairs but fears disclosure of a parent’s modification record. Players can investigate and seek help or try valves after learning the risk.
Establish the failure, investigation point and key holder on entry. Show valve risks through readable diagrams and warnings before failure, rather than revealing an unknowable rule afterward.
Fill a production-ready quest card
| Field | Example |
|---|---|
| Initial state | No supply; north reserve remains; gardener holds key |
| Goal / deadline | Restore supply by sunset; expiry changes nursery state |
| Starting path | Read diagram, request key, gain operating access |
| Tradeoff | Show old record for a reliable sequence, or keep it private and accept trial risk |
| Rule result | Update valves, reserve and affected plants from the action |
| Feedback | Water and nursery show the change; characters respond |
| Next opportunity | Gardener’s assistance reads loss and whether the record was shown |
Keep task-relevant rules rather than imposing identical fields on every game. Showing a document informs its recipient; private inspection does not automatically inform every NPC.
Give approaches distinct consequences
The investigation route finds and shows the modification record. The gardener supplies a verifiable sequence; water is restored only after the player gains operating access and follows it. The administrator then asks why the record was disclosed. Either route can retain the original document; the private route also keeps its contents undisclosed to the gardener while accepting the risk of draining the north reserve through trial.
Label the button “Show the gardener the modification record,” not “Honest route.” Present necessary costs without every distant ending. An uninformed gardener cannot later quote unseen details.
Not every approach must succeed. Nursery damage may cause refusal of later help while opening another investigation path. A known-risk failure with continuing actions is more complete than an isolated failure popup.
Complete the route: knowledge still requires action
Continue the greenhouse example as a paper route for production discussion, not a running prototype. Make its established order-dependent storage rule concrete: from both valves closed, south then north restores supply and preserves the north reserve; opening north first loses that reserve. This is the example’s fictional rule, not real plumbing advice. Present it through the diagram and gardener’s warning before operation.
| Player action | Result and feedback |
|---|---|
| Before sunset, inspect the diagram and find the record | The player learns the order risk and record contents. The gardener remains uninformed and holds the key. |
| Choose “Show the gardener the modification record” | After seeing it, the gardener explains south before north; the player checks that against the diagram. The original stays with the player. Viewing does not transfer custody. |
| Borrow the key and open the valve room | In this route the gardener agrees, placing the key in inventory. The player uses it to gain access before valve actions become available. Knowing the sequence opens neither door nor supply. |
| Open south, then north | The announced rule restores flow and preserves the reserve. Completion is before the deadline, avoiding this outage’s expiry loss. Scene water and the log read the same result. |
| Return the key and ask about the old accounts | The key returns to the gardener. Reading the absence of loss and having seen the record, the gardener agrees to help. Assistance becomes available; the accounts are not already solved. |
The administrator needs access to the disclosure before asking about it. Here the gardener tells him in person; a distant administrator cannot automatically inspect inventory. Knowing a document was shown does not reveal all its contents.
For comparison, start from the same state: privately read the record and borrow the key without showing it, then open north first. The rule removes the reserve; flow, nursery and log read the resulting state. The gardener can refuse later help because of actual loss but cannot quote unseen records. Repeating resolution cannot remove the reserve again or grant assistance twice.
Specify these inputs and results before checking a prototype. A coherent paper account does not establish working access, inventory transfers, deadlines or feedback.
Check agreement across log, world and characters
Walk investigation, key access, valve operation and resolution, then change the order on a neighboring path. Compare water flow, key inventory, nursery state and log. Completion must change more than text, and repeated resolution must not duplicate rewards.
Connect the next quest to this result: assistance, obstruction or new records each need a cause. Repeated collection errands without new tradeoffs can become one action.
After rule changes, replay the affected route and a neighboring choice sharing earlier state. Polishing the log cannot leave an obsolete result hidden in state; dialogue and actions must read the revised history.
FAQ
Does every quest need combat?
No. Investigation, negotiation, exploration, craft, or a relationship decision can make a complete quest when the player’s actions change the state.
Do it with the skill
Use $game-world-design to turn a source conflict into a quest card with initial state, access, risks, results and later responses. Preserve knowledge boundaries and define a normal path plus a meaningful counterexample.
Read the method: Actions, feedback and quest responses · Agendas and knowledge boundaries