What do the confirmed playtest announcements say?
The research includes official testing information from 2025. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. Those announcements describe development-stage access and community involvement before the October 2026 Early Access plan.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. They establish that tests took place, but they do not establish a standing promise that every interested player can join at any later date. Testing information is especially sensitive to timing.
A sign-up opportunity, internal test or invitation can apply to one phase of development and end before another begins. Read the date and the described audience before deciding whether an announcement applies to your account today. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Is Discord the place to get access?
The official Discord is a confirmed community channel associated with testing discussions. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. It can help you follow developer notices and distinguish a new testing phase from an old one.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. Membership by itself is not evidence that a Steam entitlement or download has been granted. The collected material does not verify a current request form, a guaranteed invitation schedule or an access button that works for every visitor.
This guide therefore does not promise keys or describe an unverified application sequence. If a new test is announced, its own instructions should determine what participation requires. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
How does a playtest differ from the demo?
A playtest is a development testing phase, while the original demo was a separately listed public sample released in June 2026. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. That demo was later withdrawn, and its reworked return had no confirmed date in the collected launch material.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. Neither fact creates a guaranteed alternative route into the other product. Videos labelled as demo gameplay should be read in that context.
They may show tutorials, templates or bugs from a particular public demo build rather than the contents of an invitation-only test. A useful gameplay demonstration is not automatically a reliable explanation of present-day account access. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Is the main Early Access release another playtest?
The main Steam game has app identifier 3447280 and an announced Early Access date of October 28, 2026. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. Our research checked the store early on that date and still observed coming soon.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. That snapshot establishes the state at the time of collection, rather than proving a completed launch or an ongoing test later that day. Keep release stages separate when searching for access.
The main product, the withdrawn sample and historical testing each have their own context. A past playtest announcement does not replace current store information about the main release. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
What can historical testing footage teach you?
Recorded builds can demonstrate the relationship between editors and the simulation. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. For example, a settlement needs more than decorative buildings: housing uses House POIs, and human residents depend on faction and City Zone setup.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. Those dependencies have stronger support than any assumption that an old testing invitation still functions. Footage can also reveal features that were attempted without success.
A failed character-control interaction or a rejected war command should not become a guaranteed current bug or a reliable step-by-step tutorial. Combine a recording with dated developer explanations before using it as mechanical advice. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
How should you assess a new testing notice?
First establish who published it, when it was posted and which build or phase it describes. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. Then distinguish the opportunity to apply from actual acceptance and access.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. Those are separate states even when the same community announcement discusses all of them. For practical planning, follow official Steam announcements and the official community rather than relying on an undated search snippet.
For gameplay preparation, use the beginner guide and topic pages to learn confirmed worldbuilding concepts. This keeps the question of how the simulation works separate from the question of whether a particular testing phase is currently admitting players. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Sources and verification
This answer cross-checks developer and Steam material against independent reporting or gameplay footage. Details from older demos are identified as historical because interfaces and availability can change between builds.