Reference: the data we can actually stand behind

This section is tables, not prose. Two pages, both built the same way: confirmed values are stated as confirmed, and unpublished values are left visibly blank rather than filled with something plausible.

For an unreleased game that is a strange thing to publish. A reference section with holes in it looks unfinished. It is, unavoidably — and the alternative is worse, because a spec table with invented numbers is indistinguishable from a correct one until the game ships and someone checks.

What is in here

Two pages so far:

• System requirements — four confirmed lines, six fields still marked To Be Announced, on both Windows and Mac
• The arsenal — 38 named assets across infantry sources, vehicles, helicopters, artillery, naval fire, fixed-wing strike and base structures

Both are short by the standards of a normal reference section. Neither is padded.

System requirements: four lines confirmed, six not

The Windows block confirms: 64-bit Windows 10, DirectX 11, 10 GB of available storage, and a 64-bit processor and OS.

The Mac block confirms one thing that will rule people out: Apple Silicon required. Intel Macs are outside the stated requirement. That line is easy to skim past when you are hunting for a GPU name, and it is the single most consequential confirmed requirement on the page.

Then the holes. Processor and graphics are listed, in the store page's own text, as "To be announced". Memory does not appear at all — not at minimum, not at recommended. The recommended tier contains exactly one line: "Requires a 64-bit processor and operating system".

The developer has attached a deadline to this themselves: "Final system requirements will be announced before release." That is a commitment, which is why the page currently reads as provisional rather than as final.

Linux is not listed as a supported platform. Steam Deck compatibility has not been rated, and the absence of a Linux build is the reason it cannot be assumed.

The arsenal: 38 names, zero stats

The list is more complete than you would expect from an unreleased game, because ProjectAlive has named a lot of hardware in the store page description. Tanks, Bradleys, LAVs, Humvees. Apache and Viper attack helicopters, Black Hawks for fast-rope deployment and rooftop landings. M777 howitzers, HIMARS, destroyer guns, Tomahawks. F/A-18s, F-15E, F-35B, A-10, AC-130J, MQ-9. HESCO walls, concrete walls, gates, scaffolding, gun nests, CIWS, mortar pits, ammo depots, fuel points, lighting.

What it does not contain is a single number. No damage, no range, no cooldown, no cost, no build time, no capacity.

The one entry that other coverage misses is the AH-6M Little Bird. It never appears in the store page text, but ProjectAlive published a devlog dedicated to it and to flight deck takeoffs. That is a first-party source, and it is the only public confirmation the aircraft is in the game. Finding it required cross-checking the video series against the store text rather than reading one source.

Two structural facts in the arsenal list matter more than the names:

• Ship magazines are finite — fire support depletes
• Heavy weapons bring buildings down — fire support damages your own cover

Those turn the fire support list from a power fantasy into a resource decision, and they interact with the supply line described in the mechanics section.

Why so much is labelled Unknown

Because it is unpublished, not because it is hard to find.

We checked three sources for this section: the Steam store page description, the appdetails API, and the official news feed (ISteamNews). For the arsenal list we added a fourth: the official devlog videos.

What is missing after checking all four is missing from the public record. That includes district names, unit costs, ammo capacity, wave composition, whether destroyed structures can be rebuilt, and the GPU requirement.

We could have filled several of these convincingly. Unit stats for a game like this follow predictable patterns, and a table of plausible-looking numbers would have looked far better than a table full of blanks. It would also have been worthless the moment the game shipped.

Three ways to use this section

If you want to know whether your machine will run it

Read system requirements and use the four-step self-check at the bottom. It answers the questions that are answerable — 64-bit, DirectX 11, 10 GB free, Apple Silicon on Mac — and is honest that the CPU and GPU questions cannot be answered yet.

If you want to know what is in the game

Read the arsenal, but read the source column. Entries marked Devlog are not in the store page text, which means they are invisible to anyone who only read the store page.

If you want to cite something

Everything is dated. Each table carries a <SourceNote> with the retrieval date, and each page carries a correction block. If you need to quote a figure, quote the date with it — this game's data will change.

How the labels work

Four levels, used consistently across the site:

The third level is currently the most dangerous one on this site's subject. Several third-party trackers report figures for Ebbtide that contradict the developer's own announcements — one listed a single Steam follower while ProjectAlive was posting about 15,000 wishlists on the same day. When a first-party post and a third-party estimate disagree, the first-party post wins, and we say so rather than averaging them.

When this becomes a real reference section

When the game ships and can be played, every Unknown on these pages becomes an Observed entry. District names get filled in from in-game observation. Unit costs come from the interface. Whether structures can be rebuilt gets answered by trying it.

Until then, this section is deliberately thin. A reference page that admits what it does not know is more useful than one that does not, because you can tell which parts to trust.