Cadence Machine turns a spreadsheet into a séance

For the first two hours I thought Cadence Machine was a small game wearing a large game as a coat. You are given a junction, four platforms and a timetable, and told to move rolling stock between them without anyone missing a connection. There is no story. There is no character. There is a grid, a clock, and a quietly excellent sound design that tells you when something has gone wrong before the interface does.

The tutorial is four screens long and then it leaves. That is the first sign that this is a more confident piece of work than it first appears. Most systems games of this shape spend their opening hours apologising for their own complexity, layering tooltips over tooltips until the player is reading documentation rather than playing. Cadence Machine hands you a timetable and assumes you can read.

You cannot, at first. My third shift was a catastrophe. A freight service arrived nine minutes early, which should have been good news, and instead cascaded into a forty-minute delay across the entire western approach because I had parked a maintenance unit in the only siding long enough to hold it. The game did not tell me that was going to happen. It let me find out, and then it showed me exactly why, in a replay view that is the single best piece of interface design I have used this year.

The loop is a teaching machine

That replay view is the key to the whole thing. When a shift ends, successfully or otherwise, you can scrub back through it on a single horizontal timeline with every unit drawn as a coloured thread. Conflicts show as crossings. Delays show as threads stretching. You are not told what you did wrong in words; you are shown a picture in which the mistake is the most visually obvious thing on screen.

This is what I mean about teaching. A great systems game does not explain its rules, it builds a representation in which the rules become visible, and then gets out of the way. Cadence Machine has found one of those representations, and the confidence to make it the centre of the experience rather than a menu three clicks deep.

By the second act the junctions have grown to a size where holding the whole thing in your head is no longer possible, and the game knows it. It introduces a planning layer, a way to write standing instructions that execute without your attention, and the game quietly becomes about writing a small program in a language made of platforms and timings. The moment your first standing instruction runs a full shift without intervention is genuinely thrilling in a way I struggle to explain to people who do not already like this sort of thing.

It is also where the game very nearly loses its nerve. There is a five-shift stretch in the middle where the difficulty jumps hard, and the planning tools you are given have not quite caught up with the problems you are being handed. I lost an evening to a scenario that turned out to hinge on a signalling rule mentioned once, eleven hours earlier. That is the one genuinely poor piece of design in forty-one hours.

The part nobody expected

Between shifts there is text. Short passages, two or three hundred words, about the people whose journeys you have been rearranging. A nurse who has changed at your junction every Tuesday for six years. A freight driver counting down to a retirement he does not want. None of it is interactive and none of it affects the puzzles at all.

I expected to skip these. I read every one of them twice. They work because they never once ask you to feel something about the trains; they simply establish that the abstraction on your screen has weight, and then return you to the abstraction. By hour thirty I had started making scheduling decisions that were slightly worse on paper because I did not want to delay the Tuesday service again. The game never acknowledges this. It does not need to.

Performance and comfort

It runs on anything. On a five-year-old laptop it held a locked frame rate at native resolution with the fan barely audible, which matters more than it sounds: this is a game you play for three hours at a stretch, and thermal noise is a real cost. The console version is identical in content and slightly better in one respect, because the controller cursor has an acceleration curve that the mouse version does not quite match.

The accessibility settings are thorough without being showy. Colour-blind-safe thread colours are on by default rather than buried, text scales to 200 per cent without reflow problems, and every timed element can be paused. The one gap is audio: several conflict warnings are distinguishable by pitch alone, and there is no visual equivalent for two of them.

Should you play it

If you have ever enjoyed a game about logistics, yes, immediately. If you have not, this is the one to try, because it is the clearest example of the form anyone has built and it asks for four hours before it asks for forty. The middle-act difficulty spike is real and it is worth pushing through. Two years from now I expect to still be opening this on weeknights, which is the only review score that has ever meant anything.