Relationships, Memories, and Emotional Continuity
Relationships and memories are deliberately separated because they answer different questions.
A Relationship asks: What is the ongoing dynamic between these people?
A Memory asks: What does this person remember or believe about a particular experience?
Keeping those jobs separate prevents one enormous emotional-history file from becoming the only place anything makes sense.
Relationship Profile is the canonical pair
A Relationship Profile is the main record for two Characters’ ongoing dynamic. It can track:
- Each person’s view
- Public and private dynamics
- Relationship state and trend
- Emotional dimensions
- Boundaries
- Strength
- Unresolved issues
- Next likely behavior
- Change history
- Key Memories
Use one canonical pair record for the same two Characters. Do not create “A and B” plus another duplicate called “B and A.” The pair key exists to help prevent that.
Specialized bond records
LWE includes focused relationship types for dynamics that deserve additional structure:
- Friendship
- Rivalry
- Romantic Bond
- Mentorship
- Family Connection
- Promise and Debt
- Betrayal
- Emotional History
- Inherited Bond
These do not replace the Relationship Profile. They point back to it when a canonical pair exists.
Use a specialized bond when the theme itself matters. A simple friendship may need only a Relationship Profile. A friendship tested by shared oaths, strain points, and a specific bond type may benefit from a Friendship record.
NPC Memory is subjective
An NPC Memory can store:
- What happened
- What the NPC believes happened
- Confidence and distortion
- Emotional impact and valence
- Behavioral effect
- Salience
- Reinforcement
- Who the memory was shared with
- How the memory might change
This allows characters to remember the same Event differently. Memory is not an objective transcript.
Use it for experiences that change future behavior. Do not create a separate Memory because an NPC noticed the player’s shoes.
Knowledge layers protect secrets
Many file types can separate information into layers such as public, player-known, restricted, or GM-only. This is useful for secrets, misunderstandings, disputed history, hidden motives, and information that should become visible later.
A public-facing summary should not casually reveal a hidden truth merely because both fields exist on the same record.
Location Memory
Places can remember too—not literally in every genre, but through evidence and social consequence.
Location Memory can represent:
- Physical scars
- Memorials
- Laws created after an Event
- Rumors and legends
- Hauntings
- Rebuilding
- Emotional atmosphere
- Hidden historical evidence
The Location remains the canonical place. Location Memory records how the past continues shaping it.
Updating relationships after a scene
Do not update every emotional dimension after every conversation. Ask:
- Did trust, fear, affection, resentment, dependency, respect, or obligation meaningfully change?
- Did someone learn something that changes future behavior?
- Was a promise made, kept, or broken?
- Did a public and private dynamic diverge?
- Did the relationship enter a new state?
When the answer is yes:
- Update the canonical Relationship Profile.
- Create or update a specialized bond only when its structure is useful.
- Create an NPC Memory when a specific experience will shape behavior.
- Update World Pulse only with what remains immediately relevant.
Independent lives and relationships
NPC independence does not mean characters ignore relationships. Their obligations and next actions should be influenced by what they know, whom they care about, what they owe, and what they fear.
A character may refuse the player because they are protecting someone else. They may leave town because a family obligation matters more. They may act offscreen because a promise has reached its deadline.
That is the point of the system: not random independence, but motivated life beyond the protagonist.
Avoiding emotional clutter
The best emotional records are selective. One strong Memory with a clear behavioral effect is more useful than fifteen nearly identical notes saying the NPC felt sad.
Archive or resolve records that have finished their role. Preserve important history, but do not force the GM to retrieve every emotional beat ever written before a character can speak.