Asynchronous Multiplayer Games for Friends on Different Clocks

My oldest gaming group has five people in it. Two live in Manchester, one moved to Lisbon, one works nights as a nurse, and one has twins under four. For about eighteen months our group chat was a graveyard of "anyone on tonight?" messages followed by silence. We were not drifting apart as friends. We simply could not get five bodies in front of five screens at the same moment.

What saved the group was not a better scheduling app. It was switching a good share of our play to games that never needed us online together in the first place. Asynchronous multiplayer, where each person takes their turn whenever they have a spare ten minutes, sounds like a consolation prize. In practice it became the main way we play, and the live sessions became the occasional treat.

Why live sessions get harder with every person you add

Here is a rough piece of arithmetic that explained our failure better than any excuse. Suppose each of five friends is free on three evenings out of seven, picked more or less at random by work and family. The chance that all five are free on a given evening is three sevenths multiplied by itself five times, which comes to about 1.4 percent. Over a whole week, you would expect a shared free evening roughly once every ten weeks.

Real life is not random, of course. Some evenings are reliably freer than others, which improves the odds. Time zones push them back down: Lisbon sits an hour ahead of Manchester most of the year, and our friend who briefly moved to Seattle sat eight hours behind. Night shifts scramble the picture further. The number is crude, but it matches the feel of that dead group chat almost exactly.

Every extra player multiplies the problem instead of adding to it. That is why a duo can keep a weekly session going for years while a group of five quietly stops playing by month three.

The fixed game night is not the only fix

The standard advice is to lock in a regular night and protect it. I am not against that. My own tips for playing with friends lean on it heavily, and for people in one city with predictable jobs it works well.

It fails in two specific situations. The first is shift work, where "every Thursday" is meaningless because the rota changes monthly. The second is a group spread across time zones, where any fixed hour is late for someone and early for someone else. Pushing harder on the fixed night in those cases does not build commitment. It builds a rota of people apologising for missing it, and that guilt does more damage to a friendship group than not playing at all.

Asynchronous play removes the coordination step entirely. Nobody misses anything because there is nothing to miss. You move when you can, and the game waits.

What asynchronous play looks like in practice

There are really two flavours, and they suit different groups.

Strict turn-taking

These are games where one person moves and then the game sits until the next person acts. The simplest is correspondence chess. On Chess.com the daily mode lets you choose how long each player has per move, with options from one day up to fourteen, and I have had a single game with a friend in Lisbon run for five weeks of pleasant back and forth. Words With Friends works the same way for word games, and the digital edition of Ticket to Ride supports asynchronous matches so you can claim a route on your lunch break.

For something heavier, Civilization VI added a Play By Cloud mode that sends a notification when it is your turn. Our group used it for one long campaign. It was fun, with a caveat I will get to below. The Battle of Polytopia is a lighter alternative: matches are shorter, turns take a minute or two, and it runs comfortably on a phone.

Shared worlds you visit separately

The second flavour is softer. Nobody takes turns, but your actions show up in someone else's game later. In Death Stranding, ladders, bridges and roads built by other players appear in your world, and you can leave "likes" that reach them days afterwards. In Dark Souls and Elden Ring, you can scrawl short messages on the ground that strangers read. Our group set up a shared Minecraft server that stays running, and people log in at three in the morning or seven at night to add to a build the others discover the next day. It is a long way from a raid, but it gives the group a project that moves forward even when nobody overlaps.

The catch nobody mentions: the slowest player sets the pace

The Civilization campaign taught us something about structure. In a six-player turn order, each person waits for all the others before moving again. If one friend takes a day per turn and everyone else takes an hour, the whole game runs at the speed of that one friend. Ours stalled for nine days while our nurse friend worked a run of night shifts, and two people quietly lost interest.

The fix was to stop running big group games in strict sequence. Now we pair off into one-on-one games instead: several chess and Polytopia matches running in parallel between different pairs of friends. If one person goes quiet, only one game slows down. The group still feels connected because we talk about the matches in the chat, and nobody becomes the bottleneck everyone resents.

The rule we settled on: no turn-based game with more than three players unless everyone agrees on a turn deadline before it starts.

A deadline of 48 hours per turn, written into the game settings where the game allows it, turned out to be the sweet spot for us. It is long enough for the parent of twins and short enough that a match still finishes inside a month.

Where live sessions still matter

I do not want to oversell this. Some of the best evenings in a gaming friendship happen live, shouting over voice chat during a co-op disaster. If your group can manage those, keep them. The guide on getting into online co-op games covers that side well.

What changed for us is the role those sessions play. They used to carry the whole friendship, which meant every cancelled night felt like a small failure. Now they are the occasional big event on top of a steady background of turns, messages and shared builds. When we do manage a live night, roughly once every five or six weeks, it feels like a reunion rather than an obligation. That shift also made it easier to judge which wider communities deserve our time, a question covered in choosing a community worth your free time.

One thing to set up this week

Pick the friend you always fail to schedule with and start a single correspondence chess game or an asynchronous Ticket to Ride match with them, using a three-day move limit. Do not invite the whole group yet. Run one game for a fortnight, see whether the rhythm suits you both, and only then add a second pair. Starting small is how ours went from a dead group chat to a dozen games running at once.