More indie games

Launch Window makes the timetable the hard part of spaceflight

4 min read

Most space games make the burn the skill. Launch Window makes the burn automatic and the calendar brutal — you plot shipping lanes between planets, then wait for the one moment the geometry lets you leave.

You plot lanes, not burns

The verbs are build, route, and launch. You place solar panels and drills across the surface of a planet — anywhere on it, because the worlds are spheres rather than flat plots — wire them into factories, build ships out of what those factories make, and then draw a shipping lane between one body and another. Once the lane exists, the ships fly it themselves.

That last part is the unusual choice. Almost every other physics-based space game makes the manoeuvre the skill: you are at the controls, nudging a burn until the projected path kisses the right orbit. Launch Window hands the burn to the simulation and keeps the part above it. You are not a pilot, you are the person deciding that the ice moon needs eight more tankers and that they have to leave now, because the next time that trip is cheap is a long way off.

Hence the title. Two bodies moving around a star are only occasionally in a position that makes the trip affordable, and that window closes whether or not your cargo is loaded. So the real work is anticipation — what will that colony be short of by the time a ship arriving today was supposed to have arrived, and what do you have to have built weeks earlier for the answer to be “nothing”.

The scale is the other half of the pitch: over a thousand physics-simulated ships under your command at once, with flagships leading convoys so you are giving orders to a fleet rather than to a vessel. Star systems are procedurally generated, and the bodies in them are not interchangeable — ice-rich moons make water and therefore fuel, metal-rich rocks feed factories, and the outer planets hold the rare material behind the longest transit times. Where you expand, and in what order, quietly writes the logistics of everything you do afterwards.

Why a schedule makes a better puzzle than a joystick

Clockwork games and time loops is the essay that explains why this design can work at all. Its argument is that most games freeze the world until the player acts, and that the genuinely interesting alternative is a world running on its own schedule, where the moment you show up becomes the decision. A solar system is the purest clockwork there is. Nothing in Launch Window waits for you to be ready; the planets keep going round, and your entire plan is an answer to where they will be.

How games use feedback loops covers the engine underneath the growth. An automation game is a positive feedback loop by construction — fuel buys ships, ships open routes, routes bring back the material that builds more ships — and left alone that loop only accelerates. The transit time is the brake. Cargo you committed to a six-month trip is cargo you cannot spend, which means every expansion is paid for in advance and the runaway is held in check by physics rather than by an arbitrary cost curve.

The power of video game HUDs is the one that decides whether any of it is playable. That piece argues a HUD is not decoration but a constraint on which mechanics a game can carry at all, and a thousand ships on independent trajectories is exactly the mechanic that lives or dies on its readouts. If the interface can tell you at a glance which window opens next, which colony is running dry, and which lane is over-served, this is a great logistics game. If it cannot, the fleet becomes noise and the player goes back to flying one ship.

What you actually get

Launch Window is by gumptiongames, self-published, coming to Windows with no date announced beyond “to be announced”, listed under Simulation and going out into Early Access. It is single-player, and the store page flags save anytime, adjustable difficulty, camera comfort options and playable without timed input — a considerate set of switches for a genre that usually assumes you will simply cope.

The honest risk in the design is the same one every automation game runs: once the lanes are drawn and the colonies are fed, the loop can turn into waiting for numbers. What suggests otherwise here is that the timing is not a delay bar, it is orbital geometry — a missed window is not a slow reward, it is a plan that has to be rebuilt around a system that has moved on without you.

If the appeal is a logistics network you have to keep alive while it travels, Railborn is the closest thing on this list — a base that is a train instead of a place, where laying the track is the decision that determines everything the base can do next. Same idea, one gravity well down.