The fleet ↓
USS Missouri · 1945
Historical photograph / Not gameplay
01 / THE SURFACE FLEET
Ship roles
Select a class to read its proposed role. The photographs are historical examples, not a playable roster.
Swipe to explore ship classes ↔
Yamato · Imperial Japanese Navy · Sibuyan Sea, 24 October 1944 · U.S. Navy aerial photograph / National Archives 80-G-325953
BB / DESIGN DIRECTION · JAPAN
Battleship
Proposed role: heavy gunfire from the battle line, with allied ships protecting the flanks.
HISTORICAL ROLE EXAMPLES
Yamato / Missouri
These photographs illustrate proposed roles, not a confirmed playable roster. The repair ship shown is USS Vestal, not USS Medusa. Neither is confirmed playable.
02 / ABOUT THE GAME
About the game
The game is in development. A communications wheel has been built, and ships and boats are being checked in internal playtests.
PROPOSED DESIGN
The sections below describe design goals, not a list of features available to play. See Development for recent work. There is no public game download.
01 / THE FIGHT
Manual aiming
You steer one ship, lead moving targets and choose when to fire. The goal is to make aim, timing and maneuver matter while keeping gun readiness and hit feedback clear.
Combat scope
+
Random variation should have a limited effect on outcomes. Playable aircraft carriers and submarines are outside the project’s scope.
02 / THE WATER
Movement and detection
Maps should leave room to flank, screen an ally or retreat. Cover and long-range fire should be useful without making one position safe indefinitely.
Map requirements
+
Land should block radar and hydro detection. Ships need practical responses to threats, which may depend on a teammate or a change of position rather than winning a duel alone.
03 / THE FORMATION
Team roles
The five proposed ship classes are described in the fleet tabs below. Scouting, escort, objectives and recovery should count toward contribution alongside damage.
Scoring
+
Rewards should reflect useful actions, not simply the class selected. Scoring, attribution and rules to prevent farming rewards still need design and playtesting.
04 / THE AFTERMATH
Damage and recovery
Damage should affect what a ship can do. Towing a disabled ally, covering its retreat and making limited repairs are proposed team tasks.
Repair limits
+
Recovery should restore some useful capability, not reset a ship to full strength. The limits, risks and support-ship controls are still being designed.
REPAIR SHIP REFERENCE
USS Pensacola alongside USS Vestal · Espiritu Santo, 17 December 1942
U.S. Navy / 80-G-33862 · Historical reference · not gameplay
05 / THE SHIPS
Historical ships
The fleet is based on WWII ships that were actually built. National differences in capability should remain; fictional ships and crossovers are outside the setting.
Models and gameplay
+
Speed, distance, damage and repair may be adjusted for gameplay. Models use dated references and rights review, not another game’s assets, code or designs. The photographs on this site are historical references, not finished game art.
06 / THE GROUND RULES
Purchases and matchmaking
The commitments are no pay-to-win, premium ammunition, paid randomized containers or paid keys. Purchases must state what they contain and must not sell a competitive advantage.
Matchmaking
+
Matchmaking should seek competitive matches without manipulating wins or losses. Ship capability and team roles need to be accounted for. The system is not finalized, and no public matchmaking service is available.
07 / THE LONG VIEW
Ship progression
The proposed progression system uses per-ship specializations, mostly sidegrades and modest, bounded improvements. A stock ship should remain competitive.
Unsettled rules
+
Specialization branches, equipped choices, respec rules, ship tiers and the economy are not settled. Historical differences between ships still need to be accounted for in matchmaking.
08 / THE CONVERSATION
Player feedback
Community requests, discussion and votes are intended to inform development. Spending or creator status should not buy extra voting influence.
Participation
+
Feedback from support players should count alongside combat roles. Criticism is welcome; abuse and cheating are not. Security, accessibility and essential maintenance should not depend on a poll. This site does not provide voting, moderation or appeals services.
03 / UNDER DEVELOPMENT
Development update
20 November 2026 / Internal development build
Juneau’s whaleboats had a snagging problem. After revisions, development playtests verified that they cleared the surrounding geometry. A communications wheel has also been built. King George V’s bridge, foremast and boats have been revised, and Emden’s hull, bridge and funnels have been remodeled against frame plans. These checks were internal, not a public release or a final roster announcement.