Start here: three questions before anything else

Most game wikis assume you already know which game you are looking at and that it is out. Neither is safe with Ebbtide. Three separate entities use the name, and the game has not been released, which means a large share of what a normal guide would cover does not exist yet.

So this section is deliberately short and deliberately unexciting. It answers three questions in order, and each answer changes what you should read next.

First: is this the Ebbtide you want?

There is a real chance you do not want this game at all. Search the bare word Ebbtide and the top results are a women's health product, a 1994 Australian film and a dictionary entry. When we checked on 22 October 2026, none of the first five organic results were about the game.

If you arrived looking for dosage information, a film synopsis or the definition of a falling tide, you are in the wrong place and no page here will help you. The disambiguation page exists specifically to make that check take ten seconds instead of ten minutes.

If you did arrive looking for the game — the real-time zombie survival strategy title by ProjectAlive, on Steam, App ID 4915700 — then the name collision is mostly an annoyance rather than a problem. You just need to add a modifier when you search: Ebbtide game, Ebbtide Steam, Ebbtide ProjectAlive.

What the collision does change is how this site has to present itself. Every title on this site carries a distinguishing word — Steam, ProjectAlive, zombie — because a page titled simply "Ebbtide Districts" would compete with a trademarked product page and a Wikipedia article, and lose.

Second: has the game come out?

No. This is the single most important fact about this site, and it drives everything else.

As of 22 October 2026, the Steam storefront API returns coming_soon: true with the date field reading the literal string "Coming soon". There is no price, no review score, no achievement list, and no published CPU or GPU requirement. The store page itself says final system requirements will be announced before release.

That status has a consequence people often resist: there is no such thing as an Ebbtide walkthrough right now. Nobody outside the developer has played the game. Any page claiming to tell you how to beat a boss, which units are best, or how to optimise a build is generating that content from imagination.

We are not going to do that. It is the single easiest way to build a site that looks complete and is worthless, and it is exactly the failure mode that makes players distrust game wikis in general.

The release status page tracks this properly: what the API returns, what would count as a change, and the command you can run yourself to check.

Third: what can actually be known today?

More than you might expect, but less than a normal guide needs.

ProjectAlive has described the game's systems in unusual detail on the store page. We know the operations map becomes the battlefield with no loading screen. We know Los Angeles is split into 15 districts that slide from Hold to Crisis to Lost. We know ammunition and fuel can only be replenished at bases you hold, and that a hive mind called the Nexus hunts convoys and cuts roads. We know you can press TAB to take direct control of a single soldier, tank or helicopter.

That is enough to write a genuine mechanics breakdown that contains no invented numbers.

What we do not know is anything numeric. No unit costs, no damage values, no ammo capacity, no district names beyond the two the store page mentions, no confirmation of whether destroyed buildings can be rebuilt. That list is genuinely unpublished — we checked the store page, the appdetails API and the official news feed.

The discipline that follows from this is simple: we publish what is sourced and label the rest as unpublished, rather than filling gaps with plausible-sounding figures.

Three ways through this site

Different readers need different things. Pick the path that matches you.

If you have never heard of Ebbtide

Start with the disambiguation page to confirm you are in the right place, then read what the game actually is for the systems, then decide whether to wishlist based on the release status. Skip the reference section entirely — a spec table for an unreleased game is not useful to someone still deciding whether they care.

If you have been following the game since the store page went live

Go straight to the mechanics page and read the supply-line section, because that is the system the marketing underplays and the one most likely to decide your campaigns. Then read how it compares to They Are Billions, which is the comparison you are probably already making.

If you want the data, not the prose

The reference section is for you. System requirements tells you which four lines are confirmed and which six are blank. The arsenal lists 38 named assets with a source for each — including at least one, the AH-6M Little Bird, that appears only in an official devlog and not in the store page text.

The mistake we expect people to make

The most common wrong assumption about Ebbtide will be that it is a tower defence game or a They Are Billions variant.

It is not, structurally. Tower defence is about a fixed lane and a fixed budget. They Are Billions is about one colony on one map, and your failure condition is that the colony falls. Ebbtide's failure condition is distributed across 15 districts, each of which you can lose separately while the rest of the city keeps fighting. The store page states outright that you cannot save everyone.

That difference changes the whole shape of play. You are not solving a defence; you are managing an evacuation that keeps being interrupted by a defence.

How we check what we publish

Every factual claim on this site falls into one of four buckets, and we mark them visibly:

• Confirmed — the Steam store page, the appdetails API, or another first-party source
• Observed — something we tested ourselves in-game (currently unused, because the game is unreleased)
• Unverified — reported by a third party, not reproduced by us
• Unknown — we could not confirm it, and we say so

You will see Unknown a lot on this site right now. That is not laziness or hedging. For an unreleased game, a site that has no Unknowns is a site that is making things up.

What happens when the game ships

This section will be rewritten, not patched.

The moment coming_soon flips to false, every page saying "unreleased" becomes wrong, and that is a same-day fix. After that, the plan is straightforward: play the game, record what actually happens, and replace the Unknowns with Observed entries — district names, unit costs, whether structures can be rebuilt.

Until then, what you get here is a small number of honest pages instead of a large number of confident ones.