What is the idea?
I have been working on an integration between LuaTools and CloudRedirect to help users protect save files for games that do not have usable Steam Cloud support.
The idea is to let LuaTools identify a supported game, resolve its save locations, and call the CloudRedirect CLI to upload or restore the original save files using the cloud provider already configured by the user.
The LuaTools side is data-driven, so support for additional games and save layouts can be added without implementing a separate service for each title.
Current status
I already have a working prototype in my LuaTools fork.
The first supported game is Assassin's Creed Black Flag Resynced (Steam AppID 3751950). It supports both the Voices38 and HV save layouts, allowing their saves to coexist independently in cloud storage.
CloudRedirect dependency
The current prototype depends on CLI functionality that I added to my CloudRedirect fork. These commands upload and download a supplied directory tree while keeping CloudRedirect itself game-agnostic.
I discussed the idea with the CloudRedirect author. They are also exploring official support for games without Steam Cloud, including scenarios involving HV releases. Their preferred implementation may use Steam AutoCloud where possible.
Because the official design and interface are still being developed, I do not think LuaTools should depend on my modified CloudRedirect fork in its main branch.
Why open this issue now?
I would like to discuss whether this feature would make sense for LuaTools before proposing an upstream implementation.
For now, I can maintain it as a temporary build of my LuaTools fork using my CloudRedirect fork. Once CloudRedirect provides official support for the required scenarios, the integration could be adapted to use the official implementation and the temporary fork dependency could be removed.
Would the LuaTools maintainers be interested in this integration? If so, how could we make a regular latest version and a temporary cloud-redirect-fix version coexist until the required functionality is officially available in CloudRedirect?
Some Images
What is the idea?
I have been working on an integration between LuaTools and CloudRedirect to help users protect save files for games that do not have usable Steam Cloud support.
The idea is to let LuaTools identify a supported game, resolve its save locations, and call the CloudRedirect CLI to upload or restore the original save files using the cloud provider already configured by the user.
The LuaTools side is data-driven, so support for additional games and save layouts can be added without implementing a separate service for each title.
Current status
I already have a working prototype in my LuaTools fork.
The first supported game is Assassin's Creed Black Flag Resynced (Steam AppID 3751950). It supports both the Voices38 and HV save layouts, allowing their saves to coexist independently in cloud storage.
CloudRedirect dependency
The current prototype depends on CLI functionality that I added to my CloudRedirect fork. These commands upload and download a supplied directory tree while keeping CloudRedirect itself game-agnostic.
I discussed the idea with the CloudRedirect author. They are also exploring official support for games without Steam Cloud, including scenarios involving HV releases. Their preferred implementation may use Steam AutoCloud where possible.
Because the official design and interface are still being developed, I do not think LuaTools should depend on my modified CloudRedirect fork in its main branch.
Why open this issue now?
I would like to discuss whether this feature would make sense for LuaTools before proposing an upstream implementation.
For now, I can maintain it as a temporary build of my LuaTools fork using my CloudRedirect fork. Once CloudRedirect provides official support for the required scenarios, the integration could be adapted to use the official implementation and the temporary fork dependency could be removed.
Would the LuaTools maintainers be interested in this integration? If so, how could we make a regular latest version and a temporary cloud-redirect-fix version coexist until the required functionality is officially available in CloudRedirect?
Some Images