SeaWar Sandbox V1 is finished. Not paused, not on hiatus, not waiting for the right moment. Finished. There will not be a SeaWar V2, and with support for both platforms ending in September 2026, this is the natural moment to say so plainly rather than let the project fade out without a word.
This is not a sad post. It is the opposite. But it deserves an honest accounting, because a studio that only publishes good news is a studio nobody should believe.
What SeaWar was
A free single player naval combat sandbox. You started on a salvage raft with nothing, you fought your way up through better hulls and heavier guns, and at the end there was a Demon Lord waiting. It ran on Windows and later Android, entirely offline, with no account, no telemetry, and no online check of any kind.
Every system in it was built rather than bought. The ship movement, the cannon volleys, the harpoons, the enemy behaviour, the progression curve. That was the founding principle of this studio and SeaWar was the proof that one person could actually hold to it and still ship something.
It launched complete. No early access, no roadmap of promises. That mattered more to us than any single feature in it.
What went right
- It shipped. The overwhelming majority of solo projects do not. This one went from nothing to a finished, downloadable, playable game with a start and an end.
- The combat felt good. Not deep, but readable and satisfying, which is harder and matters more.
- The Android port worked. Touch controls on a naval game could easily have been a disaster and were not.
- The distribution chain worked end to end. Website, launcher, installer, update flow, all built and all functioning. That infrastructure outlives the game it was built for.
What went wrong
The honest list is shorter and more important.
It was single player, and it should not have been. This is the whole thing. Every piece of feedback we valued most came down to the same shape: someone had a good moment and wanted to tell somebody about it, and there was nobody in the water to tell. A naval game is fundamentally about the horizon and what might be coming over it. When the answer is always a scripted enemy, the horizon stops being interesting.
Scope was set by what one person could finish, not by what the idea needed. That is a defensible way to ship a first game. It is a bad way to build a second one.
Distribution friction was worse than we modelled. A side loaded APK and an unsigned Windows installer both ask the player for trust before they have any reason to give it. We wrote a whole trust section on the download page to compensate. The better answer is not to need one.
Why we are not making SeaWar V2
Because fixing the real problem would not produce SeaWar V2. It would produce a different game wearing the name.
Adding multiplayer to SeaWar is not a feature you bolt on. It changes the engine, the architecture, the economy, the progression, the balance, the anti cheat surface, and the entire question of what the player is doing and why. Every one of those is a foundation, not a feature, and you do not retrofit foundations. You pour new ones.
So calling the next thing SeaWar V2 would be a marketing decision dressed as a technical one. We would rather be straight: the sandbox is done, we learned what it had to teach, and the next project starts from the lesson rather than from the code.
What happens to your copy
Nothing. This is worth repeating because plenty of studios have said "end of support" and meant "we are switching it off". We cannot switch SeaWar off. It has no server, no login, and no license check. If it is on your machine it stays on your machine, saves and all, working exactly as it does today.
The guide stays online. The news archive stays online. The EULA and licence pages stay online. What comes down in September is the download link and any expectation of future patches.
What we would do differently
If someone reading this is about to start their own first game, these are the four things worth stealing from our mistakes.
Decide whether it is multiplayer before you write anything. Not as a feature, as an architecture. Single player and shared world are different programs that happen to look similar in screenshots. Choosing late means choosing twice.
Solve distribution first, not last. We built a good game and then discovered that getting it onto a stranger's machine was its own project, complete with operating system warnings, store policies, and a trust problem we had to write copy to solve. Distribution is not the final step. It is a design constraint that should shape what you build.
Ship complete is a promise worth keeping and a trap worth seeing. We are glad SeaWar launched finished rather than as early access. But a finished single player game cannot respond to what you learn after launch, and everything we learned arrived after launch.
Build the infrastructure once and reuse it. The website, the release pipeline, the analytics, the legal pages, the update flow. None of that was wasted when the game ended, and all of it is running for the next project already. It was the best time investment of the whole thing.
What a first game is actually for
Not money. SeaWar was free and was always going to be.
A first game is for proving to yourself that you can finish one. The industry is full of ambitious unfinished projects and almost empty of people who have carried something from an empty folder through to a working download. Once you have done that once, the second project starts from a completely different place: you know the shape of the whole path, including the ugly parts nobody writes devlogs about.
By that measure SeaWar did its job exactly.
What comes next
Something bigger, built on the one lesson that mattered: the sea needs other people on it.
We are not going to tease it for months. The next post is about what we are building and what it is built with, and it is coming soon.
Thank you to everyone who downloaded a small naval game from a studio nobody had heard of, played it, and told us what they thought. That feedback is the entire reason the next project exists and the reason it looks the way it does.