Trust should be specific
Generic approval turns every relationship into the same optimization puzzle. Specific milestones are stronger: the player protected a source, kept a painful promise or exposed a companion's secret in public.
A visible bond level can summarize direction, while remembered events explain why the relationship moved.
Disagreement is a form of care
Companions who always approve do not feel autonomous. A trusted ally may challenge a reckless plan, request a different approach or refuse to harm people connected to their past.
The game should distinguish principled disagreement from random obstruction. Values and current knowledge make a refusal legible.
Relationships should affect play
Trust can unlock coordinated abilities, honest warnings and personal knowledge. Broken trust can close those paths, alter camp conversations or cause departure. Injuries and sacrifices can create lasting changes without requiring every dramatic scene to end in death.
Romantic content, when present, needs explicit boundaries and the ability to change them without punishing the player.
Continuity creates attachment
A relationship matters more when it survives chapters and Seasons. The companion who remembers an early failure can reinterpret a later victory, making progression emotional as well as numerical.
Living Party stores relationship milestones and private companion knowledge alongside campaign state, allowing the same party to develop across the base expedition and later Seasons.
Frequently asked questions
Should RPG companions have approval meters?
A meter can summarize the relationship, but specific remembered events and behavioral consequences are necessary to make it meaningful.
Can a companion refuse the player?
Yes. Refusal feels fair when it follows established values, knowledge and relationship history.
Can AI companions keep secrets?
They can when the system stores private knowledge separately and prevents the Game Master or other companions from exposing it accidentally.