Satisfactory

The genre's defining games are top-down, and the reason is obvious: you need to see the whole factory to reason about it. Satisfactory throws that away and puts you on the ground inside the thing you are building, and the trade turns out to be worth it, because standing under a conveyor bridge you designed forty hours ago produces a feeling no spreadsheet does.

Vertical space is the innovation

Once you have jetpacks and hypertubes the factory stops being a floor plan and becomes architecture. My aluminium plant is four storeys with the refineries stacked above the smelters because gravity made the pipes easier, and arriving at that solution took two hours of walking around a half-built structure looking at it.

That is the loop. Not optimisation — the game is generous enough that almost any working design is acceptable — but building something you then inhabit.

Hours

143 across two worlds

Full teardowns

4

Longest single belt

Embarrassing

Pace over pressure

There are no enemies worth the word, no timers, and no fail state. Progression gates are research milestones that ask for a quantity of something you cannot yet make efficiently, so each phase begins with a problem and ends with a factory. The 1.0 release added an actual ending, and the final phase is a genuine escalation rather than a number increase.

Where it slips

Pipes. Fluid mechanics simulate head lift and pressure in ways that are physically defensible and practically miserable to debug, and the game explains almost none of it. Every player learns the same lessons from the same wiki page.

Performance also degrades hard at megabase scale, and the last twenty hours of my main world were noticeably worse to play than the first hundred.

The verdict

A hundred and forty-three hours and the only reason I stopped is that I finished it. The most time-consuming game reviewed here and the one I regret the least.

Play it with one other person. Do not look up ratios for the first fifty hours.