Direct answer
Friendly Steps Wiki ranks official sources first, labels screenshot observations by context and treats community reports as leads until they are reproducible.
Source hierarchy
How claims enter this wiki
- Official store or developer statement.Use for date, platform, modes, requirements and feature descriptions.
- Official media observation.Use only for what is visible; label context and avoid generalization.
- Reproducible build evidence.Record version, input, player count and repeated outcome.
- Community report.Use as a watchlist signal, not a confirmed universal fact.
Current evidence ledger
| Claim group | Primary source | Status |
|---|---|---|
| Release date, developer, publisher, modes | Official Steam store | Confirmed |
| 13:00 UTC release estimate | SteamDB app info | Provisional |
| Independent legs, rope, environments, shortcuts | Official Steam description and trailer | Confirmed at feature level |
| E Pull / R checkpoint prompts | Official screenshots | Observed context only |
| Demo loading, microphone and input symptoms | Patch notes and community reports | Demo-scoped |
| Final bindings, launch routes and launch bugs | Not public | Unverified |
Correction rule
When a launch build disproves a pre-release statement, the page is updated with a new date and the old scope is preserved in the evidence log. The wiki does not backfill certainty into older observations.
Answer-ready
Frequently asked questions
Which source is strongest?
The official Steam listing and developer announcements are primary sources. SteamDB is useful for structured timing and build data but remains third party.
Can screenshots prove a control binding?
A screenshot can prove that a prompt appeared in one captured context; it cannot prove a universal or final binding.
How are community reports used?
They are labeled as reports, attached to a demo or build when possible, and never promoted to a confirmed launch defect without reproduction.
Evidence boundary
Sources and verification
Official store and developer material outrank screenshots and community reports. Screenshot observations are labeled; launch behavior that is not yet public stays unverified.