03
Screenshots
Save data sync for 3DS, Switch and nds-bootstrap
DaeMoon backs up and syncs saves for the 3DS, the Switch and nds-bootstrap. Every version is kept, and nothing is ever merged behind your back.
In step. Nothing to do.
The console is ahead, so it uploads.
Both moved on. You choose, and both survive.
No clock appears anywhere on this card. Freshness is the version the server issued, because a console clock is user settable.
Never sync while a game is running.
02
Nothing is replaced. An upload adds a version and the ones before it stay downloadable, so choosing wrong is something you can undo tomorrow.
When two consoles disagree, you pick a side and both sides survive. A restore writes a backup to the card first, every time, with no way to switch that off.
A console reaches your server over Wi-Fi, wherever either of them happens to be. Leave a save on one console and the next one to sync picks it up.
03
04
The save is read into a zip with a manifest beside it, and the payload is hashed on the way in.
The version the console started from against the server's latest. Matching numbers accept, differing ones are a conflict.
A package reaches the SD card before one byte is written to a save archive. There is no switch that turns this off.
The archive is committed and the digest checked. Skip that and the console keeps nothing, and the game is what finds out.
05
Scan this with the console
In FBI: Remote Install, then Scan QR Code. The console downloads the current build and installs it, so nothing has to reach the SD card by hand.
06