Not right now. That's part of why there's no release. It's still incomplete. Before stuff started getting crazy for me last year, I was actually cleaning up a lot of the code and finishing off the Google drive stuff. Right now it might just be small updates to the master branch until I have enough time to really sit down and get some stuff done. I might spend some time on the weekends on it, but it's only gonna be a few hours here and there.
Ok, thanks! I'm glad I didn't miss something obvious. What it has right now works for me.
I'm trying to figure out a development strategy for the scenario I'm facing. Being able to push to Google Drive helps with that, but there are some other parts that I need to consider.
(The following is just me thinking out loud. I'm not asking you for anything!
)
Essentially, I'm looking at what I would need to do to share Octopath Traveler 2 saves between my PC, my Steam Deck, my local NAS, and my Switch. I have the PC-Deck/PC-NAS/Deck-NAS stuff worked out using SyncThing, which just leaves figuring out what to do with the Switch.
There are two problems I face. One is that the Switch saves need renamed; I need to figure out a way to auto-rename the saves as they get pushed to / pulled from the Switch. The second is how to automate the system such that I can push saves from my Switch to some storage and have it be parsed without waiting for a script on a timer.
In the ideal scenario, I would have a fork of JKSV that, when saves are made, would push data to an FTP server on my NAS and then rename the files based on some rules I defined in a .JSON file for that particular title. My NAS would use SyncThing watch the FTP folder and then distribute the saves to my PC and Steam Deck when they are turned on. Likewise, I'd have a reverse operation that would pull data down from an FTP server and do the reverse renaming.
(The reason for FTP: It gets around the 7 day reauth of Google, and I don't expect to upload my saves from a place other than my house.)