This is what a D&D game across three time zones looks like when it’s working. The college group scattered, or the forum friends never lived in the same country to begin with, and now every session is simultaneously a Saturday night, a late night, and a Sunday breakfast. If you searched “how to run D&D in different time zones” because your group chat has spent two weeks failing to schedule session one, here is the honest answer: the game is absolutely runnable, people run campaigns like this for years, and almost everything that kills them is a logistics mistake with a known fix. The fixes below are the ones that matter, roughly in the order groups get them wrong.

Stop looking for a time that works for everyone

There is no fair time. Spin a globe with players in New York, London, and Sydney on it and every slot you land on is somebody’s midnight or somebody’s dawn. The groups that die spend months refusing to accept this. They run a fresh availability poll every week, hoping this time the grid will produce a slot nobody hates, and every week the poll itself burns a little more of everyone’s enthusiasm. Scheduling by consensus is a tax you pay weekly, forever.

Pay it once instead. Find the least-bad time, give the person who got the worst end of it a genuine veto, and then write the result down as law: same slot, every week, permanently. This belongs in session zero alongside tone and safety tools, because at long distance the scheduling contract carries more of the campaign’s weight than anything else you agree on. Most campaign deaths are scheduling deaths, and a standing time is the strongest medicine there is. A recurring slot becomes a habit, and habits survive busy months; a weekly negotiation has to win an argument every single week, and eventually it loses one.

Anchor the game to one named city

“6 pm Eastern” feels precise. It is a trap with a fuse on it, and the fuse is daylight saving time. The United States and Europe change their clocks on different weekends in spring and autumn, so for a few weeks a year the gap between New York and London is five hours in one direction. Australia changes in the opposite season entirely. Twice a year, a game scheduled by offset quietly detonates: two players arrive an hour apart, both of them certain they’re on time, both of them right.

The fix costs nothing. The game lives in one city’s civil time, named out loud: “we play at 6 pm New York time, whatever that happens to be where you are.” One person owns a recurring calendar invite set to that city’s time zone, everyone else accepts it, and the software does the conversion forever. When the clocks change, the invite moves everyone together. The DM’s most important prep artifact for a distributed table is a calendar event with the right time zone attached. That’s the whole trick, and groups still get it wrong for years.

Run shorter sessions than you think you want

The four-hour session is a same-living-room luxury. In your three-city game, hour four of a 6 pm New York start is 3 am in London. Your wizard was sharp for the first two hours, quiet for the third, and by the fourth she’s a camera-off presence who answers direct questions after a delay. Push a long session on a distributed table and the back half is played by fewer people than the front half, whatever the attendance list says.

Two to two and a half hours, weekly, is the shape that works. It fits inside a school-night evening and a weekend morning at the same time, so nobody has to be a hero to attend. It keeps the whole table inside the hours where they’re actually good. And a shorter session concentrates play in a way that’s easy to underestimate: when everyone knows the window is two hours, the shopping montage gets snappy and the table finds the plot faster. Ending on time, on purpose, is its own craft skill, and it matters double here; I wrote up how to land an ending so that next week starts itself.

Spend live hours only on things that need to be live

Once you accept the two-hour window, the arithmetic gets strict. Live, synchronous time is the scarcest resource your game has, and a lot of what fills a typical session doesn’t need it. Shopping trips. Downtime projects. The letter your bard wants to send to the duchess. Two players having the quiet character conversation they’ve been circling for weeks. All of that plays beautifully in a side channel on Discord, typed across days, at whatever hour suits each writer.

Move it there. Reserve the live session for the things that genuinely require six people in one moment: fights, revelations, arguments about the plan, and any decision the whole party has to own. The async channel does double duty, too. Your Sydney player, whose live slot is breakfast, gets a version of the game where the hour is always right for him, and roleplay that would have been rushed at the table gets room to breathe. Some of the best scenes in a long-distance campaign happen on a Wednesday, in text, between two people who have never been awake at the same time.

Design for absence, because absence is coming

Run any game long enough and people miss sessions. Run one across three time zones and the misses multiply: the 8 am player has a family thing, the 11 pm player has an early flight, somebody’s power is out in a storm the rest of the table didn’t know was happening. Treat absence like weather. It arrives on its own schedule, it’s nobody’s fault, and a campaign built to require perfect attendance is a campaign with a countdown clock on it.

Building for weather takes three rules. The game runs at three players or more, announced up front, so one absence never cancels a session and the quorum question never has to be litigated at 5:55. An absent character fades politely into the background, and the table doesn’t puppet them through anything their player would want to play. And catching up costs the absent player nothing. That last one is where distributed tables quietly fail: when catching up means reading forty minutes of scrollback or cornering the DM for a summary, people skip it, fall out of the story, and drift out of the game without ever deciding to quit.

This is the exact problem we built Loracle around. The bot sits in your Discord voice channel, records the session, and posts a recap to the channel afterwards, so the player who slept through Saturday wakes up to the story on Sunday and walks into next week current. A distributed game leans on that harder than any other kind, because at three time zones the recap is doing quiet work every single week for somebody.

The game is worth the spreadsheet

Back to that Saturday. Your wizard is typing her spell descriptions in a hush at half past midnight. Your rogue has finished his cereal and is arguing tactics with a spoon in his hand. On paper this is a ridiculous way to spend a weekend, and every one of these people chose it, again, for the fortieth week running, because the alternative was letting the group dissolve when the distances got real.

A time-zone game asks more of you as a DM in exactly one place: logistics. Fix the slot, name the city, shorten the session, push what you can into the week, plan for the weather. None of it is glamorous. All of it is the difference between a campaign that limps through six sessions of scheduling polls and one where three cities’ worth of friends get the best two hours of their week at the same table, even when the table is an ocean wide.