How we verify

How source data, derived paths, manual tests and downloadable packages are kept apart.

Availability is never inferred

A published game, a mapped Save path and a downloadable Save are three separate facts. A download is never created from Steam metadata alone.

Confidence labels

Confirmed
An editor tested the path on the stated OS, store and game build.
Derived
The path was built from Steam Auto-Cloud configuration or another primary technical source, but has not been tested on a real machine yet.
Unverified
A credible report exists but the evidence is incomplete. Normally kept off public pages.
Broken
The source configuration is contradictory or the path failed testing.

What “100%” means

A package page lists its scope: campaign, collectibles, achievements represented in the Save, unlocks, endings or routes, difficulty, NG+, DLC and anything intentionally left out. An achievement count alone is not proof.

Source changes

Imported changes go into review as a diff. Published data is never silently replaced by a fresh parser result, and every record keeps its source and check date.

Corrections

Material errors are corrected visibly. A package that becomes unsafe, misleading or incompatible is withdrawn instead of being left up behind a warning.