What the progress tracker stores

The progress tracker stores a schema version, update time, and a sorted list of completed entity IDs. It does not copy source text, Steam account data, mission choices, player name, or a device identifier. The IDs map to qualified pages already present in the static catalog.

Every checkbox updates the progress record in local browser storage. Reloading the page restores that progress on the same browser profile. Another browser, private window, cleared site storage, or different device will not see it unless you manage a file yourself.

Mission progress

The mission group contains the fifteen qualified campaign missions in the official sequence catalog. Marking a mission records only that you consider it complete. The progress tracker does not inspect a save file, verify an outcome, or infer medal rank. Use the mission evidence link to review the sourced title, order, and related achievements.

Some missions can have multiple outcomes or achievement paths. One mission progress checkbox does not mark every linked achievement. Track those items separately so your progress record reflects the result you actually reached.

Achievement progress

The achievement group contains the thirty-three names and requirements returned by the official Steam achievement interface for the current catalog check. Each progress row includes a concise sourced requirement and opens its qualified detail page. The tracker does not request your Steam profile or compare global completion percentages.

Mark achievement progress only after the platform reports it unlocked. A mission outcome may lead toward an achievement without satisfying it. Keeping the two groups separate prevents one broad mission checkbox from creating false achievement progress.

Medal and unlock progress

The medal, punchcard, and requisition groups track the scope records currently supported by public evidence. Their checkboxes are personal reminders, not proof that every underlying medal, card, cost, or unlock is known. The public dataset deliberately withholds incomplete tables.

Use these progress items to remember that you reviewed or completed the visible scope. Open the evidence page before interpreting what completion means. When a richer qualified catalog arrives, the site can add stable items without uploading your prior progress.

Export progress

Export downloads the exact version 1 progress state as JSON. The file contains only the schema version, update timestamp, and completed entity IDs. The export is created in the browser. No file name or content is sent to the site, Neon, or analytics.

Keep the file if you want an audit or manual backup. This release does not provide import because automatic import would need a separate validated conflict and recovery workflow. Export still gives you a readable record before clearing storage or moving devices.

Reset progress safely

Reset checks whether material progress exists. If the record is already empty, the tracker reports that state without opening a confirmation. If one or more items are complete, the browser asks before erasing them. Cancelling leaves every checkbox unchanged.

After confirmation, the tracker writes a new empty version 1 state with a fresh update time. The reset affects only this progress key. It does not clear firing planner records, analytics preference, browser history, or unrelated site storage.

Version migration and recovery

The progress parser recognizes the current versioned object and an older plain array of entity IDs. A valid legacy array migrates to version 1. Duplicate IDs are removed, order is normalized, and unknown IDs are discarded with a visible recovery message.

Corrupt JSON or an unsupported schema becomes a new empty record rather than a partial guess. This fail-fast behavior keeps progress state predictable. It cannot reconstruct records that the browser has already deleted.

Progress privacy

The progress tracker does not require an account. Checkbox state, counts, update time, and export contents are never analytics parameters. The page makes no request to save progress remotely. Neon stores public content operations, not visitor progress.

Local storage is convenient, not secret encrypted storage. Anyone using the same browser profile may inspect or change it. Do not store sensitive notes here; the tracker stores IDs only. Review the privacy page for the full site boundary.

When the catalog updates

A daily content run may add a mission, achievement, medal, or unlock record after evidence and release gates pass. New progress rows start unchecked. Existing stable entity IDs stay completed. If an entity is retired or merged, recovery removes an unknown old ID and reports the change.

The site never changes your progress based on social engagement or competitor content. Candidate facts can enter Community Radar, but only qualified indexable entities enter this tracker. Open the database and source ledger to audit the catalog.

Use progress as a checklist, not proof

Mission progress records your own completion decision. Achievement progress records your own platform check. Medal progress records the qualified scope you chose to track. Punchcard progress and requisition progress remain reminders because the public catalog does not contain every underlying unlock.

The tracker never upgrades personal progress into public factual evidence. Your progress does not alter achievement requirements, mission order, source confidence, or global completion rates. Local progress also does not prove that a saved game remains intact. It is a lightweight progress checklist that you control.

Review progress after a major patch, especially when official notes mention progression. Open each affected evidence page, compare the current requirement, and update progress deliberately. Export progress before clearing browser storage. Reset progress only when you intend to erase every completed item. Mission progress, achievement progress, medal progress, punchcard progress, and requisition progress remain separate. This separation keeps private progress useful without turning it into an account, telemetry stream, or unsupported public claim.