Learning how to run a co-op campaign when players miss sessions is one of the most practical skills a tabletop RPG game master can build. Most groups of 4 to 6 players lose at least one person to scheduling conflicts almost every week, and unprepared campaigns stall, frustrate the present players, and quietly dissolve.
I have run campaigns where we played with 3 of 6 players for a month straight, and I have lost entire groups because I had no plan when attendance slipped. This guide covers the 6 solutions that actually work in play, how to choose between them, and the fairness, balancing, and async engagement questions most guides skip.
You will leave with a comparison table of every approach, a D6 table of ready-to-use in-character excuses, a session zero attendance script, and concrete encounter math for when you are short on players.
Table of Contents
Quick reference: 6 solutions to missing players at a glance
Use this table when you have 5 minutes before a session and need to decide what to do. Each approach is rated for group size, campaign type, and how much trust it requires.
| Solution | Best for group size | Best for campaign type | Trust required | Effort for DM |
|---|---|---|---|---|
| Passive tag-along | 4+ players present | Plot-driven or sandbox | Low | Low |
| Leave character behind (in-game excuse) | 3+ players present | Player-driven, hex crawl | Medium | Medium |
| Another player runs the absent character | 4+ players present | Any, with established group | High | Low |
| DM runs the absent character as an NPC | Any size | Plot-driven modules | High | High |
| Cancel the session | Below 3 players | Any | Low | None |
| Run a one-shot instead | Any size, 2+ players | Flexible | Low | Medium |
Pick the row that matches your situation, then jump to the detailed section below.
Plot-driven vs player-driven campaigns: which framework are you running?
Plot-driven and player-driven campaigns handle missing players in completely different ways, and naming your campaign style is the fastest decision you can make.
A plot-driven campaign is a linear TTRPG storyline with a clear sequence of events, scripted encounters, and an expected next beat. A player-driven campaign is a sandbox, hex crawl, or open-world TTRPG where the players choose where to go next.
If you run a plot-driven D&D module like Curse of Strahd or Tomb of Annihilation, the absent character cannot easily leave the party mid-dungeon without breaking the story. Passive tag-along or another player running the character works best. If you run a sandbox or hex crawl, the absent character has plausible reasons to wander off, so leaving them behind with an in-game excuse feels natural.
Our team has found that plot-driven campaigns are more sensitive to absences because the GM has prepped a specific scene. Player-driven campaigns are more forgiving because the players generate the agenda and the absent character can simply not be in the room.
6 proven solutions when players miss sessions
These are the 6 strategies the TTRPG community keeps returning to, refined from the most cited sources and tested in actual play. I have used all 6 in campaigns ranging from 2 to 7 players.
1. Passive tag-along: the character is present but inactive
The passive tag-along is the easiest solution and works for almost any co-op campaign. The absent character stands in the scene, takes part in the dialogue when needed, but does not roll initiative or make tactical decisions. The DM avoids targeting them in combat and does not let NPCs or monsters attack them unless unavoidable.
This approach shines when you have 4 or more players present, when the absent character is a support or spellcaster role, and when the player wants their character to keep gaining XP and story beats. The downside is that it can feel like a free pass if you do not communicate it well, and combat scaling still matters.
2. Leave the character behind with an in-game excuse
The character stays in town, runs a side errand, or gets separated by a plot device. You generate or ask the player to generate an in-fiction reason they are not present.
This works beautifully in player-driven campaigns, hex crawls, and West Marches games where characters regularly split up. It does not work as well in a tightly scripted dungeon because the absent player will not have narrative reasons to return.
My favorite excuse generator is a simple D6 roll the absent player or DM makes before the session.
| D6 result | In-character excuse |
|---|---|
| 1 | A mysterious fog rolls in and separates the party; the missing character is found later, disoriented. |
| 2 | The character is struck by a sudden bout of magical shrunken sleep and curls up in a pack. |
| 3 | A long-lost relative arrives with urgent news and the character steps away to handle it. |
| 4 | The character is tracking a personal quest hook and asks the party to continue without them. |
| 5 | The local temple calls the character in for a vision quest that cannot wait. |
| 6 | A bounty is finally collected; the character must escort a prisoner to the next town. |
3. Another player runs the absent character
Hand the character sheet to a trusted player at the table. They make the same decisions the absent player would, using the same alignment, class features, and personality notes. The absent player keeps ownership and reviews the recap later.
This is a high-trust approach that works best in groups that have played together for months. It preserves combat balance and keeps story momentum. The risk is that the controlling player makes choices the absent player would not, which can create resentment on both sides. Always get explicit consent from the absent player first.
4. The DM runs the absent character as an NPC
The DM controls the absent character as a follower NPC, making tactical choices that preserve party balance. This is the default in many D&D Adventurers League games for a reason – it is reliable.
The cost is DM cognitive load and the loss of player agency. Present players sometimes resent the DM piloting a character better than they could. It also steals screen time from the NPCs the DM should be running. Use this only when consent is clear and the absent character is non-complex.
5. Cancel the session
Sometimes the right answer is to skip the week. If you have fewer than 3 players, no one is in the mood, or the scene you prepped requires the missing player to work, cancel without guilt.
Our team uses a simple rule: if we drop below 3 players, the GM runs a one-shot or skips. If we have exactly 3, we play if the absent player is the same one missing last session and the campaign can absorb it. This protects the DM from burnout and protects the present players from a slow, awkward session.
6. Run a one-shot instead
If you have 2 to 4 players and the missing player is not coming back, swap the campaign for a one-shot. One-shots are designed for irregular groups and let the present players experiment with new characters without affecting the main campaign.
This is also the right move when the DM is burned out on prep. You can pull a one-shot from a published anthology, a community jam, or a 4-hour module. The main campaign simply pauses for one session.
Group size matters: when to cancel vs continue
The threshold question comes down to numbers, and most groups settle into a pattern quickly. With 5 or 6 players present, you can absorb 1 to 2 absences easily. With 4 players present, 1 absence is fine but 2 absences hurt. With 3 players, every combat gets harder to balance and every social scene loses variety. With 2 players, the session is closer to a duet than a co-op campaign.
For 2-player TTRPG sessions, lean into rules-lite systems designed for duets, or use a sidekick NPC controlled by the DM. Many popular D&D starter set adventures work fine at 2 players if you slow the pace and increase NPC depth.
For 3-player sessions, scale encounters down by removing 2 to 3 minions from each combat and reducing monster HP by 25 percent. For 4-player sessions with 1 missing, you usually do not need to scale at all.
The fairness concern: present players vs absent players
The single biggest tension I see in TTRPG forums is the fairness dynamic. Present players sometimes feel they are doing extra work – splitting XP, sharing loot decisions with someone who was not there, watching the DM run a character they could have played – while absent players keep the same level of XP and narrative power.
There is no perfect answer, but two habits help. First, ask the table openly what they prefer. Some groups are happy to keep XP parity; others want absent players to skip XP and treasure for sessions they missed. Second, do not invent elaborate in-fiction rewards for absent players without checking with present players first. The Reddit thread that surfaced this concern showed the OP stopped making up reasons because it broke immersion for the people who showed up.
Trust and consent are the foundation. A 2-minute conversation at session zero removes 90 percent of this resentment.
Managing recurring absences for long-term unreliable players
Most guides assume an occasional miss. The harder problem is the player who misses every other session for 6 months. The co-op campaign still has to function, and the rest of the group cannot wait forever.
Three approaches work. First, run a parallel one-shot campaign on the off-weeks so the reliable players always have a game. Second, demote the recurring absentee to a guest character role with their own subplot that can come and go without blocking the main story. Third, if the absences are due to a real-life situation like a new baby or a hard job, simply pause their character progression until they return, and protect their spot.
Whatever you do, set a clear expectation at session zero. I have found that saying “we expect you to be at 70 percent of sessions and we will design the campaign around that” works better than vague hope.
Setting expectations at session zero
Session zero is the pre-campaign meeting where the group agrees on rules, tone, and logistics. The single most useful thing you can add to your session zero is an explicit attendance conversation.
Ask each player to commit to a percentage of sessions – 75 percent is a common target. Ask what counts as an acceptable reason for absence. Ask whether the group is okay with passive tag-along or another player running a character. Ask how to handle XP and loot when someone misses. Write the answers down and revisit at session 5.
A 5-minute conversation here saves you 5 sessions of resentment later.
Encounter and XP balancing with fewer players
When players miss, encounters become harder relative to party size. A quick scaling formula: remove 2 minions per absent player, reduce remaining monster HP by 15 percent per absent player, and cap single monsters at the next-lowest difficulty tier.
For XP parity, two camps exist. Camp A gives full XP and loot to absent characters so they do not fall behind. Camp B gives half XP and no loot, since the absent player was not present to advocate for treasure. Both are valid; just pick one and announce it.
For leveling, avoid milestone-only systems if your group is irregular, because the absent player will often hit the same milestones as the present ones and the present players feel skipped. Mixed XP and milestone tends to feel fairest.
Async tools for keeping absent players engaged
The biggest gap in most TTRPG guides is what happens between sessions. A short Discord recap, a shared Notion page, or a 5-minute voice memo from the DM keeps the absent player in the loop and dramatically reduces their feeling of being lost.
Our team writes a 200-word recap after every session and posts it to a private channel the absent player can read. Some groups record sessions and post them to YouTube unlisted. Others run short async scenes via text – “while you were away, did you want to pursue the side quest about the missing sister, yes or no?” – and resolve them between sessions.
The point is not to recreate the session. The point is to keep the absent player feeling like part of the co-op campaign instead of an outsider catching up.
FAQs
Can you run a 2 person Du0026amp;D campaign?
Yes, you can run a 2 person Du0026amp;D campaign with adjustments. Use rules-lite variants designed for duets, give each player a sidekick NPC, scale encounters down by 40 to 50 percent, and lean into social and exploration scenes over combat. The Du0026amp;D Starter Set works at 2 players if you slow the pace and add NPC depth.
Is 2 players too little for Du0026amp;D?
Two players is workable for Du0026amp;D but is below the typical sweet spot. Most published adventures assume 3 to 5 players, so you will need to scale encounters down significantly and may want to use a duet-style ruleset instead of standard 5e. It is not too little – it just requires the GM to do more balancing work.
Should I cancel a Du0026amp;D session if a player is missing?
Cancel a Du0026amp;D session if you have fewer than 3 players, if the missing player is critical to the scene you prepped, or if you do not have a one-shot ready to fill the time. With 3 to 5 players present, continue using passive tag-along, an in-game excuse, or another player running the absent character.
Is it fair to give absent players the same XP as present players?
It is fair to give absent players the same XP if the group agrees to it at session zero. Some groups prefer full parity so absent players do not fall behind; others prefer half XP and no loot because absent players were not there to advocate for treasure. The fairness comes from consent, not from a single right answer.
Do one-shots need a session zero?
One-shots do not need a full session zero, but a 5-minute conversation about attendance expectations, character handoff if a player misses, and how to run one-shots in parallel to a main campaign is helpful. Session zero is most useful when a co-op campaign is forming; for a single one-shot, a quick chat is enough.
Final thoughts on running a co-op campaign with irregular attendance
The most important step in learning how to run a co-op campaign when players miss sessions is to pick your default approach before you need it. Decide now whether you will use passive tag-along, in-game excuses, or one-shots as your go-to. Decide your XP and loot policy. Decide your minimum group size. Then write it down at session zero so nobody is guessing in the moment.
With a clear default, a fair XP policy, and the 6 solutions above in your back pocket, your TTRPG group can survive almost any attendance pattern and still feel like a real co-op campaign.