The tutorial we built but couldn’t open
There is a particular kind of bug that doesn’t crash anything, doesn’t corrupt anything, and doesn’t even look like a bug — because every piece you wrote works exactly as intended. We hit it building the opening of The Long Watch. The whole first-time experience was finished, saved, and confirmed working. And for a stretch, no one could get to a single second of it.
What we’d built
The Long Watch has no separate tutorial mode. The first hour of your first save is the tutorial, taught by a hand-shaped little valley rather than a stack of pop-ups — the whole design, from the staged opening scene to the way it forgives a failed first run, has its own field note. This post is not about that idea. It’s about the unglamorous engineering underneath it, and the gap that nearly swallowed the whole thing.
For our purposes, only three pieces matter — the three the wiring bug touches. There’s the first-run valley itself: a fixed, hand-composed opening that a brand-new player is meant to drop straight into. Over the top of it sits the quiet stream of in-world prompts that hand you your divine powers one at a time. And underneath both is a completion mark, the little record that says this player has been through the lesson and shouldn’t be shown it again.
All of that was built. Committed. Tested. Confirmed working.
The door with no latch
And yet, for a while, you couldn’t open any of it. Every part of the door was finished except one small piece: the latch that turns the handle from the main menu.
Here is how a brand-new player is meant to arrive in the valley. On a genuine first run, the game raises a one-time signal — a quiet flag that means this is someone’s first time; take them straight in. The start-up code was fully wired to watch for that signal: read it, act on it by building the special starting world, and clear it once it had been used. The menu even carried notes describing the exact moment that was supposed to flip it on.
But nothing ever flipped it on. The single connecting line that the menu was meant to set on a first run was never written. So the flag sat forever in its off state. The start-up code never saw its cue. And the finished tutorial stayed sealed behind a menu that had no idea it existed.
We had built the whole room and forgotten to hang the door.
This is the oldest shape of bug in feature work, and it’s nearly invisible because nothing is wrong. The scene is correct. The prompt stream is correct. The start-up code is correct. Every line you’d inspect does its job. The defect lives in the absence of a line — the one short wire between two finished halves that nobody connected. A code review reads what’s there; this was a hole shaped exactly like the thing that should have filled it.
It’s worth being honest about why the wire got left dangling. It wasn’t carelessness so much as sequencing. The launch plumbing was next up precisely when other work pulled focus — the winter pressure-test mechanic needed real teeth, and a parallel push to make the simulation run faster was reshaping the ground underneath us. The closing paperwork got deferred, the door stayed unhung, and because nothing visibly broke, nothing shouted to remind us.
Hanging the door
The fix was small and undramatic, which is fitting. We taught the menu to recognise a true first run on its own — no world saved yet, and the tutorial not yet completed — and, when both are true, to quietly take the player straight into the valley instead of the usual world-preview screen returning players see. On the way in, it raises the signal the start-up code was already waiting for. On the way out, it marks the tutorial complete.
That completion mark is the other half of doing this gently. It’s remembered per install, so the guided opening only ever runs once; a returning player with worlds already on the shelf is never dropped back into the lesson. The flip to “done” happens only after every teaching prompt has appeared and faded, so finishing means finishing, not merely arriving.
With that one line of plumbing in place, the door finally opens. A first-time player now lands in the valley exactly as intended, walks through the powers one prompt at a time, and every divine verb — including the handful held behind the learn-first gate until earlier lessons land — becomes reachable in the order the lesson means to teach them.
Hardening the latch
A latch that only works on a sunny day isn’t a latch, so we spent the rest of the day making the new path honest under pressure. We added tests that the lesson can actually be completed end to end — that every power can be exercised, that the world survives a save and a reopen, and that a first-run player is genuinely routed in rather than left at the menu.
Two edges got specific attention. We made the launch signal commit only after the screen transition into the valley has actually succeeded — so a half-finished hand-off can’t leave the flag set with no world behind it. And we refused to let the menu silently mark the tutorial “done” if its roster of lessons were ever empty, because a tutorial that teaches nothing should fail loudly, not quietly pretend it taught everything.
The gaps we left open on purpose
Hanging the door surfaced two honest gaps, and we’d rather name them than pretend the opening is finished.
The first is about leaving and coming back. Reopening a saved world faithfully restores the world itself — the terrain, the creatures, where everything stood — but it does not yet bring the guided-start layer back on top of it. So if you quit mid-tutorial and relaunch, the place returns but the gentle voice goes quiet: the prompts, the progressive unlock, the competence-fade, and the re-seed watcher don’t resume. The world reloads; the lesson doesn’t. That one is logged for a future design call, because the right answer isn’t obviously “always” or “never.”
The second is about generosity. A tutorial about divine power only teaches if you can afford to use it. Right now the early energy economy is too tight to learn in — a starting budget nowhere near the cost of trying every power once, with the slow background trickle far too gentle to close the gap inside the short window before winter. A first-run player should be able to reach for everything at least once; today they can’t quite. That’s a tuning problem, not a structural one, and it’s next.
And the winter pressure-test still ships with its difficulty dialled all the way down, waiting to be tuned by feel rather than nailed to a number in code — but that’s a story for the field note about the day winter learned to kill.
None of that takes anything away from the small victory of the day, which was almost embarrassingly modest in size and outsized in effect. One line of wiring. A door that was always there, finally given a handle that works. The tutorial we built is, at last, a tutorial you can open.
