An affinity bar cannot replace remembered conduct
novel-to-game’s narrative method records specific persistent facts; its numeric method requires origins, uses and feedback for numbers. Neither assumes every relationship needs a hidden bar.
Original character: craftsperson Cen Qing values control over how her work is used and dislikes others accepting exhibition terms for her.
| Item | Record |
|---|---|
| Promise to ask before publication | Memory: A specific commitment; Later response: Willingness to share an unfinished sketch when consulted |
| Publish without asking | Memory: The broken commitment; Later response: Refuses further representation by the player |
| Help move materials | Memory: A completed collaboration; Later response: Work proceeds faster, without erasing the breach |
Three helpful tasks cannot automatically cancel a broken promise. If repair is possible, show explanation, changed action and her own choice rather than restoring a total score.
Give each state a write point and a read point
A small table is more useful than many unread variables:
State: Promise to consult Cen before publication.
Write: Player commits at the first exhibition request.
Read: A later publication opportunity changes options and responses.
Visible echo: Keeping the promise opens collaboration; breaking it removes representation rights.
Ending: Show who controls publication and whether cooperation is restored.
Feedback need not be a reward banner. Changed address, an unsolicited visit, an object shown or a request refused can reveal remembered conduct.
Delete unread states. Ordinary greetings need not enter a permanent ledger; prioritize facts that affect later judgment.
When numbers are needed, calculate the threshold
If the project needs a measure of working familiarity, test example numbers rather than claiming a universal standard: start at 1; two distinct collaborations add 1 each; familiarity 3 opens a more complex shared repair. An unresolved publication breach remains a separate condition.
| Item | Record |
|---|---|
| Two collaborations, promise kept | Familiarity: 1 + 1 + 1 = 3; Cooperation: Shared repair available |
| One collaboration, promise kept | Familiarity: 2; Cooperation: More preparation needed |
| Two collaborations, promise broken | Familiarity: 3; Cooperation: Numeric condition met; authority and trust still need handling |
Check reachability, whether the initial state already qualifies and whether another meaningful route exists. A single mandatory sequence is a story condition, not deep numeric strategy.
Increasing a relationship value should create new action or response. A growing display with unchanged character behavior does not deliver the system.
Test whether the character remembers opposite histories
Compare a kept-promise path with a broken one: do responses differ, do available actions change consistently, and can the ending identify the cause? Add a path with no promise so it cannot accuse the player of breaking one.
If one repeated gift solves most situations, check whether every problem reads only a total and ignores facts. If changes are unclear, add character or world feedback without exposing every variable.
Balance and character appeal require actual play. Automated checks can expose unreachable thresholds or leaked states, not prove universal naturalness. Repair the failed node before rewriting every character.
Complete paths: a score of three cannot decide for Cen
Paper starting state: familiarity one, no publication promise, and Cen controls her work. The player holds a plan copy for collaboration, which grants no publication authority. The distinct collaborations are moving materials and sorting tools. Each adds one only upon its first completion; repeat clicks add nothing. Shared repair requires familiarity three and no unresolved publication breach, and opening the activity is not starting the work.
- Kept-promise path: at the first publication request, the player tells Cen, “I’ll show you before anything goes out.” She replies, “Ask about sketches too.” The promise is made. Both collaborations are actually completed: 1+1+1 = 3. When the exhibition next requests material, the player selects “Show Cen the request first,” without publishing. She says, “We can repair this together. You can see the sketch first. Don’t publish it.” Private viewing is granted; publication is not. Shared repair is available but has not begun. The response reads conduct and collaboration instead of merely announcing a higher affinity.
- Breach path, with the same two collaborations: make that promise, finish both collaborations, then publish the plan without asking. The event records the breach. Cen actually sees this version on the exhibition page and recognizes the plan she did not approve, then objects. Familiarity remains three. She says, “You said I would see it first. Don’t post for me again.” The player selects “Move the materials once more.” She replies, “Materials don’t explain this.” Repeating completed collaboration adds no score. The breach and withdrawn representation remain; the shared-repair gate stays closed despite sufficient familiarity. If the story permits repair, write correction, explanation and her decision separately, without automatic forgiveness.
- No-promise counterexample: complete both collaborations from a clean start without promising to publish for her. Ask, “Do you want this included in the next exhibition?” Cen replies, “Show me the version you want to send first.” No invented “You broke your promise again” appears. The request is pending, with neither publication nor representation permission granted. Without a publication breach and at familiarity three, shared repair is available; publication remains a separate decision.
Each path reads only its own occurred history. The no-promise path cannot import another path’s breach. Check choices, replies, authority and unfinished work together. These are rule and dialogue arrangements, not a claim of an executed playtest or proven character appeal.
FAQ
Can a relationship system work without an affinity score?
Yes. Promises, public positions, object ownership and character responses can form traceable relationship changes.
Can hidden affinity have no feedback?
Players still need conduct, wording or available actions that make the effects of their choices understandable.
Do it with the skill
Ask game-world-design for memories, write points, read points and visible responses before choosing numbers. Calculate representative threshold paths without letting totals erase promises and losses.
Read the method: Relationship history, persistent facts and visible echoes · Purpose, reachability and tradeoffs in relationship values