Twenty-Four Things a Resumed Run Forgot
Twenty-four things a resumed run had forgotten, found and fixed inside nine days, twenty-three of them in three.
The game is a browser survivor shooter, and a run can be long, so it saves: every thirty seconds, on every tab hide, and whenever the page is about to go away. What I had not taken in is how often the page goes away. Rotating the phone restarts the scene from the save. Changing the UI scale does. Handing a run to another device does. A killed background tab does. Every one of those is a resume, and I had been playing resumed runs for months without ever calling them that.
Each thing the save did not carry was small. A combo buff worth eight seconds of extra damage. The pity streak toward a guaranteed epic relic. The cursor into the boss rotation, so a resumed run fought bosses it had already beaten. The sixty-second timer that owed the next enemy a magnet drop. The walls a room had rearranged mid-fight, so a reload snapped them back and a chest could come back inside rock. A milestone buff that wore off on a timer, where the timer died with the page and the boosted stats were what got saved, so a resume inside that minute made the buff permanent. The boss wave an endless cycle had staged as bare delayed calls, so a save in that window came back with the cycle advanced, a full boss timer and no wave. Card locks. Enemy types, so restored kills counted for nothing in the codex. The pace ghost and the run timeline, both switched off for the rest of a resumed run on the theory that their early samples had died with the page, when in fact nothing had ever written them to the save at all.
None of these was reported, by me or by anyone else. Each was the size of a shrug. Most were found by an agent reading the restore path against the run’s state, feature by feature, and filing one item per thing the save did not carry; twenty-one of the fixes landed in two days in October, two more the day after, and the last one a week later: a boss wave staged in the seconds after a cycle banner.
The number I keep is twenty-four, not because it is large but because of what it counts. Every one of those fields existed because a feature had shipped with its own piece of state and nobody had asked the save file about it. A save file is an inventory of what someone remembered the run was made of, taken on the day the save was written. Every feature since is a thing the run forgets, until someone turns the phone sideways and happens to be watching.