A good use case for keeping program settings, profiles, configs, etc, in sync across devices is to store those files in the cloud and point the program paths to the cloud folder. It's a simple and robust solution with good compatibility across various programs, since this solution inherently requires no dedicated cloud integration on the part of the maintainers, they only need to provide editable paths for these files - the user assumes control and liability for the behavior. E.g, this is how I keep my emulator ROMs, saves and configs synced across devices, and it works very well
Although reWASD does provide editable path to the "My data" subfolders and will migrate the data to a cloud directory, the program will no longer allow you to create new game profiles. I'm not sure, but it seems there exists some incompatibility with the way reWASD creates it's files/folders in a streamed cloud directory, even when the cloud directory is flagged to always be available offline
So my first ask is that reWASD simplify and streamline its file/folder creation process for improved compatibility with this sort of workflow
My second ask is that reWASD not micromanage the migration of the data itself. In its current implementation, editing the paths to the "My Data" subfolders is highly conditional and too restrictive. It seems that instead of being able to simply point to new folders and assume the responsibility myself, reWASD actually tries to fully migrate the data to the new location. This means that the new location must be completely empty or the migration fails. So you can migrate the data to the cloud once on one computer, but try and point a second reWASD instance on another computer to the new cloud directory, and you have the same issue - the new directory now has data in it, and reWASD refuses to point to the new paths in the cloud. We're all adults here. I'm quite capable of copy/pasting this data myself to a new directory and updating the paths in the software. There's really no need for reWASD to assume responsibility for migrating this data
So all that really only leaves 2 solutions for keeping things in sync. You can either create an annoying network share that fails the moment you leave the local network, or you can just manually export/import your files...in 2026
Although reWASD does provide editable path to the "My data" subfolders and will migrate the data to a cloud directory, the program will no longer allow you to create new game profiles. I'm not sure, but it seems there exists some incompatibility with the way reWASD creates it's files/folders in a streamed cloud directory, even when the cloud directory is flagged to always be available offline
So my first ask is that reWASD simplify and streamline its file/folder creation process for improved compatibility with this sort of workflow
My second ask is that reWASD not micromanage the migration of the data itself. In its current implementation, editing the paths to the "My Data" subfolders is highly conditional and too restrictive. It seems that instead of being able to simply point to new folders and assume the responsibility myself, reWASD actually tries to fully migrate the data to the new location. This means that the new location must be completely empty or the migration fails. So you can migrate the data to the cloud once on one computer, but try and point a second reWASD instance on another computer to the new cloud directory, and you have the same issue - the new directory now has data in it, and reWASD refuses to point to the new paths in the cloud. We're all adults here. I'm quite capable of copy/pasting this data myself to a new directory and updating the paths in the software. There's really no need for reWASD to assume responsibility for migrating this data
So all that really only leaves 2 solutions for keeping things in sync. You can either create an annoying network share that fails the moment you leave the local network, or you can just manually export/import your files...in 2026