#[SPZ2-5043] Steam cloud errors for blueprints that contain illegal filename chars on windows

1 messages · Page 1 of 1 (latest)

young bolt
#

Hi.

Forbidden filename chars on windows are: * " / \ < > : | ?. Shapez is not properly filtering these on other platforms, so they are saved, uploaded via cloud sync, then emit an error when pulled back down on a windows machine.

For example, you can see in the steam cloud_log.txt on windows:

[2025-10-10 00:59:29] [AppID 2162800] HTTP download for file 'tobspr Games/shapez 2/blueprints/Etc/??.spz2bp' from host 'steamcloudquincy.blob.core.windows.net' - Success.
[2025-10-10 00:59:29] [AppID 2162800] Downloaded file could not be written - error 2, internal path 'tobspr Games/shapez 2/blueprints/Etc/??.spz2bp', file path 'C:\Users\****\AppData\LocalLow\tobspr Games\shapez 2\blueprints\Etc\??.spz2bp'
[2025-10-10 00:59:29] [AppID 2162800] Download I/O Operation Failed for file tobspr Games/shapez 2/blueprints/Etc/??.spz2bp
[2025-10-10 00:59:29] [AppID 2162800] Download complete, result I/O Operation Failed
young bolt
#

This is particularly nasty because it's nontrivial to remove that "corrupt" file from the steam remote cloud. Basically the sitation is:

  • Played some on machine A (mac)
  • Close game, all files + bad blueprint uploaded
  • Played some on machine B (windows). Get a cloud sync error upon launching, don't think much of it since my savefile from A is there and looks okay, as well as my other blueprints. Likely the initial sync is mostly successful because it does in fact download all the files it can.
  • Close game, nothing uploads because cloud sync is still stuck on initial download error. Whole sync system is now in a deadlock.
  • I'm unable to directly delete this file from steam remote storage. It must be overwritten or explicitly deleted by the game binary itself.

So in order to not lose the progress I made on B and also remove this corrupt file in the cloud it seems like i'll have to do some cursed combination of deleting caches and manually moving save files over to my mac, then renaming the ?? file on my mac to something different.

#

i'll have to do some cursed combination of...

confirmed this solved the sync deadlock for now

smoky knot
#

I tested it in Linux and had the same problem.