Stormworks: Build and Rescue

There’s a moment, maybe six hours into Stormworks, when the game finally clicks. A boat has been built. It floats — barely. A diesel engine is wired to a fuel tank, an electrical bus runs from a battery to a starter, a throttle connects to a gearbox, and — at the last second — an engine which burns fuel and air also produces heat and therefore needs a radiator with coolant flowing through it. Ignition. It runs. Then it overheats and dies four hundred meters offshore because the cooling loop was undersized, and there the creation drifts in the rain while a distress call ticks down somewhere over the horizon.

That failure is the product. Stormworks: Build and Rescue, from British studio Geometa, is not a game about rescuing people. It’s a game about building the machine that rescues people, and then living with every engineering decision made along the way.

Market-wise, it sits in awkward and largely uncontested territory. It is not Kerbal Space Program, though it shares the “your incompetence is the antagonist” design philosophy. It is not Minecraft with vehicles, though the block-based editor invites the comparison and the comparison does the game a disservice. The closest honest framing is From the Depths meets a maritime search-and-rescue simulator, with a node-based logic layer and embedded Lua that would look at home in an industrial automation course.

Its long-term Steam reception reflects cult status rather than mass appeal, and the trend has held up through years of early access and post-launch iteration. That matters. It suggests a developer that has kept working rather than a studio coasting on a good launch week.

• The Vehicle Editor: A voxel-adjacent block editor where every component is placed — engine blocks, fuel lines, electrical wiring, hydraulic actuators, pumps, valves, radiators, gauges, rotors — and connected physically and logically. Nothing is decorative. If a cockpit has an altimeter, that altimeter was wired to an altitude sensor by hand.
• Node Logic + Lua Microcontrollers: A visual programming system with composite signals, gates, PID controllers, and delay blocks, plus actual Lua scripting for anything the nodes can’t express. Autopilots, radar displays, terrain-following helicopters, autonomous drone boats — all player-built, all functional.
• A 15,000 km² Physics Ocean: Buoyancy, wave dynamics, dynamic weather, and day-night cycles across a vast archipelago. A hull that’s stable in flat water can and will roll in a storm.
• Career Mode Economics: Start with a small budget and a cramped workbench. Take cargo runs, firefighting contracts, medevacs, and rescues. Manage fuel, repair costs, and workshop expansion.
• Drop-In Co-Op and Steam Workshop: Crew a vessel with friends — one on helm, one on winch, one panicking in the engine room. The Workshop hosts tens of thousands of community craft, missions, and mods.

The Gameplay Loop

Stormworks runs two loops stacked on top of each other, and the tension between them defines the entire experience.

The outer loop is a business sim. Accept a contract, fly or sail to the location, execute, get paid, buy better components. It’s serviceable. The missions — hauling cargo, extinguishing a burning oil rig, hoisting an injured crewman off a listing trawler at three in the morning in six-meter swells — provide structure and, occasionally, genuine drama.

The inner loop is where the real game lives: build, test, fail, diagnose, rebuild. This is not iteration in the vague sense marketing departments use. This is discovering that a helicopter’s collective is responding too aggressively because a PID controller’s derivative term is tuned wrong, and rewriting it. It’s debugging. The game is, functionally, a debugging simulator with waves.

What makes it work is the specificity of failure. When something breaks in Stormworks, it breaks for a reason that can be traced. A winch won’t lift because the hydraulic pump isn’t getting enough RPM. A sub won’t surface because ballast is unevenly distributed and a pitch moment has been created. A plane stalls on approach because it never had enough control authority at low speed. Every one of those is a solvable problem with a discoverable cause, and solving them produces a specific and increasingly rare flavor of satisfaction — the kind that comes from understanding a system rather than beating one.

Onboarding Friction: The Elephant on the Helipad

Now the bad news, and it’s serious.

Stormworks’ tutorials are inadequate to the point of negligence. They introduce the editor. They gesture at basic concepts. They do not, in any meaningful way, teach how to build a working vehicle from scratch — which is the entire game. The gap between “completed the tutorial” and “built a helicopter that doesn’t immediately invert itself into the sea” is measured in YouTube playlists and forum archaeology.

