Watch
Watchers mark changed save files while the game or its launcher is running.
How it works
Local first is a sequence, not a slogan.
Rove watches for stable changes, commits locally, and only then considers cloud replication. That order is the product.
Your PCsave files + local revisions
1
Rovecommit first, replicate later
2
Your destinationDrive or synced folder
Settle
Stable changed files are captured incrementally. Rove avoids treating an actively-written file as finished.
Commit
A local immutable revision is committed first. This is the durable checkpoint on your PC.
Replicate
Cloud replication happens later. It can wait offline, pause on request, or stay local-only.
Review
If both sides changed, both versions are preserved for review rather than silently overwritten.
Restore
Restore verifies required data, shows what will change, and creates a pre-restore Recovery Point before writing save files.
The boundary
No VPS in the middle.
Rove does not send saves through a Rove-hosted server. The desktop app talks to the destination you select: your local disk, Google Drive, or a synced folder on your machine.
That means provider availability, account permissions, quota, and network conditions remain real-world constraints — and the app shows those states instead of hiding them.