Check Steam update against deployment #35
Labels
No labels
ci
crate/dtmm
crate/dtmt
crate/sdk
crate/serde_sjson
kind
bug
kind
documentation
kind
enhancement
kind
feature
kind
question
kind
upstream
part/bundle
part/filetype
stage
actionable
stage
design
stage
proposal
status/duplicate
status/good first issue
status/help wanted
status/invalid
status
need-replicate
status/wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#21 Detect Steam and game directory
bitsquid_dt/dtmt
Reference: bitsquid_dt/dtmt#35
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Look through Steam's metadata files. There's probably something that records the last update time. Or something that can be mapped against steamdb.info to get the update time.
Then, during deployment, write a file containing the deployment time (and maybe some other info, such as included mods and packages).
On the next deployment (and maybe also when DTMM is started), read that file and check whether there was an update since. If that was the case, notify the user that they will have to reset things first.
Things to look into:
The file is actually an
.acf
. Specifically,<steamapps>/appmanifest_1361210.acf
:The file looks relatively simple to parse, as it's just quoted strings and maps.
.acf
seems to be the same format as.vdf
: https://developer.valvesoftware.com/wiki/KeyValuesParsers exist already: https://docs.rs/keyvalues-parser/latest/keyvalues_parser/
Closed in #50.