Steam preservation proposal: Difference between revisions

From No-Intro ~ Wiki
Jump to navigation Jump to search
(Created page with "<pre> folder structure (top level folder = dat entry): ``` app1 depot1 CSM/CSD with all depot chunks all depot manifests depot key depot2 ... possibly sidecar file with update history (for correct manifest combos). current manifest combos can be retreived via steam. could include historical data from steamdb, marked as such. ``` chunks and manifests are to be the raw files from the server when a new manifest is pushed, the CSM/CSD file would be up...")
 
No edit summary
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
<pre>
<pre>
folder structure (top level folder = dat entry):
This is a work in progress proposal for improving the Steam datting procedures
 
folder structure below. top level folder (app1) = dat entry
```
```
app1
app1
Line 18: Line 20:
unsolved issues:
unsolved issues:
* tooling to automate all this
* tooling to automate all this
* recording package info, so that "trap DLC" DRM can be avoided
 
supplemental projects:
* The data from the older steam server/API versions: Steam1 and Steam2 data (current Steam is Steam3)
* recording app and package info, so that "trap DLC" DRM can be avoided and the real steam install process can be recreated (rather than user manually choosing depots)
* recording achievement info, so that can be used offline with steam emulators
* recording achievement info, so that can be used offline with steam emulators
* SmartSteamEmu is closed source and windows only (its apparently the best steam emulator - hooks API calls instead of replacing DLLs, has achievement display)
* SmartSteamEmu is closed source and windows only (its apparently the best steam emulator - hooks API calls instead of replacing DLLs, has achievement display)
* recording the rest of the metadata on steam
</pre>
</pre>

Latest revision as of 09:33, 15 June 2024

This is a work in progress proposal for improving the Steam datting procedures

folder structure below. top level folder (app1) = dat entry
```
app1
  depot1
    CSM/CSD with all depot chunks
    all depot manifests
    depot key
  depot2
    ...
  possibly sidecar file with update history (for correct manifest combos). current manifest combos can be retreived via steam. could include historical data from steamdb, marked as such.
```

chunks and manifests are to be the raw files from the server

when a new manifest is pushed, the CSM/CSD file would be updated (added as new file, with old file excluded from DoM?) and new manifest file added

unsolved issues:
* tooling to automate all this

supplemental projects:
* The data from the older steam server/API versions: Steam1 and Steam2 data (current Steam is Steam3)
* recording app and package info, so that "trap DLC" DRM can be avoided and the real steam install process can be recreated (rather than user manually choosing depots)
* recording achievement info, so that can be used offline with steam emulators
* SmartSteamEmu is closed source and windows only (its apparently the best steam emulator - hooks API calls instead of replacing DLLs, has achievement display)
* recording the rest of the metadata on steam