Sinking Steel: The Pleasure of Earning a Torpedo Shot

A submarine game becomes interesting before the torpedo leaves the tube.

The explosion is the payoff, but the real drama happens earlier: in the dark approach, in the periscope sweep, in the uncertain contact report, in the calculation that might be wrong, and in the decision to fire anyway.

That is the heart of Sinking Steel, our working title for a compact submarine simulation built around manual torpedo targeting.

The fantasy is not commanding a giant fleet. It is being inside a diesel-electric submarine, trying to stay hidden long enough to understand what you are looking at. Somewhere ahead, there is a ship. Maybe a convoy. Maybe an escort. Maybe a silhouette barely visible through the periscope. The player's job is to turn fragments of information into a firing solution.

Not by pressing an automatic lock-on button.

By measuring.

That distinction matters. Many combat games make targeting feel like permission: place the cursor over the enemy, wait for the game to confirm the lock, then fire. Sinking Steel is aiming for a different kind of satisfaction. The player should feel that a successful shot was earned through observation, patience, and judgment.

A good torpedo solution depends on several questions. What type of ship is it? How long is it? How far away is it? How fast is it moving? At what angle is it crossing your bow? Where will it be when the torpedo arrives?

Each question becomes a small interaction.

The player uses the periscope to identify the target's silhouette. A recognition book helps compare ship profiles, lengths, mast heights, and class notes. The game should not automatically tell the player what the vessel is. Classification is part of the play. A small freighter, a large freighter, and a tanker should feel meaningfully different because their dimensions affect the solution.

Range can be estimated through stadimeter-style measurement. Speed can be estimated by observing how long the target takes to cross a known reference. Angle on bow can be judged from the target's apparent heading and silhouette. None of these measurements need to be brutally realistic to become interesting, but they need to be understandable and consequential.

The torpedo data computer, or TDC, becomes the center of the ritual.

In Sinking Steel, the TDC is not just a decorative panel. It is the player's bridge between perception and action. The player feeds it a target class, range, speed, bearing, and angle on bow. The machine then represents a solution, but the quality of that solution depends on the quality of the player's inputs. Bad data creates bad shots. A stale range, a misread speed, or a wrong bow angle can turn a confident attack into a clean miss.

This is the kind of failure we like.

Not random failure. Not unfair failure. Mechanical failure.

The torpedo misses because the player fired on outdated information. The shot runs behind the target because the speed estimate was too low. The spread looks good but passes in front because the angle on bow was wrong. These are not punishments from the designer. They are consequences from the system.

That is what makes the eventual hit satisfying.

When a torpedo strikes, the player should remember the work that led there: the cautious approach, the depth change, the slow periscope raise, the silhouette comparison, the speed timing, the range estimate, the TDC adjustment, the final bearing, the order to fire, and then the waiting.

The waiting is important.

A torpedo shot is not instant feedback. The weapon leaves the tube, runs through the water, and the player is left with doubt. Did I fire too early? Did the target turn? Did I expose the boat? Was that escort closer than I thought? The time between launch and impact is where the player feels the weight of the decision.

But Sinking Steel is not only about math. It is also about stealth.

A submarine is powerful because it is hidden. Once that advantage is lost, every action becomes dangerous. Depth, speed, and exposure risk must matter. Running on the surface should be faster but riskier. Periscope depth should allow observation but increase the chance of being seen. Deeper running should improve safety but reduce vision and slow the player's ability to build a solution. High speed may help reposition, but it should also make the submarine easier to detect.

This creates a second layer of tension. The player does not have unlimited time to calculate. Staying too long at periscope depth may invite detection. Moving too fast may create noise. Remaining too deep may mean losing the target. The perfect shot is not only a mathematical solution. It is a tactical window.

That is why Sinking Steel is being built with both a tactical engagement layer and a wider patrol layer in mind. On the patrol map, the player searches for contacts, manages speed, depth, fuel, battery, risk, and approach angle. In the engagement view, the world becomes more focused: bearing, distance, silhouettes, torpedo tubes, and the geometry of attack.

The goal is to make a game that feels serious without becoming bloated.

We do not need photorealistic oceans to make submarine warfare tense. We need good information design. We need the periscope to feel useful. We need the map to communicate uncertainty. We need the target book to matter. We need the TDC to be readable. We need the player to understand why the shot hit or missed.

That is the same design philosophy behind our other prototypes. Skyline Kites turns a sky duel into tension and line geometry. Interrex turns a shooter into movement and firing angles. Grim Pilgrim turns combat into timing and discipline. Sinking Steel turns naval combat into measurement, patience, and stealth.

A small submarine game can feel deep if the core loop is honest. Find the target. Identify it. Measure it. Stay hidden. Build the solution. Fire. Wait.

The hit is only the final sentence. The story is the calculation that came before it.