Choose structure from experience and budget
NovelToGame chooses structures by experience and budget. This page covers routes and scope; use the choice guide to assess a decision’s meaning.
| Structure | Experience and cost |
|---|---|
| Shared trunk with merges | Share major events while retaining relations and positions; cost lies in state variants. |
| Reorderable investigation | Choose where and whom first; cost lies in conditions and clue combinations. |
| One main line, local choices | Everyone sees core events, while causes, responses, and actions retain choices; branching stays shallow. |
| Early route assignment | Choices lead to different people or tasks; requires separate later content. |
| A few separate paths | Short stories, multiple runs, and different results; much content is unseen in one run. |
One endpoint need not make every button irrelevant. Players can decide who participates, how evidence is obtained, and whether promises are kept; causes and consequences differ even at the same endpoint. If only tone changes with no later effect, describe an expressive choice rather than a major story route.
Original example: investigate a missing theater handover book over one night. Ask the gatekeeper or check storage first, then attend the meeting. The shared meeting retains evidence, promises, and willingness to testify rather than erasing history.
Map nodes and conditions before writing dialogue
Start with four nodes:
Entry: the book is missing and tonight’s meeting sets the investigation window.
A: question the guard, obtaining a box-removal statement; record any promise of anonymity.
B: inspect storage, obtaining movement records; handing them over changes evidence ownership.
Shared meeting: vary questioning and responses according to testimony, ownership and promises.
Flexible order does not require a wholly separate scene for every combination. Reuse shared action and replace the affected passages.
| Item | Record |
|---|---|
| Guard | Entry condition: Present, not yet questioned; Player changes: Anonymity promise and timing inquiry; Departure record: Statement and commitment |
| Storage | Entry condition: Access permitted; Player changes: Whether to hand over the record; Departure record: Seen record and its holder |
| Meeting | Entry condition: Investigation ends or deadline arrives; Player changes: Evidence used and promises honored; Departure record: Persuaded people, relationships and open questions |
Do not add a countdown merely to manufacture tradeoffs. If a deadline is used, node access and consequences for unfinished investigation must be consistent.
Preserve history at convergence
The same meeting can retain these differences:
- Narration cannot automatically reveal a guard’s identity after an anonymity promise. The player may break it, with consequences.
- A record already surrendered cannot appear in the player’s bag. Ask its holder to present it or use an established copy.
- Unheard testimony cannot become an available quotation.
- A respected promise may lead the guard to volunteer more information; a broken one may end cooperation.
Convergence uses fewer scenes while retaining history. Give each state a write point, read point and perceptible result. Remove states nobody reads.
If a route has a fundamentally different theme and action, a separate later section may preserve it better. Acknowledge the additional scope.
Showing the record at the meeting needs a response. If it was handed to the manager, the player can ask, “Put the record I gave you on the table so we can check.” Only after acceptance and display do attendees acquire its visible contents. Refusal leaves existing testimony or another request available; the document does not return to inventory automatically.
An anonymity promise also has scope. Mentioning a box-carrying witness does not grant permission to reveal the name. Read possession, knowledge, and disclosure separately so the shared scene retains different strategies.
Budget variants and characters as well as nodes
List shared text, then facts requiring variants. The meeting need not be rewritten in full for every state combination: evidence presentation, guard response and attribution can be handled separately. Their combined order and knowledge still need checking.
The concept method uses nodes × variants × key characters to flag combinatorial cost, not quote precise labor. Identify actual sharing and affected characters instead of treating every option as a complete route.
Walk opposite histories: keep the promise and retain evidence; break it and hand evidence over. Add a path that never questions the guard to detect impossible testimony. If a choice changes only a polite reply and is never read later, call it local expression rather than a major route.
Complete a few remembered decisions before expanding. State what new action and result a route adds, not merely another clickable portrait.
FAQ
Does convergence make a choice fake?
Not if the shared scene preserves different causes, relationships, objects and available actions. Erasing all history removes the consequence.
Are more options always better?
No. Let the situation determine options and prioritize actions that alter causality and are remembered later.
Do it with the skill
Ask game-concept to compare nodes, shared scenes, necessary state variants and content burden without an unlimited tree. Evaluate choice significance separately from production scope.
Read the method: Branch structures and content budget · Shared scenes, persistent states and remembered history