Devlog: DO YOU COPY

Five days ago a glacier came off a mountain above the Trishuli valley in Nepal. 919 dead as of tonight, close to five thousand missing, and the detail I could not put down is that the warning system worked. The USGS logged the collapse live, as a magnitude 4.4 earthquake. Nepal's flood network heard it too. But the network was built to watch monsoon rain, the sky was clear, and the manual for earthquakes does not say run. The signal existed. It was filed under the wrong disaster.

So I built the filing. You sit one chair for the whole game, a river gauge duty post above a fictional valley, and the verb is reading. A drum seismograph plotting in real ink. Water needles for five stations up the gorge. A laminated manual with thresholds that are genuinely correct, which is the trap. Two quiet shifts teach the book, a monsoon crest handled exactly right, then a blast at the road cut and a dead battery that teach what silence usually costs. The third shift is a clear morning. The drum slams, HQ reads the file aloud, seismic event, not a flood criterion, and then Station 12 stops answering. Then 11. Then 10. Each one exactly sixty seconds after the last, six kilometers apart. The radio log stamps seconds, the manual's travel table does division, and the game trusts a stranger to do the rest. Nobody on screen ever says wave.

The scoring is minutes of warning delivered, per village, on a report card that looks like the form it would actually be typed on. Sirening the moment the drum slams beats waiting for certainty. Waiting for certainty beats the protocol. The protocol scores zero, and following it to the letter is the only way to lose everyone, which is the entire point.

The seismograph nearly shipped blank. I drew the trace onto the drum's texture with what looked like correct math and leaned in one night to find pristine paper: the ink was landing on a single ring around the cylinder's midpoint, a line one texel wide hiding exactly behind the pen arm. Geometrically true, perceptually nothing. The fix turned it into an actual helicorder, the trace advancing down the sheet lap after lap, permanent, so the quake leaves a scar you can lean in and read an hour later. An instrument that forgets is just a decoration.

The other lesson cost me a whole evening in two installments. Three.js will happily accept a material flag with nothing behind it. A Points cloud with no texture renders opaque squares. A vertexColors flag on geometry with no color attribute multiplies by black. Both times the symptom was the same, hard black rectangles scattered across a sunrise, and both times the bug was a promise the shader kept and I had not. The renderer does not warn you. It just draws exactly what you asked for.

The radio voices are synthesized garble, band passed to 300 to 3000 hertz like a real handheld, each station keeper seeded with their own pitch and cadence. You never understand a word, the subtitles carry that, but you learn who is who by rhythm, which is how radio actually works. And when a transmission cuts mid sentence into static, the silence that follows has a shape. The last thing a dying instrument does is tell the truth.