A current AppID 2523770 community guide reports that a joining client’s autosave may not always trigger reliably. Its cautious end-of-session sequence is: travel to a town, have the host complete a small merchant transaction and wait for the save icon, have the client do the same, let the client quit to the main menu first, and let the host end the session last. Treat this as a player workaround, not official Aspyr documentation.
1. Reach town
Finish the checkpoint and travel to a safe hub such as Bree before anyone disconnects.
2. Host trigger
The host buys or sells a cheap item, exits the merchant, and waits for the golden save indicator to finish.
3. Client trigger
The guest repeats the transaction and confirms the save indicator on their own screen.
4. Ordered exit
The client returns to the main menu first; only then does the host close the session normally.
Record ownership before the first long session
Name the campaign host and decide whether the same person will host every chapter. Record each player’s hero, level, last completed chapter, and a recognizable equipped item. That baseline makes lost progress visible without comparing entire inventories from memory.
All players should use Legacy Edition AppID 2523770 on the same public branch. Do not mix original AppID 32800 saves or assume cross-product conversion. A player who advances the same character in a separate solo timeline may create quest-state differences; the community workaround recommends keeping the guest’s co-op character aligned with the host campaign.
Test one short Bree-to-checkpoint loop before committing to several chapters. Rejoin once and confirm the guest’s level and equipment remain.
Trigger separate autosaves in a town
At the end of play, travel normally to a safe hub. Let story dialogue and the arrival checkpoint finish. The host opens a merchant, buys or sells an inexpensive disposable item, exits the vendor, and watches for the golden spinning save indicator to appear and disappear.
Then the client performs a separate small transaction and watches their own screen. Do not rely on the host saying that a save icon appeared; the purpose of the sequence is to trigger and observe each side independently.
Avoid moving high-value set pieces during this test. A cheap ordinary item creates a clear transaction without risking the campaign loadout.
Leave in client-first order
After both indicators finish, the client uses the pause menu to quit to the main menu. The host waits until the disconnection completes and the client confirms they reached the menu. The host then ends the session through normal game menus.
Do not use Alt+F4, kill the process, power down the PC, or interrupt Steam Cloud synchronization. An abrupt exit makes it impossible to distinguish a co-op autosave issue from an incomplete local write.
The community post also recommends running the executable as administrator. This guide does not make that a default step: elevated privileges expand what the process can change and should be considered only when Aspyr support or a diagnosed filesystem-permission problem specifically requires it.
Verify the client before continuing
At the next session, have the same host open the lobby. After the client joins, compare hero level, equipped item, inventory, and chapter state with the previous note. Run a harmless merchant check before traveling.
If only quest position differs but equipment remains, identify whether the host owns story progression while the guest retains character progression. Do not assume every campaign flag is meant to be independent. Capture exact differences before attempting recovery.
If the client reverts, stop. Preserve current files, exit cleanly, and document the session order, visible save icons, branch, and Steam Cloud messages for support.
Recover without overwriting evidence
Restart Steam and the game, verify Cloud status, and retry the last stable lobby. Avoid repeatedly joining and quitting because each attempt may create another save state. Do not rename, copy, or replace save folders based on an original-release path.
If one player’s achievement credit differs, separate that issue from character saving. Strength of Our Alliance may need host rotation according to the current completion guide even when inventory saves correctly.
Use Online Co-op for lobby preparation and Strength of Our Alliance for the host-sensitive group action.