The extraction phase begins when the vehicle is useful enough to change the crew’s goal from collection to departure. Funnel Runners’ official Steam description connects van repair, scavenged parts, fuel, tools, storms, destruction, and escape. Use the checklist below to keep the final decision readable without relying on a fixed map or a universal timer.
Confirm the vehicle
Read the current vehicle display and call the remaining requirement. If the game marks the van ready, make sure every player understands the departure action. If one requirement remains, decide whether it is mandatory or optional from the live objective rather than an old guide.
End optional looting
Once extraction is the priority, leave unconfirmed objects behind. The storm can remove roads and buildings, so the value of a distant item is smaller than its distance suggests. Carry confirmed progress home and preserve the team for the route out.
Choose the first route
Use the street, landmark, or line the team can presently observe. Name a fallback before moving. If a landmark disappears, call it blocked and regroup instead of sending players down separate guesses.
Keep roles clear
One player owns the vehicle state, one calls the route, and everyone reports separation or debris. These jobs can overlap in a small crew. They are temporary coordination tools, not fixed classes.
Review a failed attempt
After an unsuccessful extraction, identify the last decision that removed a safe margin: late return, optional detour, silent split, or unconfirmed vehicle state. Change one behavior next deployment and keep the new test small.
Last-minute route choices
When the first exit line looks damaged, compare routes by evidence. A visible street that has already carried the crew is easier to trust than a shortcut that exists only in memory. A route with one clear fallback is better than a fast-looking line that ends at an unobserved crossing. The approaching storm makes uncertainty expensive, so use the simplest line the crew can describe.
If the van requires one final interaction, keep the route caller informed while the vehicle lead works. A player outside the van can watch the first turn, but should not wander ahead without announcing where the regroup point is. Good extraction is shared attention, not a silent race.
When a teammate is missing
Call the last confirmed location and the direction the teammate was taking. Wait at a readable landmark only when the route remains safe; otherwise return to the vehicle and make the next search decision from known information. Do not let one missing player pull the entire crew into an unplanned storm route.
Solo players can apply the same rule by leaving a deliberate marker in their own route memory: van, landmark, turn, fallback. The point is to return to information, not to push deeper because the last object was almost reached.
Keep the failure useful
After an unsuccessful extraction, write a three-line review: what the vehicle needed, which departure decision was made, and which route fact changed. This separates a repair problem from a weather problem and a navigation problem. The next run can then test the smallest correction.
A calm departure call
The departure call should contain the vehicle state, the first route landmark, and the fallback. For example, a crew can announce that the vehicle is ready, that the team is leaving through the visible street, and that everyone regroups at the van if the first turn is blocked. The wording will differ by crew, but the information should remain short enough to repeat under noise.
Avoid adding optional objectives to the call. Once the team has committed to extraction, a new object or a rumor about a shortcut should require a fresh decision. It should not quietly replace the route that everyone else is following. A shared plan protects players who cannot see the same screen or weather angle.
If the final route changes twice, stop and return to the last known point before choosing a third line. That pause can feel slow, yet it prevents the common failure in which each player follows a different interpretation and no one knows where the van or the rest of the crew went.
Evidence boundary
The official store page supports the extraction context. Exact triggers, routes, keybinds, and storm damage need the live game.