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.

Host-side checks before the lobby

Because save compatibility changed around 1.7.0, branch identity matters alongside the usual lobby setup. The official capacity is four total, not four guests plus a host. This guide intentionally avoids claims about cross-play or automatic world migration.

  1. Ask every player to read the installed version and branch from Steam before the session.
  2. Choose one current-build world intended for co-op; keep any historical Legacy save separate and backed up.
  3. Have the host verify the lobby's displayed player capacity. Count the host as one of the four listed online co-op players.
  4. Send invitations only after the group's branch/build labels match; if a guest cannot join, record the error and compare one version at a time.
  5. Do not transfer or overwrite a save to fix an invite problem unless the current official support instructions explicitly say it is safe.
  6. If connection fails, record host/client roles and exact error; the local tool sends nothing and cannot inspect networking.
PreflightCheckNot established by source
Player countUp to four online co-op players total on Steam listingMore than four or extra host slot
Build/branchMatch the labels shown by players' Steam clientsCross-branch join support
World ownershipAgree which host save is being usedAutomatic transfer of host save to guests
PlatformSteam PC evidence is explicitCross-play with console/storefront

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

Ask for help without exposing a save

A join failure is easier to triage if the host and guest versions and exact error are recorded. Never post login credentials, invite tokens or raw save files to an open discussion.

  1. Record the host's branch/build and the guest's branch/build.
  2. State whether the host is on a current or Legacy save.
  3. Copy the exact lobby error and platform/storefront.
  4. Use Steam Discussions for peer troubleshooting only; verify any claimed cross-version rule with the developer.

References: Forever Skies Steam Community Discussions

Before you play

  • I counted host within the four-player total.
  • The group compared branch/build labels.
  • A current co-op world is separate from an old Legacy save.
  • I did not assume cross-play or cross-branch compatibility.

Frequently asked questions

Can four friends join the host?

The Steam listing says online co-op for up to four players total. That ordinarily counts the host in the listed maximum; check the in-game lobby's live limit.

Does the old announcement confirm current co-op compatibility with Legacy?

No. It described Legacy as a separate non-updating branch and did not establish that Legacy and current builds can join each other.

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 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.

  2. 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.

  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. Added host-side player/build checks bounded to Steam's four-player listing; no multiplayer session was tested.

How we research and correct guides

No affiliate links or paid placement. Commercial disclosure.