How to Bring Two Separate Solo RPG Character Stories Together Gradually

Keep each character’s story independent at first

Before linking the characters, write a one-sentence summary of what each is trying to do right now. Make the goals specific enough to generate scenes: Mira wants to deliver a repaired weather vane to a cliff village before the spring festival; Oren wants to map a safe route through the foothills. Neither goal requires the other character.

Add one current obstacle and one detail the character cares about. Mira’s obstacle might be a washed-out trail; she cares about the village’s handmade festival kites. Oren may be short on supplies and especially interested in old survey marks. These details give you material to echo later without rewriting either character’s motivation.

This separation matters because a crossover can otherwise take over both campaigns. A useful test is: if the connection disappeared, would each character still have a next scene? If the answer is no, the bridge has become the whole plot. Restore an independent immediate objective before continuing.

Choose a small shared anchor

Pick one element that can plausibly belong in both stories. Good anchors are portable or repeatable: a crest stamped on travel permits, a tune played in two settlements, a distinctive blue thread, an uncommon map symbol, or a recurring courier. Begin with a clue, not an explanation. Mira might find a strip of blue thread tied to a damaged kite; Oren might notice the same color knotted around a marker on his route.

The anchor should be visible in both stories but need not mean the same thing. A weathered brass sun symbol could be a festival decoration to one character and a surveyor’s mark to the other. That difference invites curiosity while leaving room for each character’s local context.

A practical limit: use one principal anchor at first. Introducing a secret society, a shared prophecy, three mysterious strangers, and a matching heirloom all at once can make coincidence feel like an answer already decided. If you use random prompts or oracles, treat results as raw material to interpret in light of the scenes already established. Ironsworn’s publisher describes its oracles as random tools for determining details and narrative events, with interpretation feeding results into the story and world already in play. Ironsworn RPG – Tomkin Press

Let the anchor recur with a different meaning

Use a three-step echo. First, one character encounters the anchor in an ordinary context. Second, the other encounters it somewhere else, with a detail that makes it recognizable. Third, a later scene changes what the anchor might mean. Keep each step separated by at least one scene focused on that character’s own goal.

For example, Mira repairs the kite and discovers the blue thread is tied in a knot she has seen on old festival banners. Later, Oren finds the same knot on a trail marker, but the marker points toward a disused lookout rather than the village. In a subsequent scene, Mira hears that a traveling mapmaker used the knot to mark safe places to shelter from sudden coastal winds. Now the connection can suggest a shared history of travel and craft without requiring that the characters meet immediately.

You can also let a result remain ambiguous. Perhaps Oren sees the blue thread but cannot tell whether it is the same material, or Mira hears an account that conflicts with Oren’s discovery. Keep the uncertainty in your notes instead of resolving it just to move faster. A connection is more useful when it creates a question each story can pursue on its own terms.

Alternate scenes instead of switching constantly

Choose a simple rhythm for playing the two threads: one scene for Character A, one for Character B, then decide whether either story has reached a natural pause. If you prefer longer sessions, play two or three scenes with one character before switching. The point is to make sure both threads advance, not to enforce equal word counts or identical scene lengths.

At the end of each scene, record three brief items: what changed, what remains unresolved, and what the character will try next. Keep separate notes for each character, plus a shared list of anchors and open questions. This prevents details from one thread from accidentally becoming knowledge the other character should already have.

A journaling solo RPG can offer useful examples of how different prompt structures shape play, but its procedure may not transfer directly to another game. For instance, Alone Among the Stars is presented by its creator as a tabletop roleplaying game using a standard deck of cards and a six-sided die, while Ironsworn: Delve offers quest tools, location material, and oracles for its own campaign context. Borrow the broad idea of prompts sparking scenes, not another game’s specific rules unless you are intentionally adapting them. Alone Among the Stars Ironsworn: Delve – Tomkin Press

Give each character a separate reason to follow the clue

When an anchor becomes important, ask what it means to each character locally. Mira might follow the knot because it could help her find a safe route for the festival delivery. Oren might investigate it because it marks a promising vantage point for his map. These motives can point toward the same place without making either character act out of character.

Write one next action for each person before deciding whether their paths converge. If both actions lead toward the old lookout, decide what each expects to find and what would still matter if the other person were absent. One may expect a shelter; the other may expect a survey record. Different expectations create a scene with its own choices rather than a meeting whose only purpose is to fulfill the crossover.

If only one character has a compelling reason to follow the clue, let that character act while the other continues their own story. The second character can encounter the consequences later: a newly repaired sign, a rumor, a route changed by a landslide, or an empty campsite. They do not need to chase the same mystery at the same pace.

Choose a meeting threshold, not a meeting date

Decide what needs to be true before you stage a direct meeting. A threshold might be: both characters have independently reached the same region; each has learned one useful fact about the shared anchor; or one character’s action has created a practical reason for the other to respond. This gives you a clear signal without scripting an exact scene too early.

When the threshold is met, play the arrival as a normal scene. Ask what each character is doing, what they notice first, and what immediate task brings them together. In the example, Mira arrives at the lookout looking for a dry place to repair a festival kite, while Oren is sketching its old survey marks. They may trade information, disagree about which path is safe, or simply share the shelter before continuing separately. The first meeting can be brief; it does not need to solve the whole connection.

You can also decide that the characters never meet. Their stories may still connect through an object passed along, a route improved by one person’s work, or a clue whose meaning becomes clearer in the other thread. A shared world is enough to make the narratives touch; a permanent party is not required.

Use a light tracking method to avoid continuity tangles

Keep a small crossover ledger with four headings: shared detail, who has seen it, what each believes, and what has been confirmed. Separate facts from guesses. For example, “blue thread appears on kite” is an observation; “same mapmaker made both knots” is a character’s theory until the game establishes it.

After each session, update only what changed. If an oracle or prompt gives you a new detail, first ask whether it can deepen an existing anchor or a character’s current goal. Add a second anchor only when the first has already generated a meaningful choice or consequence. This keeps the connection legible without needing a complicated conspiracy chart.

For conflicting information, preserve both accounts. Maybe the village says the lookout was abandoned decades ago, while Oren finds a fresh mark there. The mismatch can become a question for later play. Do not silently reconcile it in your notes; record what each character knows and allow a scene to establish whether one account is mistaken, incomplete, or describing a different thing.

A compact procedure for your next session

This approach keeps two solo RPG character stories recognizable as separate adventures while giving their shared details time to gather meaning. Start with a small echo, let each character respond for their own reasons, and allow the crossover to grow at the pace of the play.

Sources

Keep exploring this topic