How to Connect Two Player Characters’ Goals Without Making Them Identical
When two player characters want different things, connect the route they take rather than replacing either destination. Give them a shared situation, a reason each needs the other’s help, and separate outcomes that still matter to each character. This approach creates scenes where the characters cooperate, make distinct choices, and can change their relationship through play.
Start by separating the goal from the reason
Write each character’s goal as a concrete outcome: “map the old observatory” or “restore the village’s annual lantern festival.” Then add the personal reason that makes it matter. One character might want the observatory’s star charts to improve their navigation; another might hope its records identify the artisan who designed the festival’s lanterns. The characters can want different things from the same place.
Keep these two layers separate. A goal answers, “What does my character want to accomplish?” The reason answers, “Why does this outcome matter to them?” If you make the characters’ goals identical, they may sound like one character with two names. If you connect only their reasons, they may have no practical reason to share scenes. A useful link lets their immediate actions overlap while preserving their own stakes.
Find a shared point of contact
Look for one person, place, object, event, or obstacle that already fits both goals. In the observatory example, both characters need access to the building, but they may be interested in different rooms or records. A caretaker might agree to unlock it if the characters help prepare for a public star-viewing night. That gives them a common first task without requiring them to agree on what to do afterward.
Keep the shared point specific enough to put into a scene. “They both care about history” is broad; “the observatory’s opening day gives both a chance to find a useful record” suggests an action the group can play. Advice on backstories from D&D Beyond similarly recommends leaving room for other players and the game master to connect character stories, rather than filling every detail in advance. Roleplaying 101: Building a Backstory
Give each character a different contribution
Ask what each character can do that moves the shared situation forward. One might know how to read a hand-drawn star chart; the other might know how to organize a welcoming public event. This need not mean assigning a formal specialty. It can be a difference in knowledge, resources, relationships, or the kind of choice a character is willing to make.
Then make sure both contributions lead to meaningful decisions. If one character handles every obstacle while the other waits for their goal to come up, the connection is mostly in the backstory. Instead, create beats where one character opens an opportunity and the other decides what to do with it. For example, the chart reader finds a locked archive, while the festival organizer learns the caretaker has promised the room to another group. Each now has a reason to negotiate, improvise, or offer a compromise.
A useful check is to ask each player: “What can your character do in the next scene that matters to both goals?” If only one player has an answer, add a choice or resource for the other character. If both give the same answer, distinguish their methods or the costs they are willing to accept.
Build a bridge, not a merger
A shared goal can be temporary. The characters might both want the archive opened, but for different reasons; once it is open, they can pursue separate discoveries. Or their aims may overlap in stages: first gain access, then find the chart, then decide whether to copy it for public use or keep it for private study. Each stage creates a point to act together and a point where their priorities can diverge.
For a practical design, write three lines: “We both need .” “My character will contribute .” “After that, I still want .” For example: “We both need the caretaker’s permission. My character will help prepare the viewing night. After that, I still want to copy the chart for my own travels.” Have the other player complete their own version. The bridge is the first line; the distinct goals live in the last line.
This distinction helps avoid making cooperation depend on one character abandoning their objective. D&D Beyond’s guidance on character relationships describes shared bonds and events as ways characters come to have reasons to stay together. The practical extension here is to let a common reason for cooperation coexist with separate personal aims. New Player’s Guide: Character Relationships
Add a relationship question
Connect the goals to a question the characters can answer through interaction: “Will you trust my character with the original chart?” “Will you help me make the festival open to newcomers?” “What do you think I should do with what we find?” These questions give the players something to explore together, without dictating that the characters must become friends, agree, or change in a particular way.
Keep the relationship detail small and open. “You owe me your loyalty forever” tries to settle the future in advance. “You promised to show me the first map you draw from the chart” creates a specific expectation the characters can revisit. The Dungeon World rules use bonds as statements relating one player character to another and describe replacing them as play changes the relationship. That offers a useful model for treating a connection as something that can develop rather than a permanent script. Playing the Game — Dungeon World
Turn different priorities into choices
If the goals never pull in different directions, the connection may feel decorative. Add a choice that lets both characters express what they value. The archive might contain a chart that can be copied only once before the caretaker closes the room. One character wants to preserve the original; the other needs an accurate copy. They can propose taking turns, ask for more time, or accept that one aim will wait. The purpose is not to force conflict; it is to give the players a decision with more than one reasonable answer.
Agree on the scale of the disagreement before play if it could affect another player’s enjoyment. A useful fictional disagreement concerns approaches or priorities: preserve a record or share it, prepare carefully or act now. Avoid turning a character’s goal into permission to control another character or derail the group’s adventure. In Fate, a compel can introduce a complication related to an aspect, but the rules include negotiation and a way for the affected player to prevent the complication. That is a system-specific procedure, not a universal rule; the broader lesson is to make complications discussable and grounded in the character’s established material. Invoking & Compelling Aspects — Fate Core
Check that the link works in play
Before the session, test the connection with three questions: Can both characters take an action in the next scene? Does each have a personal reason to care about the result? Can the characters disagree about what to do without one player’s character making the other irrelevant? If an answer is no, adjust the shared situation, not necessarily the characters’ goals.
Also give the connection an exit or a next step. When the immediate shared problem is solved, the characters might exchange a promise, discover a second lead, or decide to work together again for a new reason. They may also part ways for a while. A connection that needs constant emergency coincidence to keep the characters together is harder to use than one that gives each character a clear reason to choose cooperation again.
A worked example: the lantern festival
Mira wants to restore a lantern festival using its original designs. Rowan wants to chart the seasonal stars from the old observatory. Both goals point to the same town archive, where the observatory’s records and a bundle of festival plans are stored. The archive is closed while the caretaker prepares a public viewing night.
Their immediate shared need is permission to use the archive. Mira offers to help prepare the lantern display; Rowan offers to explain the star chart for the event. Once inside, they discover only one set of plans can be carried to the viewing room at a time. Mira wants to check the festival designs; Rowan wants the chart before the stars become visible. They can divide the work, ask the caretaker for extra time, or choose which task comes first.
The goals remain distinct: Mira can still restore the festival even if Rowan has already made a star chart, and Rowan’s navigation goal does not depend on Mira caring about astronomy. Their connection comes from shared access, complementary contributions, and choices that affect both. If the players want another link after this scene, they can decide whether they made a promise, learned something about one another’s priorities, or simply found a useful way to work together.
Connecting two characters’ goals works best when the shared situation creates cooperation and each character’s own goal still points toward a different meaningful outcome. Start with one overlap, give both characters something to contribute, and leave room for their relationship and priorities to develop through play.