Store what two player characters share without mixing up who feels what

Ana saved Bo's life, Bo hardly noticed, and the game has to say two different things when each one talks to the other. Here is how to keep the shared past in one place and each person's feeling in its own, and the key mistake that mixes up two pairs.

Why this works

What happened between two people is one fact, but how each feels about it is two. Keeping the shared past in a single place and the feelings apart means each character speaks from what they themselves would know, and no pair is confused with another.

When not to use it

Skip it when relationships are not a theme of the game, or when characters only have a single standing with the whole town. A simple score per faction is easier to keep and enough there.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 25 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Store what two player characters share without mixing up who feels what" (read_entry online-pair-history-between-two-player-characters) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP