Rule the Waves 3

There is a moment in every Rule the Waves 3 campaign that justifies the whole exercise: a light cruiser designed personally — 4,100 tons, undergunned, overengined, built purely to outrun anything it couldn’t kill — spotting an enemy battle squadron in fog and living long enough to radio the bearing. That cruiser is a compromise agonized over on a design screen two in-game years earlier, trading belt armor for a knot and a half of speed. The trade pays off. Nobody writes that story. The simulation does.

Developed by Naval Warfare Simulations and published by Matrix Games/Slitherine, RTW3 is the third and largest iteration of a series whose lineage runs back through NWS’s earlier tactical naval titles. The pitch is simple and enormous: you are Grand Admiral of one of ten navies — the USA, Britain, Germany, Japan, France, Russia, Italy, Austria-Hungary among them — from 1890 to 1970. That’s eighty years, from pre-dreadnought turret ships to jets and guided missiles, resolved in monthly strategic turns punctuated by top-down tactical fleet actions.

Market positioning is refreshingly honest: this game does not want everyone. It’s Windows-only on Steam, priced at $39.99, and it makes no attempt to court the Civilization crowd. Its natural competition isn’t Hearts of Iron IV or Victoria 3 — it’s Aurora 4X and Dwarf Fortress, systems-first simulations where the interface is a toll you pay to reach the machinery. The audience shape is predictable: strong praise from people who get past the front door, and a hard, unapologetic door.

Critics of the series have been cooler, and their central complaint is fair. RTW3 does a great deal more than RTW2 and refines comparatively little.

• The Ship Designer: The reason this game exists. You set displacement, gun calibre and layout, belt and deck armour schemes, torpedo armament, engine output, and watch cost, stability, seakeeping and crew requirements fight each other in real time. Every ship in your navy can be your fault.
• Eighty Years of Technology Drift: Campaigns start in 1890, 1900, 1920 or 1935 and run to 1970. Research is probabilistic, not a tech tree you shop from — you fund priorities and hope. Superheavy AP shells, radar, angled flight decks and guided missiles arrive on their own schedule, not yours.
• The Political Layer: Budgets, cabinet demands, public unrest, prestige, naval treaties, espionage and escalating tension with rival powers. Your government will demand battleships you don’t need and cut the budget that pays for them.
• Tactical Fleet Actions: Gunnery, torpedo runs, submarine ambushes, airship and floatplane scouting, carrier strikes — resolved on a top-down map with weather, visibility and night engagements that genuinely change outcomes.
• Emergent Alternate History: No scripted timeline. Wars start because tension crossed a threshold, and your 1930s can look nothing like ours.

The Gameplay Loop

RTW3 runs on a monthly strategic tick. You approve construction, assign fleets to stations, fund research, manage bases and coastal fortifications, and click “next month.” Most months, nothing happens. Then a report lands: tension with Japan rising, cabinet demands a new battleship class, a destroyer flotilla has run aground, war weariness rising. You react, you click again.

That rhythm sounds inert on paper and is anything but, because the loop’s real payload is deferred consequence. A battleship laid down in 1908 commissions in 1912 and fights in 1919, by which time the gun you specified is a generation behind and the armour scheme you skimped on is being tested by shells you didn’t know were coming. RTW3 is one of very few strategy games built around anticipatory dread about a decision made four in-game years ago. Paradox games let you course-correct constantly. This one makes you live with things.

The tactical layer is where those decisions get audited. Battles play out on a clean top-down plot with time compression and pause, and they are slow in the way real naval combat was slow — long approaches, ranging shots, minutes of nothing followed by a magazine detonation that erases a capital ship and 1,200 men in a single dice roll. Fog and night actions produce the best drama. The worst-case scenario is a running fight at extreme range where nothing lands for twenty minutes of real time, and the auto-resolve button starts looking reasonable. The design gives no reason to trust it: the AI resolves ships more carelessly than a player would.

The Ship Designer Is the Actual Game

Everything else is context for this screen. Add a fourth turret and displacement jumps, cost jumps, speed drops, and suddenly you need more boilers, which need more hull, which needs more armour to protect. The designer punishes cramped layouts, rewards coherent doctrine, and quietly grades your work — build something incoherent and your own naval staff tells you so.

What makes it more than an engineering toy is the budget. You are not designing the best ship. You are designing the best ship this year’s appropriation and this decade’s metallurgy will allow, knowing the Japanese are doing the same thing with different constraints. That constant, grinding triangulation between ambition, money and physics is the most sophisticated thing in the genre right now.

Onboarding Friction Is the Headline Problem

There is no meaningful tutorial. There is a manual — a good one, long, thorough, and effectively mandatory. RTW3 expects you to read documentation before playing, which is a stance, not an oversight.

The interface compounds it. Information density is extreme and hierarchy is weak: critical numbers sit in the same grey box, same font, same weight as trivia. Fleet management across multiple stations requires more clicking than it should. Nothing is discoverable; everything is memorizable. Once internalized, the UI is fast — dense screens beat pretty ones for this kind of work — but the ten hours spent getting there will bounce a large share of buyers, and calling that “part of the charm” lets the developer off too easily. Better tooltips and a guided first campaign wouldn’t cost the simulation a thing.

The narrative events are the other soft spot. They’re thin, repetitive, and read like placeholder text for a fiction the simulation is generating far better on its own. When your systems produce a fifteen-year naval arms race with Germany, “a scandal has hit the admiralty” is not pulling its weight.

Ugly, and honest about it. Ship silhouettes are functional line art, the tactical map is a plot board, and the UI is grey panels and small type — skeuomorphism without the craft, closer to a naval staff spreadsheet than a game. There is exactly one screenshot doing marketing duty on the store page, which tells you how much confidence anyone has in the presentation.

The upside: a 2D game of this scope is light on hardware, and campaign turns are built to resolve quickly even deep into the 1950s with large fleets. The design asks nothing of the GPU, so the usual modern PC-game tax — shader compilation, heavy load times — simply doesn’t apply. Long campaigns are the real test for a game played for hundreds of hours, and the structure (monthly saves, discrete turns) is built to survive them.

Audio is minimal to the point of absence. Plan on your own music.

Steam, Windows, mouse and keyboard, full stop. This is a desktop simulation built for a real monitor and a precise pointer, and it rewards a large display — the more panels you can keep open, the less you fight the navigation.

Steam Deck and handheld players should temper expectations. It’s a Windows title running through Proton, and even where compatibility holds, the interface is the obstacle: dense small text, tightly packed controls and heavy click volume are punishing on a 7-inch screen with trackpads. Mac and Linux users are in the same boat, minus the ergonomics complaint.

Steam Workshop and modding support are limited compared with what a game this systems-heavy could sustain, and cloud saves matter more than usual here, because losing a 40-year campaign is a genuine loss.

RTW3 is a specialist tool sold as a game, and it’s very good at being one. The ship designer alone justifies the price, and the campaign layer wrapped around it turns eighty years of naval engineering into a story you can only get by living through it. The criticism that it adds much and refines little is accurate — the jet and missile era extends the timeline without fixing what was already creaking, and the interface remains the single largest barrier between this simulation and the audience it deserves.

The depth is real and it’s rare, but the toll is steep and the flaws matter: a hostile on-ramp, thin narrative events, and tactical battles that drag. We recommend it to the right audience only — those who already know they want this kind of simulation. Pay the ten-hour toll and there is something substantial on the other side; just know the door is locked from the inside.