Inspecting Game Saves network traffic
Use Fiddler to inspect and debug network traffic coming to and from your title. For information about Fiddler setup, see the following articles: Fiddler confirms whether the title acquires or releases the title lock, which determines when data syncs to and from the cloud. Here’s thePUT request when a title successfully obtains a lock.
For more information about the sync process, see Understanding the Game Saves sync flow
Manipulating Game Saves
Two tools are available for directly interacting with Game Saves.xbstorage: Used for local Game Saves on console. For more information, see Manage Game Saves data on console (xbstorage.exe).xgamesaveutil: Used for local Game Saves on PC. For more information, see Manage Game Saves data on PC (xgamesaveutil.exe).
The import and export behavior differs between console and PC. See the details below and the respective tool pages for more information.
Console (xbstorage)
On console,xbstorage operates through the console’s Game Saves service. When the tool performs an operation, the system behaves as if the title performs the operation directly.
- Importing data causes the console to sync with the cloud first (acquiring a lock and downloading any remote changes), write the imported data locally, and then begin uploading the imported data to the cloud. The upload completes in the background before the lock is released.
- Exporting data causes the console to sync with the cloud first, then copy the local data to the output file.
PC (xgamesaveutil)
On PC,xgamesaveutil writes data directly to local disk without going through the Game Saves service.
- Importing data writes the containers and blobs to the local disk. The tool doesn’t sync with the cloud before or after the import, and it doesn’t trigger an upload to the cloud. The imported data is uploaded to the cloud the next time the title launches and acquires the Game Saves provider.
- Exporting data reads containers directly from local disk. It doesn’t sync with the cloud before reading.