Build and Kill Zombies changes what an input does according to your state: walking around the plot, using a roll station, placing a part, or driving. Current PC walkthroughs agree on the core build and drive prompts below. They are community corroborated, not an official permanent key map, so the label shown by the live game takes priority.
PC quick reference
Do not memorize Q, B, or F without the state. A reused key can browse a category at a station, delete during building, leave a menu, launch the car, or return from a run depending on the active interface.
Builder control sequence
Enter build mode and choose one owned part. Move the preview over a valid attachment point, rotate until the intended face aligns, then place. If the preview remains invalid, cancel instead of clicking repeatedly. Choose the correct inventory tab and try a connected face.
Before using a delete action, confirm which part is targeted and whether the game describes any refund or inventory behavior. That behavior was not independently verified, so do not assume removal returns the original cost. Save or photograph a working layout before a large edit.
The How to Build a Car guide turns these inputs into an assembly order. The Troubleshooting guide separates a bad key state from a missing part or physics problem.
Driving controls and camera
Use the visible Drive control only after leaving part placement and clearing launch warnings. On PC, current recordings use standard movement keys for steering and acceleration. Test at low speed before reaching the first dense zombie group so you know whether the car pulls, reverses correctly, or needs a camera adjustment.
The exact camera controls follow Roblox and device settings unless the experience overrides them. Use a view that keeps the leading edge, nearby zombies, and steering direction visible. If the pointer remains captured by a menu, close the menu before diagnosing steering.
The return action is reported on the same key used to start the drive in current PC footage. Read the current label before pressing it; returning can end a measurement run. If fuel reaches zero first, record the game’s end state rather than assuming the key failed.
Touch controls
Touch mappings were not verified device by device. Expect on-screen movement and action buttons, but do not assume their position or label matches a desktop video. Rotate the device only if Roblox supports the change cleanly, and ensure no browser overlay covers the action area.
Match actions by meaning: open builder, select inventory, rotate, cancel, place, launch, steer, and return. If a desktop guide says R, look for the live rotate icon or label rather than an on-screen letter. Capture the layout and device model when reporting a missing control.
Large builds can make touch selection difficult. Zoom or change the camera angle so the intended attachment face is visible, then select slowly. If two parts overlap, cancel the preview and approach from another angle instead of tapping repeatedly.
Console controls
Console-specific button assignments were not verified in the available sources. Roblox may show controller glyphs, a selection cursor, or context actions that differ from PC. Use the Settings and in-experience prompts to identify each action before editing a valuable build.
If a glyph is missing, reconnect the controller, close chat, and reopen the relevant menu. Record the console family and controller because the same action can display a different symbol. Do not publish a PC key as a console button without a live check.
When a control appears broken
First determine the state. Are you walking, interacting with a station, holding a part preview, editing an installed part, or driving? Close chat and any modal menu. Cancel the selected part. Move away from the station, then return and read the prompt again.
If movement works but building does not, verify that the selected item is owned and the preview is on a valid mount. If building works but Drive does not, inspect the car for missing required roles and any launch message. If no input works, use Roblox’s normal menu to check focus, controller connection, or remapping before rejoining.
Make a device-specific note
Write one row for each action you actually tested: device, game state, displayed label, input, result, and date. Keep changed bindings separate from defaults. This is especially helpful after an update because you can distinguish a new mapping from a forgotten custom setting.
Avoid recording Cash rates, part rules, or event mechanics in a control note. Controls answer how to perform an action; the Parts, Skills, and Events sections answer what the action affects.
Source note
PC inputs are community corroborated from multiple September 2026 guides and video walkthroughs for Place 105011592530400. Touch and console mappings remain needs in-game testing.