The A-plot is what the episode is “about” on paper. The ship encounters a spatial anomaly. A colony needs evacuation. A diplomatic summit goes wrong. A lost probe returns with impossible data. Romulans appear near the border.

The B-plot is what the episode is really about emotionally. Data tries to understand humor. Worf struggles with fatherhood. Bashir and O’Brien argue over something small that becomes something meaningful. T’Pol wrestles with a human custom. Seven tries to navigate individuality. A junior officer makes a mistake and has to regain confidence.

The B-plot gives the episode texture. It gives the characters room to breathe. It reminds us that Starfleet officers are not just problem-solving machines in uniforms. They are people, with friendships, rivalries, doubts, ambitions, private rituals, and small troubles that sometimes reveal who they really are.

In Star Trek Adventures, the B-plot can be one of your best tools for making a mission feel like an actual episode of Star Trek.

What Is a B-Plot?

A B-plot is a secondary storyline that runs alongside the main mission. It should not be as large as the primary conflict. It should not compete with the main plot for attention. It should not derail the mission.

Instead, it should do one of three things:

• It should reveal character.
• It should reinforce the theme of the episode.
• It should create a small complication that pays off later.

For example, if the A-plot is about first contact with a species that communicates through ritualized silence, the B-plot might involve a talkative ensign trying to learn when not to speak.

If the A-plot is about a damaged ship that refuses to abandon its mission, the B-plot might involve the chief engineer refusing to take medical leave. If the A-plot is about two alien factions that cannot forgive an old betrayal, the B-plot might involve two player characters dealing with a disagreement from a previous session. The key is that the B-plot should echo the mission without simply copying it. A good B-plot does a lot of work at the table.

First, it gives quieter characters a chance to shine. Not every player is going to be at the center of every mission. A tactical crisis may naturally favor the captain, security chief, and conn officer. A medical mystery may heavily involve the doctor and science officer. A diplomatic mission may spotlight command and social characters. The B-plot lets you give attention to someone else without forcing the main plot to become something it is not.

Second, it makes the ship feel alive. Star Trek episodes are full of small shipboard problems. A recital. A promotion. A poker game. A holodeck program. A crew evaluation. A strange new pet. A repair that should have been simple. These small details make the ship feel like a community.

Third, it gives characters somewhere to spend their Values. A B-plot is often a perfect place to challenge a Value in a lower-stakes way before the main plot puts that same Value under pressure.

A character with “The Needs of the Many Come First” might begin the episode by skipping a personal celebration because duty calls. Later, that same instinct may be tested when the main mission asks them to sacrifice one group to save another.

A character with “There Is Always Another Way” might start by trying to reconcile two feuding crew members. Later, they may need to find a third option in a diplomatic crisis. The B-plot prepares the emotional ground.

The biggest mistake with a B-plot is making it too large. A B-plot should usually be playable in three to five short scenes across the mission. Some of those scenes may only take a few minutes.

A good structure looks like this:

Scene One: Introduce the B-plot.
A problem, question, or character issue appears before or during the mission briefing.

Scene Two: Complicate it.
The problem becomes more difficult, more personal, or more connected to the main mission.

Scene Three: Pay it off.
The character makes a choice, changes their perspective, or uses what they learned to help resolve the main plot.

That’s enough.

You don’t need a full subplot with its own villain, mystery, and climax. You need a thread. Something the players can notice, tug on, and eventually tie into the larger story

Step One: Choose a Focus Character

Pick one player character, one relationship, or one part of the ship. Don’t try to give everyone a B-plot in the same session. That becomes too much. Rotate the spotlight over multiple adventures.

Good focuses include:

• The captain’s relationship with command.
• The doctor’s bedside manner.
• The engineer’s attachment to the ship.
• The security chief’s distrust of outsiders.
• The science officer’s curiosity.
• The conn officer’s need to prove themselves.
• A friendship between two player characters.
• A recurring junior officer.

Step Two: Pick a Question

A B-plot should ask a small question.

• Will the character apologize?
• Will they trust the ensign?
• Will they take the night off?
• Will they admit they are afraid?
• Will they break a rule for a good reason?
• Will they accept help?
• Will they change their mind?

This question gives the subplot direction.

Step Three: Connect It to the Episode Theme

Look at the A-plot and find a parallel.

• If the main plot is about loyalty, make the B-plot about loyalty.
• If the main plot is about identity, make the B-plot about identity.
• If the main plot is about sacrifice, make the B-plot about sacrifice.
• If the main plot is about communication, make the B-plot about communication.

This doesn’t need to be subtle at first. With practice, you can make the connection more elegant. At the table, clarity is usually better than cleverness.

Step Four: Give It Three Beats

Plan three moments.

• Opening beat: introduce the issue.
• Middle beat: make it more complicated.
• Final beat: give the character a choice.

For example:

Focus: The chief engineer.
Question: Can they delegate?
Theme: Trust.
A-Plot: The ship must cooperate with an unreliable alien vessel to escape a gravimetric trap.

• Opening beat: The engineer snaps at a junior officer for making a harmless mistake.
• Middle beat: The alien vessel offers a risky solution that requires the engineer to let the junior officer coordinate part of the repair.
• Final beat: The engineer must choose whether to micromanage or trust the team.

That is a complete B-plot.

Step Five: Let the Players Surprise You

The player may not make the choice you expect. They may turn the B-plot into a joke, a serious character moment, or an unexpected connection to the main story. That is good. Your job is not to force the B-plot to land exactly as planned. Your job is to place a meaningful thread in front of the players and see what they do with it.

A Ready-to-Use B-Plot Table

Roll or choose one when preparing your next mission.

d20	B-Plot
1	A junior officer is up for promotion and wants advice from the worst possible senior officer.
2	A cultural celebration is scheduled during the mission, and canceling it would deeply offend part of the crew.
3	Two departments are feuding over limited resources, lab time, or repair priority.
4	A player character receives a personal message they do not want to answer.
5	A holodeck program reveals something uncomfortable about its creator.
6	A visiting specialist is brilliant, necessary, and impossible to work with.
7	A crew member’s pet, plant, or personal project becomes relevant to the mission.
8	A recurring NPC makes a mistake and tries to hide it.
9	A character is asked to mentor someone who reminds them of their younger self.
10	The ship is preparing for an inspection, ceremony, or formal dinner at the worst possible time.
11	A harmless superstition spreads through the lower decks.
12	A crew member wants to transfer off the ship, and someone takes it personally.
13	A player character is nominated for an award they do not believe they deserve.
14	A routine training exercise becomes emotionally revealing.
15	A replicator, turbolift, or computer glitch inconveniences exactly the wrong people.
16	A civilian passenger misunderstands Starfleet protocol and causes trouble.
17	Two characters disagree about how to handle a minor disciplinary issue.
18	A character’s hobby unexpectedly becomes useful.
19	A crew member from a former enemy culture faces quiet prejudice aboard the ship.
20	Someone plans a surprise party, but keeping it secret looks suspicious during the main mission.

B-plots are one of the easiest ways to make Star Trek Adventures feel more like Star Trek.

They give the crew lives beyond the viewscreen. They turn the ship into a community. They let Values breathe outside of crisis. They create space for humor, warmth, vulnerability, and growth.

Most of all, they remind us that the mission is never just about the anomaly, the treaty, the planet, or the distress call. It is about the people who answer: The ones on the bridge, the ones below decks, the ones still learning who they are, and the ones who, together, make a starship feel like home.