Define what the second run offers
NovelToGame chooses shared trunks, reorderable investigation nodes, or a few separate routes according to budget. Its world method also recognizes one-time knowledge as a valid experience. Further replay design is needed when replay is promised; a complete one-sitting story need not add it.
| Replay reason | Difference to design |
|---|---|
| Unvisited character route | Independent goals, resistance, and payoff rather than another portrait. |
| Judgment with known information | Old scenes or clues gain meaning while actions remain grounded in this run. |
| Another tradeoff | Different opportunities with real relinquishments, not a universally superior second route. |
Combine these if appropriate, without requiring all. Define the promise and control cost: shared scenes retain histories, and separate routes must be deliverable.
Original example: two choices for a band’s performance
In this original short game, a band may take an early slot or wait for a late one. The organizer has offered both times. The drummer must catch the last bus and can play only early; the singer’s invited teacher arrives later. The band has rehearsed a quiet arrangement without drums, but members must agree to use it. Players can learn these conditions before deciding. The band has working recording equipment and has agreed to record this performance.
Early preserves the full ensemble but misses the teacher. Late allows a performance for the teacher while giving up this full-band appearance. This is not one correct option with a punishment alternative. An invented extra bus or changed schedule cannot deliver both for free.
On the first run, the player might choose early. The drummer helps pack instruments; the singer later gives the teacher the actual recording, and the teacher responds after listening. On a second run, players might obtain agreement for the quiet arrangement and choose late. The drummer has left while the teacher sits in the audience. Both routes complete a performance with different music, attendees, and farewells.
Replay comes from reconsidering attendance and values, not hiding a timetable to trap players. Recording must actually occur early; receipt and listening also need scenes. “We could send it” is not evidence that it was heard.
Reuse scenes without importing an unplayed history
The venue and ordinary setup may be shared. Early reads drummer present, teacher absent, and ensemble chosen. Late reads accepted quiet arrangement, drummer gone, and teacher arrived. Ending props and lines reflect those facts; the late route cannot thank the drummer for performing this show.
Players remember the first answer, while characters usually act on this run’s knowledge. Players may seek a known clue earlier, but acquiring objects, promises, and cooperation still needs current actions. Define the scope of explicit memory carryover or skipping features rather than importing every secret and relationship.
Fast-forwarding read scenes is a separate interaction decision. It can reduce repeated reading without skipping state or choice consequences. After implementation, check saves and restart.
Walk two paths before expanding
Walk early and late paper paths from the same initial state. Check conditions, member responses, actual performance, and ending echoes. Implement a small slice and observe whether a second run reveals relationships, changes judgment, or invites another outcome.
If replay adds only a closing evaluation, deepen consequences of existing choices before adding characters. If every tradeoff disappears after the secret is known, acknowledge a mainly first-run discovery experience or redesign costs that still matter. If routes require much independent content, narrow scope instead of expanding every branch into empty endings.
Reachability and historical consistency can be checked. “Worth playing again” requires player feedback, not node counts, ending counts, or machine pass rates.
FAQ
Must a second run change random results?
No. Another route, a changed view of a relationship, or another cost can justify replay. Add randomness only when it changes decisions and fits the promise; it cannot substitute for meaningful choices.
Do it with the skill
Use game-concept to define the second run’s appeal, shared and separate content, and budget; use game-world-design for concrete history and responses. Preserve current-run knowledge and action sources. Do not prove replay value through extra randomness, total scores, or ending counts.
Read the method: Narrative structures, separate routes, and budget · One-time knowledge, replay promise, and decisions · Shared scenes and historical echoes