How to run a campaign with friends who can never make the same night

Scheduling kills more campaigns than any villain

Ask anyone who has run a long tabletop campaign what ended it. It is almost never a boss fight or a party wipe. It is that Sara got a night shift, Marcus had a second kid, and the group chat where you used to plan sessions slowly turned into a graveyard of “next week?” messages nobody answers. The people did not lose interest in the story. They lost the one shared evening the story needed to exist.

This gets worse with age and with distance. A table of college friends can meet weekly. The same five people a decade later, spread across three time zones with jobs and kids and partners, cannot. The math of “everyone free at the same time for four hours” only gets harder every year, and no amount of enthusiasm fixes a structural problem. If the format demands synchrony, the format is going to lose to real life.

The classic fixes, and where they actually break

People have been working around this for a long time, and the workarounds are worth understanding before you reach for a new one, because each solves part of the problem and leaves part of it standing.

• Shared calendars and scheduling tools. Doodle polls, when2meet, a pinned availability sheet. These help you find the least-bad night faster, which is real. But they do not remove the requirement for a night. You still need a block of hours where everyone is present and awake, and if that block does not exist, a better poll will not conjure it.
• Play by post over forums or Discord. This is the honest old answer, and it genuinely works. People have run years-long play by post games in forum threads. Each player writes their move when they have ten free minutes, and nobody has to be online together. The catch is bookkeeping. The world lives in everyone's memory and in a human organizer's notes. Someone has to track who has what, which door is still locked, what the rival faction is doing this week. Threads drift. Two players remember the same scene differently. And the whole thing runs on one person's unpaid labor, so it stalls the moment that organizer burns out or gets busy, which is exactly the same fragility that killed the weekly table.

So the async idea is not new. Play by post already proved that people will happily take turns on their own time. What it never solved was the bookkeeping. Somebody always had to be the memory of the world, and that somebody was a volunteer with a life.

The newer option: an async shared world with an AI Narrator

Here is the shift. Keep the part of play by post that works, which is that each player takes their turn whenever suits them. Remove the part that breaks, which is that a tired human has to hold the entire world in their head between turns. Instead of a person tracking state, an AI game master runs the world and keeps a standing record of it, so the world is already caught up and consistent no matter who logs in next or how many hours passed since the last move.

Creation OS calls this Shared Worlds, and the shape of it is simple. Up to six players share one campaign. Each person has their own character, their own name, their own inventory and standing. You play on your own schedule. When you take an action, it persists: the door you kicked open stays open, the merchant you insulted still remembers it, and it is all there when the next player logs in three hours or three days later. Nobody has to be the bookkeeper, because the bookkeeping is just how the world works now.

That last point is the one that matters for a group that can never sync up. In a live session, missing a night means missing the story. In an async shared world, there is no night to miss. The world keeps score between turns, so “I was away for a week” is not a catastrophe. You come back, read what changed, and take your move. The persistence here is not a marketing flourish either. It has been verified past turn 5,000 in a single continuous world, which is far longer than most tables ever last.

And if the group thins out for a while, the same world runs solo. It is the same engine for one player as for six, so a quiet stretch where only you are around does not mean the campaign sits frozen. You can keep playing your own thread and the others rejoin where they left off.

How to actually set one up and keep it alive

An async campaign fails in different ways than a scheduled one. It does not die from a missed night. It dies from vagueness, from a group that never establishes a rhythm and quietly drifts. A few habits keep it healthy.

• Set a cadence, not a schedule. Do not say “we play Thursdays.” Say “everyone tries to take at least one turn a week.” That is a floor, not an appointment. Some players will move daily, some weekly, and the world absorbs both because it is not waiting on a room full of people.
• Lean on the recap. When you log in after a gap, get a light “here is what happened while you were gone” before you act. Because the world kept a standing record, that catch-up is quick and reliable, and you are never guessing at what changed.
• Keep the stakes survivable. A slow week should not be able to kill the campaign. Avoid setting up situations that only make sense if everyone acts within hours. Let the plot breathe on a scale of days, so a busy stretch for one player is a pause, not a collapse.
• Let people arrive and drift without guilt. The whole point of the format is that it forgives absence. If someone goes quiet for a fortnight, the world is still there when they come back. Design the social side around that instead of fighting it.

An honest note on what you trade away

I will not pretend async is a perfect substitute for the real thing. It is not the same buzz as five people crammed around a table, all laughing at the same bad dice roll in the same second. That electric, in-the-room energy is genuinely lost, and if your group can still make a weekly night work, keep making it work. Nothing here beats that.

But most groups cannot make the night work, and the real choice is not async versus a perfect table. It is async versus the campaign quietly dying in a silent group chat. Async is the format that survives adult schedules, night shifts, new babies, and eight-hour time-zone gaps. It trades the shared-room high for the thing that actually keeps a story going: the ability for everyone to keep playing without ever needing to be in the same place at the same time. For a lot of us, that is the only version of the campaign that gets to keep existing.