This is the single most consistent complaint in the Steam reviews, and it deserves to be. A game this systemically rich has an obligation to teach its systems, and Stormworks largely outsources that obligation to its community. The community, to its enormous credit, has answered — there’s an ecosystem of tutorial creators who are genuinely excellent. But “the players wrote the manual” isn’t a design achievement. It’s an abdication.

The Workshop functions as an accidental escape hatch. Don’t want to engineer everything yourself? Download a community-built rescue helicopter and go fly missions. That’s a legitimate way to play, and plenty do. But it also quietly reveals the design problem: the game’s most popular on-ramp is one the developers didn’t build.

The Interface

The UI is functional, dense, and inelegant. Menus are nested where they should be flat. Component tooltips explain what a part is without explaining what it’s for or what it needs to work. The logic editor — the heart of the advanced game — presents a node graph with all the visual affordance of a 1990s CAD package. Signal types (on/off, number, composite, video, audio) are distinguished by color coding that gets memorized through repetition rather than design.

None of this is fatal, and veterans stop noticing. But it compounds the learning curve rather than easing it. There’s a version of this game with a thoughtful information architecture, and it would rate several points better without changing a single simulation system.

The Update Problem

In 2023, the Space DLC shipped a substantial physics rework. It also broke a large number of existing Workshop vehicles, invalidating designs players had spent dozens of hours on. Community reaction was, predictably, furious.

This is the structural risk of a game built on player-authored content sitting atop a simulation that the developer keeps revising. Geometa’s continued development is a real asset — this is not an abandoned game — but every deep change to the physics model is a potential demolition of the community’s accumulated work. That’s a hard tension to resolve, and Stormworks hasn’t resolved it. It has mostly absorbed the hit and moved on.

Then there’s the DLC cadence. Search-and-Destroy, Industrial Frontier, Space, season passes. Individually defensible; collectively, a steady drumbeat of paid additions that a meaningful slice of the player base reads as monetization outpacing polish. When the tutorials are still weak six years in and the store page keeps growing, the priority ordering is hard to miss.

Aesthetically, Stormworks is unpretentious. Chunky, low-poly, brightly-lit — a deliberate readability-first style that keeps the eye on components rather than surfaces. It’s not beautiful, but it ages well precisely because it never chased realism. Weather and ocean rendering are the standouts: a storm at night, spray over the bow, a searchlight cutting a cone through rain, is legitimately atmospheric.

Performance is the honest weak point by design. Small craft run well; large builds are where the simulation strains. Complex vehicles with hundreds of logic components, multiple engines, and dense block counts are CPU-bound in ways a better GPU won’t fix, and multiplayer amplifies everything — several players operating large vehicles in the same area is exactly the load profile this engine handles worst. If the ambition is a 2,000-block aircraft carrier with a fully scripted CIWS, budget for frustration.

Steam is the right and only home for this. Mouse and keyboard aren’t a preference here — they’re a requirement. The editor demands precise placement, multi-axis camera control, and constant modifier-key work; a gamepad handles vehicle piloting acceptably but is useless for building.

The Steam Workshop integration is arguably the game’s most important feature, and it works exactly as it should: one-click subscription, vehicles appear in the workbench, missions and mods drop in cleanly. It’s the difference between a niche engineering toy and a living platform.

Steam’s refund window deserves a mention, though — it expires right around the point where most players are still fighting the interface and haven’t yet built anything that works. If on the fence, the decision is whether to buy in before the game has had a chance to prove itself.

Stormworks asks more of its players than almost anything else on Steam, and it gives back proportionally. The simulation is not a veneer — it’s the whole object. Lifting a stranded crewman off a sinking hull using a winch wired by hand, from a helicopter designed from scratch, stabilized by a controller programmed from nothing, is an achievement very few games can offer.

But a game that makes the first ten hours this unnecessarily hard can’t rate higher than good. The learning curve is defensible; the absence of teaching is not. Geometa has built something remarkable and then left the front door locked, trusting YouTubers to hand out the keys. That works for the audience that persists — and it filters out an enormous number of people who would have loved this game if it had simply explained itself.

Buy it if documentation reads like fun. Skip it if not. There’s no middle ground here, and Stormworks has never pretended otherwise.