What happened to the demo?
The official June 5 announcement introduced the original demo. 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. A later launch Q&A explained that the demo had been taken down and would be brought back after reworking.
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. These statements describe different stages of the same demo's history, rather than two conflicting current download offers. The important distinction is availability at the time you want to play.
A historical release announcement proves that the demo existed, but it does not override the later withdrawal notice. Likewise, an old video showing a successful session does not establish that the viewer can still install that build. 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 is the demo different from the main game?
The demo had a separate Steam app identity from the main game's app 3447280. 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. Its limited content included five classes, four environmental themes and two settlement themes in the collected descriptions.
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. The main Early Access description instead advertised 18 classes, so the demo count should not be used as the full game's total. Product identity also matters when reading technical advice.
A June demo patch can explain an editor dependency or document a simulation change without representing every feature of the later main game. Keep the build and date attached to any numerical claim, limitation or observed problem. 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.
Which old tutorials are still useful?
The revised June recordings illustrate that building artwork and housing behavior are different layers. 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. A House POI connects a suitable building to the housing system, while a faction and City Zone connect resident templates to an initial population.
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. These concepts were corroborated by developer explanations and multiple independent tutorial recordings. Other recorded details are more sensitive to version changes.
Older tutorials can involve more manual template creation than later versions, because the June 15 update added default prefab content to world creation. Watching an early recording without that context can make the setup process look more complicated than a later default-content world. 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.
Why do demo videos disagree about time and simulation?
The demo received several June patches affecting time controls, housing, families and population behavior. 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. Patch 4 documented higher speed options and a changed calendar, while later simulation work addressed hunger, nutrition and family-related systems.
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. A video recorded before one of those updates may correctly show a different behavior from a video recorded afterward. For example, the documented 48-minute year at maximum speed belongs to the June 11 time configuration.
It should not be converted into a universal promise for all subsequent versions or used to calculate an unsupported birth rate. Simulation speed, population growth and actual rendering performance are separate questions. 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.
Can you still join a test to try it?
Historical playtests were organized in phases and sometimes coordinated through Discord. 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. The collected sources do not establish a currently open test, a guaranteed key or an unrestricted replacement for the withdrawn demo.
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. A community invitation remains a communication channel rather than proof of an entitlement to play. The main game's October 28 Early Access announcement is a separate release event.
Our early October 28 store check still showed coming soon, so that snapshot should remain dated. Use a later official availability announcement or the current store state to establish whether the main product can now be installed. 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 should you check when a new demo is announced?
Confirm that the announcement actually describes a public demo and names its availability period. 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 compare its content and editor behavior with the main-game materials, rather than carrying forward every limitation of the June version.
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. A reworked demo may change what older tutorials demonstrate, but the sources collected here do not specify those future changes. Until a new version is verified, treat the June footage as historical learning material.
It can help you understand POIs, City Zones and templates before you begin a worldbuilding project. It should not be used to advertise a working download, a current bug or a fixed feature limit for a demo that has not yet been confirmed to return. 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.