Orc Incremental Steam Cloud
An official-source Steam Cloud reference with safe conflict evidence, local-backup precautions, and explicit unknowns for timing, quota, and reconciliation.
- Published
- Updated
- Last checked

Quick facts
- Demo save backup
- Steam Cloud
- Demo uninstall
- Save survives
- Local safety copy
- Required before manual file operations
- Conflict rules
- Not published
Keep a local copy as well
The announcement supplies the Cloud statement but not sync internals. Generic key art does not prove a successful upload, current remote timestamp, quota, or conflict resolution.
Before any manual file operation, close the game and preserve the entire local folder in a separately named location. A Cloud backup is valuable, but it should not be the only copy used during an unresolved conflict.
Use save location for the official Windows path and Demo save transfer for the supported compatibility boundary.
Record a conflict prompt before choosing
When Steam presents two versions, capture the exact prompt and the timestamps, devices, and recent play sessions you can verify. Do not assume “Cloud” or “local” is automatically newer or more complete.
| Field | Evidence |
|---|---|
| Build | Exact game version or date |
| Device | Neutral device label |
| Last known session | Verified time and progress |
| Local timestamp | As displayed by Windows |
| Remote timestamp | As displayed by Steam |
| Prompt wording | Complete text and options |
| Local copy | Date created before a choice |
Pause if the evidence conflicts. Current Steam support guidance, not a generic game guide, should control the platform-specific resolution step.
Distinguish sync absence from data loss
A missing Cloud indicator, offline session, or stale screen does not by itself prove that a remote save was deleted. Record connection state, Steam status, prompt history, and local folder timestamps.
Avoid cycling online/offline or launching on several devices while the state is unclear. Each new session can add another version to reconcile.
Verify after a normal session
Close the game normally and allow Steam to finish any visible sync activity. Record the time and the next launch result on the same device. This can establish an observed workflow without revealing unpublished timing guarantees.
Do not claim that a screenshot of gameplay or key art proves Cloud status. Only the platform interface and official statement address it.
Keep limits explicit
The checked game source does not document quotas, conflict algorithms, offline merge behavior, or exact upload timing. Those fields stay unknown here. If the platform publishes current instructions, link them as platform guidance and keep game-specific claims separate.
The safe approach is simple: retain a local copy, preserve prompts, and avoid irreversible choices until timestamps and sessions are understood.
Plan a device handoff conservatively
Finish and close the game on the first device, allow visible Steam activity to settle, and record the session time. On the second device, inspect any prompt before opening the game. This is an observation workflow, not a timing guarantee.
If the second device shows unexpected progress, close it without starting another play session and preserve the local state on both devices. More launches can make the chronology harder to reconstruct. Compare verified play times and platform prompts, then use current Steam guidance for the next decision.
Official sourceVerification boundary
- Build boundary
- official Demo-retirement announcement
- Evidence check
- Still unknown
- conflict-resolution rules, sync timing, quota, offline reconciliation
Frequently asked questions
- What is verified about Steam Cloud?
- The official Demo-retirement announcement says Demo saves are backed up by Steam Cloud and survive Demo uninstall. Boundary: official Demo-retirement announcement. Checked 2026-08-28. Copy %APPDATA%/OrcIncremental before manual file operations and do not edit save contents; the checked source does not publish conflict-resolution, quota, or sync-timing rules.
- What should I record when Steam reports a sync conflict?
- Do not guess which copy is newer. Record each timestamp and prompt, close the game, preserve the local folder separately, and consult current Steam guidance before choosing a version.
Source ledger
- End of Demo is tomorrow (Jul 11th)
steam-announcement ·