The official Funnel Runners Steam page describes an Early Access direction that includes additional biomes, new weather events, possible new modes, gadgets, and quests. Those statements explain the developer’s direction, not a release calendar. Use this page to read the roadmap without turning planned content into a route guide for the current build.
Planned is not playable
A roadmap item can be a design intention, a feature under exploration, or a future expansion of the live game. The store wording does not by itself establish a launch date, access requirement, map layout, reward, or final mechanic. Keep planned features in future tense until an official update says they are live.
What the direction suggests
New biomes would change search landmarks and weather context. New weather events could change retreat decisions. New modes might alter the vehicle objective or the length of a deployment. Gadgets and quests could add new reasons to coordinate. These are reasonable planning implications, not confirmed mechanics.
How to verify a release
Look for an official announcement, a store description change, or the feature appearing in the current game. Then test the player-facing behavior before changing a guide. Record the date, the source, and the narrowest claim the evidence supports.
Avoid roadmap inflation
Do not list a planned biome as an available map, call an explored gadget a permanent system, or publish a reward table before the game displays it. A short, honest roadmap note is more useful than a long speculative checklist.
Questions to ask when a feature appears
First ask whether the feature is present in the actual build or only shown in a trailer, store sentence, or community discussion. Then ask whether its player-facing rules are clear: where it starts, what it changes, what it requires, and what happens when the team completes it. A feature name alone cannot answer those questions.
Record the smallest supported claim. If an official announcement says a weather event was added, write that it was announced or present, not that it always appears, has a fixed intensity, or changes every map. If the store describes a future biome, keep it in the planned section until players can enter it in the current product.
How a roadmap affects guide maintenance
An announced biome may require a new Scavenge article, but it should not invalidate the American Suburbs route until it is playable. A new gadget may add a Controls note, but it should not create a class guide until the game exposes a stable role. A new mode may deserve its own hub only after its objective, entry, and result are documented.
This separation keeps the navigation useful between updates. Players can read what is available now, while returning readers can see what the developer has said is next without confusing expectation with access.
A dated note format
When recording a roadmap change, write the access date in UTC, the exact source URL, the feature wording, and the confidence state. Then add one sentence about the player decision that may need review. A new weather event might affect Weather and Escape; a new gadget might affect Controls and Scavenge. Keeping the impact narrow prevents every headline from triggering a rewrite of unrelated guides.
If an announcement disappears or its wording changes, preserve the earlier observation as historical context only when the date and source are clear. Do not present an old plan as the current product. Early Access readers need to know whether they are reading a promise, a live feature, or a report from an earlier build.
That distinction also helps searchers choose the right next page: playable systems belong in the relevant guide, while future direction belongs here.
Evidence boundary
The official Steam page is the source for the roadmap wording and current Early Access scope. Release timing, final features, and access conditions need an official update and a live build check. Keep planned items out of playable checklists.