Funnel Runners is listed on Steam as an Early Access game, so updates are part of the guide’s evidence model rather than a small news decoration. The official store page is the primary source for the product identity, current store description, platform scope, features, system requirements, and the developer’s roadmap statement. It describes a playable base built around one American Suburbs biome, randomized environments and weather, vehicle repair, co-op or solo play, and destruction that changes the map.
This Updates hub keeps three states apart. Confirmed means the official store or an official announcement directly supports the wording. Observed means a player has recorded behavior in a dated build but the developer has not made it a stable product promise. Planned means a roadmap or developer statement describes future work without guaranteeing a release date or final implementation. A page that collapses those states into one list makes an Early Access game harder to understand.
What the official store confirms
The exact Steam product is Funnel Runners, AppID 3712080, by Supernova Studios LLC. The store lists an Early Access release date of July 16, 2026 and Windows requirements. It lists single-player, online co-op, achievements, Steam Cloud, stats, and Family Sharing. Its game description centers on an approaching tornado, scavenged information and vehicle resources, van repair, randomized conditions, environmental destruction, and escape.
Those facts are suitable for evergreen guide context, but “evergreen” does not mean immutable. A store description can change while the game remains the same product. Record the date beside a material claim and link to the exact product page so readers can see the source rather than treating a copied sentence as a patch note.
What a roadmap means
The official Early Access answers describe plans for additional biomes, new weather events, new game modes, gadgets, and quests. A plan is useful for explaining direction; it is not proof that a biome, mode, item, or quest is playable today. Keep future work under a roadmap heading and avoid building route instructions around it.
When a planned feature appears in the game, look for two separate confirmations: the feature is present in the live build, and the player-facing behavior is clear enough to guide. A title or teaser can establish a name without establishing access conditions, rewards, balance, or completion state.
How to read a patch note
A useful patch note record has a date, an official source, the affected system, and a short statement of what players should re-check. Avoid copying a full announcement into the wiki. Explain the decision impact: a van interaction may change repair instructions, a weather adjustment may change retreat advice, and a new biome may invalidate a route example.
If no official patch note is available, label the observation as player-reported and keep it out of fixed tables. A community clip can suggest a question worth testing, but it cannot by itself prove every mechanic, version range, or future behavior.
Update-sensitive guide areas
Controls can change through binding or UI updates. Repairs can change through new parts, prompts, or dependencies. Scavenging can change when item placement and destruction rules change. Weather can change through warnings, intensity, or building behavior. Escape can change when the van or route rules change. Those pages should show a dated checkpoint whenever a new official update affects their decision.
System requirements and platform claims deserve the same discipline. The current official store page is the approved source for Windows requirements in this project. Do not promote a rumor about console support, a stable Steam Deck profile, or a new platform until a first-party source supports it.
What this wiki will not invent
There is no approved code system for this base game, so a copied code list does not belong here. There is no approved universal run timer, fixed item table, exact tornado tier table, permanent map route, or class roster in the evidence used for this build. When players ask for those values, the answer should explain the evidence boundary and point to the live objective or official update source.
Do not convert a third-party guide’s date or version string into an official patch number. Keep product identity tied to AppID 3712080 and treat a branch or build label as a separate field that must be verified.
Update workflow for players
Before a deployment after an update, open the official announcement or store page, read the affected system, and test one small interaction. Return to the van, confirm its current prompt, and note whether the route, weather warning, or control differs. A tiny test is safer than assuming a long guide is unchanged.
After a run, record the build label displayed by the game if it provides one, the date, and the observed change. Describe what happened without claiming why it happened unless an official note explains the cause. This produces a useful issue trail and helps the next guide revision stay narrow.
Update questions
Is Funnel Runners still Early Access?
The official Steam listing used for this audit identifies the product as Early Access. Revisit the store before using that label in a future release cycle.
Where should roadmap claims live?
Keep them in the Early Access Roadmap article and label them as planned. Do not represent a planned biome or mode as playable content.
Are community patch notes official?
Not automatically. Use them as leads, then find a first-party announcement or a dated in-game observation before changing a stable guide.
Evidence boundary
The official Funnel Runners Steam store page is the primary source for product identity, Early Access status, current visible features, system requirements, and the developer’s roadmap answers. Player observations are labeled separately. Recheck the source and the live game after material updates.