Funnel Runners does not publish a complete keyboard list in the official store description, so a safe PC controls guide starts with the action names the game shows in its own settings and prompts. This page gives a layout for recording those inputs and a practice routine for the actions that matter during scavenging, repair, and extraction. It avoids inventing default letters or promising a controller and Steam Deck mapping that the approved evidence does not establish.
Record actions by job
Make five groups in your notes: movement and camera, interaction and pickup, inventory and objectives, communication, and vehicle work. Put the displayed key beside the action name and mark whether the game requires a tap, hold, or context. This turns a settings screen into a useful field reference without freezing a particular layout into the wiki.
The action name is more stable than the key. A player who remaps an input still needs to know whether the game calls it interact, use, inspect, drop, or install. A group member who uses another layout can communicate with the action name while each person presses a different key.
Practice movement around the van
Walk a short line from the van to one nearby landmark and back. Turn the camera at the doorway, keep the return direction in view, and avoid opening a menu until you are in a safe position. This simple rehearsal teaches how quickly a player can scan, turn, and retreat while carrying information rather than loot.
If visibility or debris changes the street, repeat the loop with a new landmark. Procedural environments and destruction mean that a remembered direction is not a guarantee of a clear passage. The practice goal is to maintain orientation when the first route fails.
Test interaction one context at a time
Use one safe object to learn the prompt, then use the van to learn the repair context. After each input, look for a visible result. The object should either become part of the player’s carried state, update a prompt, open an interface, or clearly refuse the action. If no state changes, move closer or re-read the objective before trying another key.
Do not test an unfamiliar binding during a long search. Return to the van, change one setting, and perform a small action that can be reversed or observed. A single changed input is easier to diagnose than a full reset followed by a failed extraction.
Keep objective and inventory views separate
An inventory shows what the player carries; an objective view explains why an item or action may matter. When a player confuses the two, a full inventory can look like progress even though the van still reports the same problem. Open the objective view before leaving and after returning with a candidate part.
In co-op, the vehicle lead should call the objective while the searcher calls the location and status of the find. That division prevents a player from carrying an object that sounded useful but was never confirmed by the shared task.
Use communication inputs with a small vocabulary
Voice or text communication is a control skill because it changes what the rest of the crew does. Use short terms such as “need,” “found,” “returning,” “blocked,” and “departing.” Add a direction or landmark when it matters. A co-op crew can then adapt without assigning permanent classes or assuming every player has the same role.
Avoid announcing guesses as facts. “I think this is the part” should lead to a quick test at the van, while “vehicle accepted it” can justify a new search plan. This distinction is especially useful when a run has randomized problems.
Windows and configuration boundaries
The approved product scope is the Windows PC version sold on Steam. The official page lists Windows requirements and online features, but it does not promise a specific controller layout, Steam Deck profile, or console release. Keep those questions out of a fixed key table unless a first-party update adds the relevant evidence.
Use the game’s settings for the binding displayed in your build. If the setting menu and prompt disagree, capture both pieces of wording, reset only the affected input, and treat the result as a possible bug or update change rather than a user error.
A five-minute control check
- Confirm the movement and camera actions in an empty safe area.
- Trigger one pickup or inspection prompt and observe the state change.
- Open the objective view and identify the van’s current need.
- Return to the vehicle and test the repair context without consuming a guess.
- Tell a partner the action name rather than a keyboard letter.
- Change one binding only, then repeat the same small action.
This routine creates a dependable reference without claiming more than the game shows. It also makes a later update easier to document because you know which prompts and contexts changed.
Evidence boundary
The official store page supports the PC, first-person, scavenging, van, tool, co-op, and weather context. Exact keybinds and controller support are live-build questions. Use the Settings screen as the final source for your configuration.