You don't know how long your games take

· by Uncle Versace

Ask a Commander pod whose turns are too long and you'll get four confident answers, none of them "mine." Ask a Modern grinder how long that round went and they'll say "forever" while holding a match slip that says twenty-eight minutes. We talk about time at the table with the same swagger we talk about matchups — and, it turns out, the same accuracy.

Last month I wrote about how your matchup memory edits itself in your favor. This is the sequel: the clock in your head is doing the same thing, and honestly it's worse. At least the matchup number was about something you were trying to watch. Time is something you feel, and feelings don't come with timestamps.

Why your clock lies

Your own turns feel short because you're busy during them — sequencing, doing combat math, talking yourself out of the greedy line. Everyone else's turn is just waiting, and waiting is the slowest thing there is. The trap is that every player at the table is running that same math, which is how a four-player pod produces four people who are each certain they're the fast one. Same phenomenon as the other checkout line always moving faster; nobody thinks they're the line.

Then the outliers eat the median. You remember the forty-minute turn with the triggers and the extra combat steps, and the "three-hour game" it lived in. You do not remember the dozens of ninety-second turns and two-hour games that actually make up your average, because nothing memorable happened in them — that's what made them fast. And since nobody writes any of it down, the claims never get audited. "That deck takes forever" has the same evidentiary standing as "I'm 60-40 in that matchup," which — see last month.

What the record shows now

In the first post I said the long, patient version of this site might someday answer "what's the median game length in a format" with numbers instead of vibes. June quietly built the scaffolding. If you log a game's start and end times and its turn count — optional fields on the match form, a few extra seconds — the site now turns them into pace stats everywhere the data flows: your profile has a Pace section with your average game duration, turn count, and time per turn, honoring the same filters as the rest of the page (so you can see your pace with one deck, or in one format). Deck pages show the community's pace with that deck. Format pages show Format Averages — including a per-bracket breakdown, so once enough Commander games carry times, "do bracket 4 games actually end faster than bracket 2" stops being a Discord argument and starts being a number.

Who's the beatdown? Your clock knows

Here's the part that's more than trivia. The oldest strategy advice every player eventually gets pointed to — Mike Flores' "Who's the Beatdown?" — says that close games are mostly lost by misjudging your role: playing control when you're supposed to be the aggressor, or the reverse. Players have argued about their role by feel for twenty-five years.

The Winning vs Losing split — on your profile and on every deck page with enough data — is a role receipt. It shows the average turn your wins end on next to the average turn your losses end on, plus your fastest win and how long each kind of game runs. If your wins land on turn six and your losses on turn eleven, you are the beatdown, whatever your deck's curve says — every turn past your average win is being played on someone else's clock, and your mulligans and sideboarding should know that. If it's the other way around, stop panicking on turn five. Your deck wins the long way; let it.

The honest caveats

Same rules as everything else here. Small samples get flagged — under five games, the cards say so — and nothing shows at all until you've logged the underlying times and turn counts; "Data Pending" is the site telling you the truth about what it doesn't know. The times are time-of-day fields, so the rare game that genuinely crosses midnight can't be represented — leave the times off that one. And as of this week's release the form rejects a game that ends before it starts, a lesson I learned by watching one typo'd row quietly drag a duration stat negative for a while before I caught it. Honest numbers take maintenance.

The community numbers are still thin — there's a handful of us, and pace stats only count games where someone bothered to log the clock. But as with everything on this site, the part about you works tonight.

If any of this resonates

At your next event, log the times: when each game started, when it ended, what turn it ended on. It's a few seconds per game on top of the result you were already logging. Do it for a month and you'll know your real pace, your deck's real clock, and which side of the beatdown question you're actually on — instead of which side feels right while you're waiting for someone else's turn to end. It's free, and signing up takes less time than an average turn. I can now prove that.

The stopwatch doesn't care whose turn felt long. That's what makes it useful.

See you in the data.

— Andrew