Preparing the interactive tool. Please wait; the guide and worked examples remain available below.

Browser-local worksheet · no game or save access

Forever Skies branch and co-op check

Enter only details you are comfortable sharing. This creates a draft in this tab; nothing is uploaded or submitted.

Draft preview

Forever Skies branch and co-op check — notes from my session
Guide: undefined
Platform: PC
Displayed version/build: unknown
Branch/world/session: unknown
Mode or context: unknown
Observed (not inferred): not entered
Already changed/tested: nothing entered
Next check: Record current/Legacy branch, displayed build, host/client role, and whether the save predates 1.7.0.

The values stay in this browser tab and are cleared on reload. This does not read or change saves, inspect your account, verify a diagnosis, post to a forum, or transmit data. Remove usernames, invite codes, server addresses, and other private information before sharing a report elsewhere.

Verify before launching the old world

The official announcement described a one-way preservation option: a Legacy branch for revisiting pre-1.7 saves, without future content updates. It did not say that opening a Legacy save in the newer branch converts it safely. Keep the original untouched and never rely on Steam Cloud as your only copy.

  1. In Steam Properties, read the currently displayed branch names and note the installed version before changing anything.
  2. If the save predates 1.7.0, locate the developer's dated compatibility post and verify that the Legacy option is still offered; do not assume it is available on non-Steam platforms.
  3. Back up the save using the current platform-supported method and keep an untouched copy outside the game's active save folder.
  4. Select the matching branch only after confirming the name/build in Steam, then test a duplicate save.
  5. Inspect the airship and one objective; avoid saving over the original if the world fails to load as expected.
  6. For a new co-op playthrough, use the current build on a separate world rather than trying to migrate an old solo save.
GoalBranch decisionBoundary
Visit an old pre-1.7 airshipCheck whether Steam Legacy remains offeredDated announcement; option may change
Play current content/co-opUse current Main branch with a separate saveDo not assume old saves convert
Console or other storefrontCheck platform's current support/update channelSteam branch steps do not transfer automatically
Unsure which build owns a saveKeep copy untouched and verify firstA successful load is not a compatibility guarantee

References: Forever Skies developer: save compatibility and Legacy branch announcement · Forever Skies on Steam

Keep an old-build report useful

A report that omits the branch can confuse two valid but different game states. The local form records the branch and host/platform context without reading files.

  1. Record exact Steam branch and displayed build.
  2. State the save's approximate creation build, if known.
  3. Describe whether the save was copied or opened directly.
  4. Ask the external community only for the same branch; label responses as player experience, not official compatibility evidence.

References: Forever Skies Steam Community Discussions

Before you play

  • I checked the branch options available today, not only the old announcement.
  • I have an untouched copy before testing.
  • I keep old-save and current co-op worlds separate.
  • I do not imply Steam Legacy instructions apply to consoles.

Frequently asked questions

Does this mean every old save is lost?

No. The developer announced a Legacy branch to revisit earlier saves; it did not guarantee branch availability or compatibility for every platform/current build.

Can the tool test my save?

No. It only assembles entered details in the browser and cannot open or modify game files.

Sources & revision notes

Editorial revision: November 7, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

  1. Forever Skies developer: save compatibility and Legacy branch announcement (Official)

    Developer announcement from November 2024. It said the upcoming 1.7.0 co-op update would make earlier saves incompatible and announced a Steam Legacy branch for revisiting old saves without future updates. Because the game later released and continued to update, verify the branch and current build in Steam before acting; this is not a claim that 1.6 saves are current.

  2. Forever Skies on Steam (Official)

    Official product listing checked November 7, 2026; it describes solo and online co-op for up to four players (host plus three). Verify the current edition and lobby UI; this guide does not test networking or save transfer.

  3. Forever Skies Steam Community Discussions (Community)

    External player-generated discussion and not official support; identify the Steam branch, displayed version, host/client role and whether a save predates 1.7.0.

What changed in this revision

November 7, 2026: first publication. Clarified the 1.7 notice is historical and made branch availability a live Steam check; no save migration was tested.

How we research and correct guides

No affiliate links or paid placement. Commercial disclosure.