Ten days ago we said SeaWar Sandbox V1 was finished and that there would be no SeaWar V2. This post is the other half of that sentence: what we are building instead, and why it looks nothing like what came before.
Short version. The new project is a naval game that runs in your browser, with other players in the water, built from scratch on web technology rather than on a general purpose game engine. Everything about that sentence is a deliberate reversal of a decision we made for SeaWar.
The lesson we could not design around
SeaWar was single player. Every serious piece of feedback we got eventually circled the same drain: someone did something they were proud of, and there was nobody there.
You can patch a lot of things. You cannot patch loneliness into company. A naval game is built on the horizon and the question of what is coming over it, and when the answer is always a scripted spawn, the horizon quietly stops mattering. That is not a balance problem or a content problem. It is the shape of the thing.
So the new project starts from the opposite premise: the sea is interesting because other people are on it. Everything else follows from that, including the technology.
Why not the same engine again
SeaWar was built with a conventional game engine, and it did its job. But the requirements for the new project are almost the inverse of the old ones, and they point somewhere else entirely.
The new game needs to be instantly reachable. Not a 110 megabyte installer, not a launcher, not an APK you have to talk Android into trusting, not a store review process that takes months for a studio nobody has heard of. A link. You click it, you are in the water.
That single requirement rules out most of the conventional path. It rules in the browser, and once you are targeting the browser seriously, dragging a heavyweight general purpose engine along behind you is a cost with no matching benefit. You end up shipping megabytes of machinery to do things you could do directly, and fighting the runtime for control of the things you actually care about.
What it is built with
A custom stack, written for this game and nothing else.
The client is TypeScript, rendering to the browser with a lightweight rendering layer, and every game system on top of it is ours: movement, camera, interpolation, input, interface, effects. The server is TypeScript as well, running a real time authoritative simulation, so the world does not live in your client and cannot be argued with from it.
That last part deserves its own sentence, because it is the difference between a toy and a game with other people in it. The server is the authority on anything that matters. Movement, combat, damage, rewards, economy, progression. The client draws what the server says is true and asks politely for the rest. If you have played browser games where a determined player could simply decide they had more gold, you know why this is not a detail.
No off the shelf engine, no template, no asset packs. That has been the studio's rule since the first line of SeaWar and it has not moved. It is slower. It is also the only reason the game can be exactly the shape we want rather than the shape a general purpose tool makes convenient.
What we are keeping from SeaWar
More than you might think. The parts of SeaWar that worked are the parts we spent the longest getting right, and they transfer:
- Ship movement with weight. A vessel that turns like it has mass, not like a cursor.
- Readable combat. Volleys you can see coming, damage you can understand, states you can read at a glance during a fight.
- Progression that means something. Hulls, guns, and ammunition that change how you fight rather than just raising a number.
- Respect for the player. No dark patterns, no manufactured urgency, no telemetry harvesting.
What is genuinely new
A persistent world with other captains in it. Seas you travel between rather than one arena. Progression that survives you closing the tab. Alliances, rivalries, and the specific tension of seeing an unfamiliar sail and not knowing what it wants.
And crucially, an economy and a combat model designed from day one for a world where the other ship might be a person. That is a completely different engineering problem from a world where every enemy is a script, and it is the reason this had to be a new project rather than a patch.
Why the ashes framing is fair
Because nothing here is a fresh start pretending the last two years did not happen. The website you are reading, the release infrastructure, the analytics, the legal groundwork, the art pipeline, and above all the accumulated knowledge of what makes a ship feel good to steer, all of it came out of SeaWar and all of it is being used.
SeaWar was not a failure. It was the tuition. It shipped, it was finished, and it taught us the one thing we could not have learned any other way: build the sea for people, not for one person.
What changes about how we release
Moving from a finished offline product to a live shared world changes the studio's relationship with its own game, and it is worth being upfront about what that means in practice.
Ship complete becomes ship correct. Our founding promise was no early access and no roadmap of unfulfilled features. A live game cannot be finished in the same sense, so the promise adapts rather than disappears: every system a player can reach should be finished, and anything that is not ready stays completely hidden rather than half available.
That is not a slogan, it is an actual mechanism. Unfinished systems sit behind a registry that makes them invisible and non functional for players, and they only switch on when they are genuinely done. A player should never meet a half built feature and conclude the whole game is half built.
Testing becomes public in stages. An offline game gets tested privately and then released. A shared world has to be tested with actual people, because the interesting failures only appear when strangers with different intentions are in the same water. That means alpha and beta phases, and it means being honest that early phases will be rough in specific ways.
Progress may reset between phases. When you are still tuning an economy, old progress stops meaning anything. We will announce every reset in advance rather than surprising anyone on login.
The one thing that does not change
No dark patterns. No telemetry harvesting. No manufactured urgency, no countdown you can pay to skip, no design whose real purpose is to make waiting uncomfortable.
Those were the rules for SeaWar when there was nothing at stake, which is the easy time to have principles. They are the rules for a live game too, which is the part that actually counts.
What happens next
The project has a name, and the next post is the announcement. It is not far away.
If you would rather hear it before the rest of the internet does, the Discord link is in the footer of every page on this site.