Skip to content
Emberville PatchEmberville

Start typing to search this wiki.

EN
Field notes

Demo → EA save expectations

What Steam Confirms about Emberville saves (Cloud, Save Anytime) versus Unknown Demo→EA carry-over — no invented migration promises.

Demo → EA save expectations

At a glance

Content Angle
Demo to Early Access save and progress expectations — Confirmed vs Unknown
Evidence Policy
Confirmed = Steam store categories/text; Unknown = Demo→EA carry-over until official or Observed

Contents#

  1. Purpose
  2. Confirmed on Steam today
  3. Demo → EA carry-over (Unknown)
  4. Player checklist before EA Day-1
  5. Editor logging rules
  6. Related pages

Purpose#

Players ask whether Demo progress carries into Early Access. This note separates what Steam App 2295170 Confirms today from what stays Unknown. No invented migration promises, redeem codes, or build IDs.

Confirmed on Steam today#

Re-checked on the Steam store page (2026-10-14):

ClaimGradeNote
Steam App ID 2295170ConfirmedPrimary store URL
Studio / publisher Cygnus CrossConfirmedStore + cygnuscross.com
Planned EA date Oct 27, 2026ConfirmedStore release-date string (coming soon)
Steam Cloud listedConfirmedStore feature category
Save Anytime listedConfirmedStore feature category
Platforms Windows + Linux (SteamOS)ConfirmedStore platforms
Demo → EA save / unlock / estate carry-overUnknownNot stated on store page
Exact Demo build ID / cloud namespaceUnknownNo stable public string here

Steam Cloud and Save Anytime describe the full game listing. They do not Confirm that a Demo cloud slot migrates into the EA product.

Demo → EA carry-over (Unknown)#

Until Cygnus Cross or the Steam page states it:

QuestionGrade until evidence
Do Demo saves open in EA?Unknown
Do Demo unlocks / villagers / estate transfer?Unknown
Is there a one-time import prompt?Unknown
Community “it carried for me” postsUnverified until retested (Observed with build + clip id)

Prefer empty cells over invented answers. Do not paste second-hand “100% carries” lists.

Player checklist before EA Day-1#

  1. Note your Demo build marker (in-game string or visible Steam build).
  2. Screenshot estate / unlocks you care about (evidence id).
  3. On EA Day-1, try load once; log Observed with UTC date, build, action, result, clip id (Pre-EA Observation log).
  4. Upgrade a cell only when the store/studio posts Confirmed text — not from wishlists alone.

Editor logging rules#

  • Confirmed: store/studio strings about saves or migration only.
  • Observed: self-test on a recorded Demo or EA build.
  • Unverified: trailer or forum claim without retest.
  • Unknown: default for Demo→EA progress until evidence exists.

Pair Day-1 Diff rows with the EA Day-1 Diff evidence sheet. Keep inheritance numbers on the stub matrix — never invent them here.

Rights#

Steam and Cygnus Cross materials remain with their owners. This page records evidence grades for save expectations, not a mirror of marketing assets.

Frequently asked questions

Does Steam Cloud mean my Demo will carry into EA?

No. Cloud on the store page is Confirmed for the product listing. Demo→EA migration is a separate claim and stays Unknown until official text or an Observed self-test.

Can I trust a Discord ‘it carried’ screenshot?

Treat it as Unverified. Retest on your build, log date/build/result/clip id, then mark Observed.

Where do I record a Day-1 load attempt?

Use the Pre-EA Observation log row template, then link Diff cells only after grading on the Day-1 Diff evidence sheet.

Sources & evidence

  1. Emberville on Steam (App 2295170)OfficialAccessed Oct 14, 2026
  2. Cygnus Cross (studio site)OfficialAccessed Oct 14, 2026