Hacker News new | ask | show | jobs
by Veraticus 87 days ago
Oh this is really interesting! I hadn't explored Steam Cloud as a data source. Currently the daemon watches local save directories and parses through WASM, but if Steamworks exposes an API to pull save files remotely, that could work as a server-side adapter (same pattern I use for WoW via Battle.net API). That would eliminate the daemon entirely for Steam games, which is by far the biggest friction point in the install flow right now.

I'd love to see your JS lib if you're willing to share it! The raw files would still need per-game parsers (D2R's .d2s is a gnarly bit-packed binary, for example), but moving file access to the server side would be a big deal for adoption.
1 comments
arty_prof 87 days ago
Here it is: https://github.com/ArtyProf/steamworks-ffi-node

Actually I develop it mostly for steam integration in games under js.

I think the tricky thing left is in what format devs saving files to parse them correctly.

But generally it can parse most indie games, which are using steam remote storage api and store them as json.

The main requirement that steam must be launch for the user that MCP is parsing

Here is the doc for steam remote storage API: https://github.com/ArtyProf/steamworks-ffi-node/blob/main/do...

link