Bridge Constructor Portal (cloud profile doesn’t match actual storage location).The following titles have broken cloud sync implementations and can’t be fixed without creative game-specific patching that has nothing to do with Flatpak: † Works with at least RimWorld, City Skylines, Borderlands 2, Project Highrise, Sim Airport (game doesn’t work, but sync does), Transport Fever (game doesn’t work, but sync does), Mini Metro, Dream Daddy, and Space Run (game doesn’t work, but sync does). Some are inside the Flatpak app directory, some are in the home directory, some are partially in one place and partially in the other. We also don’t know what the actual paths that need to be migrated are. These are recoverable but we can’t migrate the data for the user without causing Steam Cloud conflicts. Local saves inside and outside the Flatpak container is lost.It can’t be migrated as moving it breaks some games that use absolute install paths and causes crashes with the Steam overlay. The old Steam library and install is no good.All games† now sync to and from Steam Cloud, meaning players get back years worth of game progression.
Unit圓D) but Steam itself doesn’t actually read the $XDG_DATA_HOME variable but just hardcodes $HOME/.local/share/ or $HOME/.config/. It appears that game developers use $XDG_DATA_HOME (default in e.g.
This is the LinuxXdgDataHome data root path in Steam Cloud, which documentation suggests is corresponding to $XDG_DATA_HOME.
The below ended up serving as drafts for that analysis and is less less accurate.įor most games, Steam Cloud syncs saves and configurations to and from /home/user/.local/share/studio/gamename. Update: Read this analysis of this bug which includes two suggestions for possible fixes. TL DR: Paths are broken because of XDG overwrites.