How to Keep Split Character Storylines Connected Before They Converge
When a game follows characters in separate places, keep each storyline moving toward a shared situation while preserving what makes it personal. Before play, give every thread a clear goal, a visible change, and one connection to another character’s story. During play, track those connections and bring them back through shared clues, consequences, or choices. The result is a set of distinct arcs that can meet naturally, rather than a collection of unrelated scenes that collide only when the group needs to reunite.
Start with a shared situation, not a forced meeting
Choose one larger fictional situation that can matter to every character, even if each sees only part of it. A festival, a missing ship, a traveling exhibition, or a town preparing for a rare visitor can give different characters reasons to act without making them start in the same room. The shared situation is the connective frame; it does not have to be the characters’ shared goal.
For example, imagine a floating lantern festival whose final display has gone missing. One character is helping a craft maker finish a replacement; another is trying to find out why the harbor lights keep going dark; a third is following rumors about a lost song that once opened the festival. Their immediate tasks differ, but each can change what happens at the event. That gives the game a plausible meeting point without requiring any character to abandon their own purpose.
This distinction matters when characters have their own storylines. In the narrative design of Wayward Strand, the team mapped each character’s core stories, then looked for interactions between characters and between their stories. The designer describes these as distinct story layers, alongside ordinary day-to-day activity. That offers a useful model for a game group: keep the personal arc, shared interactions, and routine world details in view together. Game Developer: “Deep Dive: Narrative mapping and simultaneous storytelling in Wayward Strand”
Give each storyline a compact engine
Write one short line for each character’s thread: who wants what, what is in the way, and what changes if they act. A usable thread might be: “Mira wants the lantern maker to display her grandmother’s design, but the maker has lost the original pattern; if she finds a surviving sketch, the festival’s final display can include it.” This line is enough to make the next scene playable without scripting a full personal saga.
Then give the thread a near-term step. The next step should be something the character can attempt in the current session: ask the maker about the missing pattern, search the workshop, or compare designs at the festival archive. A small action lets the player make progress even if the group does not reach the convergence point soon. It also helps the facilitator know what scene to offer when that character’s turn comes around.
Keep the obstacle specific and playable. “Mira feels conflicted” is not a clear prompt for action by itself; “the only surviving sketch is in the locked festival display case” gives the player something to investigate or negotiate around. This is a practical design recommendation: a concrete obstacle makes the next scene easier to frame, while the emotional or thematic meaning can develop through the player’s choices.
Connect threads with shared details and consequences
Make links that can be noticed, interpreted, and acted on. A recurring symbol, a person who appears in two scenes, or a decision in one thread that changes another character’s circumstances can all connect the arcs. A connection is useful when it gives the characters something to discuss or do, rather than simply confirming that the facilitator planned everything in advance.
For the lantern festival example, the lost song might use the same three-note pattern as the harbor lights’ signal. The character investigating the lights can discover the pattern; the character searching for the song can recognize it; and the craft maker can explain that the old display used lanterns arranged to match those notes. Each clue adds a different piece of meaning. The players can compare what they know, then decide how they want to use it.
If an important connection is easy to miss, make it available through more than one route. In tabletop roleplaying advice, Justin Alexander’s Three Clue Rule recommends providing multiple clues for conclusions the players need to reach, so missing one clue does not stop progress. For a group story, the same idea can be adapted without turning every thread into a mystery: let the connection surface through a conversation, an object, or a consequence. Keep these options consistent with the fiction, and let players choose which lead to follow. The Alexandrian: “The Three Clue Rule”
Keep a simple thread-and-connection map
Use a small note with one row per character. Record the character’s goal, the next playable step, one detail linking the thread to another, and what would change if the character succeeds. This is a facilitator’s memory aid, not a script the players have to follow. It helps you spot a storyline that has gone quiet or a connection that exists only in your notes.
| Character | Current goal | Next playable step | Link to another thread | Possible change | |---|---|---|---|---| | Mira | Include her grandmother’s lantern design | Find the missing sketch | The sketch includes the harbor signal pattern | The festival display can use the design | | Sol | Learn why the harbor lights fail | Compare the signal with the lighthouse log | The pattern matches Mira’s sketch | The harbor can help guide the closing procession | | Tavi | Recover a song tied to the festival | Ask the retired musician about its notes | The song and signal share a three-note phrase | The final display can follow the song’s rhythm |
Treat the final column as possibilities, not guaranteed outcomes. The players may find another solution, reject the festival plan, or decide that a character’s personal goal matters more than the shared event. The map keeps options visible; it should not decide the characters’ choices for them.
Give each character room to matter
When you move between storylines, give each player a concrete opportunity to make a choice or change something. A short spotlight scene can show what that character wants, advance the thread, or reveal a consequence. Avoid measuring the value of a storyline by how much time it consumes; a focused scene can matter if it gives the player an actual decision.
Gnome Stew’s discussion of spotlight moments describes a scene focused on one player character, connecting that focus to the player’s contribution and interests. At the table, you can turn that idea into a simple check: before leaving a character’s scene, ask what the character decided, learned, or changed. If the answer is “nothing,” consider whether the scene needs a clearer choice or can be shortened. Gnome Stew: “GMing 142: Spotlight Moments”
If the group is playing characters in separate locations, agree on a comfortable rhythm for switching scenes. You might move to another thread after a meaningful action, a new question, or a natural pause. Let players know when their character is temporarily offscreen, and give them a way to stay engaged as listeners or collaborators if they want. The exact rhythm depends on the group and game; there is no universal scene length that guarantees everyone will enjoy the session.
Build convergence from what the characters do
A convergence feels earned when the characters’ separate actions create the conditions for meeting or working together. It does not need to mean that every character has the same goal. One may bring a clue, another a practical solution, and another a reason to question the plan. Let each contribution affect the shared scene.
In the festival example, Mira finds the sketch, Sol discovers the harbor signal is failing because a lantern has been moved, and Tavi learns the old song’s final verse describes the route of the closing procession. The characters can meet at the display workshop because their separate discoveries now concern the same practical problem. They still have different reasons to care about the outcome, and those differences can shape the scene.
Game Developer’s account of Wayward Strand describes how the team organized character storylines across in-game days and added ways for characters to interact with one another’s stories. GDC’s session on sub-narratives similarly focuses on making smaller narrative arcs contribute to the larger game world. Together these examples support a useful design principle: keep a thread focused, then connect it through meaningful interaction with the surrounding story. They do not imply that every game needs a fixed convergence schedule or the same structure. Game Developer: “Deep Dive: Narrative mapping and simultaneous storytelling in Wayward Strand” and GDC Vault: “Parallel Worlds: The Mysterious Art of the Sub-Narrative”
Use a recap to carry connections between sessions
At the end of a session, note one sentence for each active thread: what changed, what remains open, and who else might care. Keep the wording concrete: “Sol found the displaced lantern, but the lighthouse log shows the same signal failed last year.” At the next session, recap the shared facts briefly and ask the players what their characters want to pursue. This helps preserve continuity without requiring players to remember every detail from a long gap between games.
A recap should describe what happened, not prescribe the next move. If the players have multiple leads, state them plainly and leave the choice open. If a storyline is paused, note the last actionable question so it can be resumed without inventing a new crisis just to make it feel active. Threads can also resolve or change direction; a connection map should be updated when play changes the story.
Check whether a thread is ready to converge
Before bringing the characters together, ask three questions: Does each character still have a reason to care? Has each thread produced something that can affect the shared situation? Is there a believable reason for the characters to meet, exchange information, or act in the same scene? If one answer is missing, add a playable step or let the characters’ choices create the link during play.
Convergence can be a meeting, but it can also be an exchange of letters, a shared performance, a coordinated plan, or the realization that two characters have changed the same place in different ways. Keep the threads distinct long enough for their differences to matter. Then let the players decide what they combine, what they leave separate, and what comes next. The goal is not to make every arc identical; it is to make the connections visible enough that the group can choose to follow them.