The problem
Every figure this publication prints depends on an ending existing. Hours to credits, finish likelihood, where owners stop — all of it assumes a terminal state the player is either reaching or failing to reach. Port Meridian has no such state. You establish a settlement, you keep it alive, and eventually you stop.
The first draft of this audit scored it zero on finish likelihood, which is technically accurate and completely useless. The second draft excluded it. The third is this one, and it accepts that a publication about the cost of long games needs a way to talk about games with no length at all.
What changed
Two things. First, finish likelihood is now marked not applicable rather than zero for games without a terminal state, and the method page says so. Second, and more usefully, the resume cost measurement was promoted: for an endless game it is not one figure among four, it is the whole audit.
A game you will play for two hundred hours across three years is not asking you to finish it. It is asking you to keep coming back, which makes the cost of coming back the only thing worth measuring.
Cost of returning after a break
Eleven minutes, which for a game of this complexity is genuinely impressive engineering. Put down for three weeks at hour fifty-two and resumed cold, the settlement was legible within two minutes and I was making sensible decisions within eleven.
Three specific things earn that figure. Every building shows what it is currently doing in words on the building itself, so the state of the settlement is readable without opening anything. Production chains are drawn as physical lines on the ground rather than held in an abstract menu. And there is a single log of recent events phrased as sentences — a harvest failed, a workshop idled — rather than as notifications.
| Resume task | Minutes | Why it was cheap |
|---|---|---|
| Reading settlement state | 2 | Every building displays its current job in plain words |
| Reconstructing production | 4 | Chains are physical lines, visible without any menu |
| Remembering intentions | 5 | The event log reads as sentences, not notifications |
| Total | 11 | Against a ledger median of 7.5 minutes for far simpler games |
Where it does lose people
Not at a cliff, but at a slope. Around hour thirty the settlement becomes stable enough that nothing is urgent, and the game offers no new goal to replace survival. Players who invent their own project continue for hundreds of hours. Players who wait for the game to suggest one drift away over a fortnight without ever deciding to quit.
This is the honest weakness, and it is a real one. The game is superb at letting you leave and return, and weak at telling you why you would want to. Those are different problems and only one of them is measured well by this publication's figures.
What the audit records instead of a finish rate
- Resume cost after three weeks: eleven minutes.
- Hours to a self-sustaining settlement: about thirty.
- Hours before the game stops proposing goals: about thirty.
- Sessions logged after that point: nineteen, averaging fifty minutes, over eleven weeks.
Verdict
The best-behaved long game in the ledger, and the one that exposed a flaw in how the bureau measures things. If your problem is that you own four hundred games and cannot maintain a commitment to any of them, this is the rare design that costs you almost nothing to abandon and return to repeatedly.
Whether it gives you a reason to return is a question the figures here cannot answer, and after eighty hours I am still not sure I can either.