Prices and observation windows
Prices are collected for the Steam US store and expressed in USD. Each history entry retains its UTC date. A record is a collection-time quote, not a promise that an offer remains available. Region, tax treatment, edition and bundle composition must be checked on the current store listing.
The observed minimum is the lowest valid price in our recorded window. It is not certified as an all-time or cross-store minimum. Missing dates are not backfilled, and unknown prices are not turned into zero. At least three valid dates are required before the interface labels a paid current quote as matching a recorded low.
Requirements and player counts
PC requirements retain the publisher values. The comparison normalizes fields such as OS and OS* so a label difference does not create a missing-value error. It does not infer FPS or hardware equivalence. A recommended requirement absent from the source remains absent.
Concurrent-player values are momentary observations, not unique players or daily peaks. A later history point cannot be displayed under an older snapshot date. An unavailable source response remains unknown; it is not a zero-player claim.
Publishing and freshness
A versioned backend dataset is activated only after import checks. Pages read that published version on the server, and the snapshot date is shown in the interface. A new interface deployment does not itself make the data fresher. Source collection and article review dates are separate.
The original files are retained in the collection workspace. The importer reads the validated catalogue and corresponding specification version, filters history to the published snapshot date and checks current-price consistency. A source failure keeps the prior valid version rather than fabricating a successful update.
Catalogue scope and corrections
The catalogue is selected from public store records and excludes source records flagged by the existing content-safety gate. It is not the complete Steam library and is not an age-rating service. Metadata may be incomplete or change after collection.
If a title, platform flag, price or parsed requirement appears wrong, include the page URL and source evidence in a correction. Feedback is reviewed separately from data collection. A collected message is not automatically considered resolved.