I was seven years old when Atari put me in a cockpit and told me not to die.
At seven you are not playing a game. You are Luke. The Force is a real thing and you have it and the exhaust port is right there. Vector graphics. White lines on black. The trench walls of the Death Star coming at me in a way that no screen had ever done before. Towers. Turrets. The moment you stopped reading the geometry and started just surviving — that was the moment you lost. I lost a lot of quarters in 1983. I also played that machine until I understood the trench well enough to stop losing. That's the distinction. That was the whole thing.
I've been chasing that distinction in runners ever since.
A runner is probably the oldest genre in games that nobody named until later. You are moving. The world is coming at you. You decide what to hit, what to dodge, how long you survive and with how much dignity. The loop is tight. The stakes are legible. The death is usually your fault.
What changed across forty-odd years is everything except that.
The Star Wars arcade was on-rails and first-person before either of those were categories — three stages, vector geometry, TIE fighters between you and the trench, the trench between you and the exhaust port, and something that felt like speed nobody had simulated before. Space Harrier did it in full color pseudo-3D two years later and Yu Suzuki proved the format could be warm and joyful instead of cold and military. The perspective became a whole mode of seeing.
Then it went quiet for a while. The genre spread into other things — into scrolling shooters and driving games and rail sections inside bigger action games. Runners were a vehicle, not a destination.
Adam Atomic's Canabalt in 2009 reminded everyone what a pure runner could do. One button. One man. Rooftops. No explanation. The purity of it was the point. You could explain the controls in half a sentence and the tension arrived anyway. Temple Run took that logic to phones two years later and made the format global. After that, runners were everywhere — and most of them had figured out how to look like runners without understanding why runners work.
The endless runner became wallpaper. Bright. Competent. Forgettable. You survived until you didn't and then you forgot why.
I've been testing the runner build for Hack Love Betray this week. Pseudo-3D trench, five lanes, thirty seconds, Handler grade at the end. Built to be played on a phone at a bar with one bar of signal. The City doesn't care how comfortable you are.
And every time I came out of a run — S, A, F, whatever — I found myself asking the same set of questions. After enough sessions I wrote them down. They turned out to be the same questions I've been asking about runners since the trench.
They're worth sharing.
Am I choosing, or only reacting?
This is the hardest question and the most important one. The worst runners are pure reaction tests — obstacle appears, you dodge, there was no decision, you either had the reflex or you didn't. That's a hand-eye coordination exam with a score. It is not a game.
A runner that works gives you decisions. The geometry arrives with enough warning that you can read it. You might have two routes and one of them is faster and riskier. You might have a choice between taking damage now for a better position or playing it safe and leaving points behind. The run should be a sequence of small bets, not a sequence of reflex tests.
The Star Wars trench was full of decisions. The towers had patterns. You could fly low for more shooting angles or high for more dodge room. You were choosing, even at eleven, even under the pressure. That is why the quarters kept going in.
Did I lose because I got greedy, sloppy, or unlucky?
If the answer is ever "unlucky," the runner has a problem.
