[UX] Show tab and message when Cloud Saves are not supported #4280
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, we do not display the
Cloud Saves Sync
tab in the game's settings if the game shows that it doesn't support cloud saves in the metadata and if the game is linux native.It had happened many times in the past that users can't find the
Cloud Saves Sync
tab and they think there's some bug when, in reality, they may be hitting one of those conditions.So, instead of hiding the tab and letting the user figure out why they can't see it, it's more user-friendly to show the tab and explain why it doesn't work. And in the case of a GOG linux-native game we can also instruct the user to use the Windows version instead so they don't need to figure that out.
I did leave the tab ignored for Amazon games and Sideloaded apps/games because I understand Amazon doesn't cloud saves at all and for sideloaded games it makes no sense.
This is similar to what we do with the Gamescope tab, that we show it with an error message if the
gamescope
binary cannot be found.The style is not great but I used the same as the Gamescope tab for consistency (just a div with red text (this is not great for themes though))
Use the following Checklist if you have changed something on the Backend or Frontend: