The official Web Rush description lists eight PC action mappings: Left Click Attack, X Air Tricks, Shift or Right Click Zip to Point and held Swing, Ctrl Dodge, C Dive, airborne Space Web Zip, and V Camera Lock. Roblox’s normal movement and jump controls still provide the base character movement, but the game-specific list below should be your reference for Web Rush actions.
Official PC control map
Practice controls in a safe order
First test Shift or Right Click in an open area and learn the difference between tapping for point zip and holding for swing. Then release into open air and press Space once for Web Zip. Add C Dive to recover toward a selected street. Add X Air Tricks only after the landing remains visible.
Move to combat after travel is readable. Use Left Click for a short attack, Ctrl for one deliberate dodge, and V to compare locked with free camera. Do not mash every input at once; changing one action at a time shows what the game did.
Point zip versus swing
The two actions share an input family. A short press can trigger a zip toward a point, while holding sustains swinging according to the official description. If the game swings when you intended to point zip, shorten the hold and make the destination clearer. If it zips when you intended to swing, check the hold and whether the current position provides a usable route.
Exact aim assistance, point range, anchor eligibility, and cancel behavior are not documented in the public text. Use the current visual feedback rather than a fixed distance claim.
Web Zip and jump context
Space performs Web Zip while airborne. On the ground, Space normally serves Roblox’s jump context, so test after leaving the surface. If nothing happens, confirm that the character is actually airborne and that another action has not already landed you.
Use Web Zip as one part of a route, not an automatic recovery from every collision. The Web Zip Guide provides a staged practice sequence.
Camera Lock decisions
V can help hold one thug in view during a short exchange. In a group, it can also pull attention away from another threat or from the movement exit. Toggle it according to the encounter rather than leaving it on by habit.
If the camera seems stuck after leaving combat, press V to test the lock state, then rotate toward the next route. Check Roblox settings for camera behavior if the issue affects the whole experience.
Mobile controls
No public first-party mobile mapping was accepted for this guide. Use the current on-screen buttons and match each by action label or observed result. Do not assume the layout mirrors a YouTube capture because screen size and updates can move controls.
If an action appears missing, check whether it is contextual: Web Zip requires air, Air Tricks may require air, and the zip/swing control can change between tap and hold. Record the button label, device, orientation, and version when reporting a problem.
Controller controls
No public first-party controller mapping was accepted. Read the current Roblox and game UI and test one action at a time. Do not convert Left Click, X, or Ctrl into guessed Xbox or PlayStation buttons based on another game.
If prompts change between keyboard and controller, disconnect duplicate devices, rejoin, and confirm which input is active. Avoid external remappers until the normal layout is understood.
Troubleshooting index
Web Zip does nothing
Confirm you are airborne, press Space once, and test away from a wall or landing transition.
Zip chooses the wrong point
Center a clearer destination, reduce camera motion, and test at a closer range without assuming a target priority.
Swing ends early
Check whether the input was released, the route lost a usable anchor, or the character touched a surface.
Dodge feels late
Shorten the preceding attack and verify frame rate before guessing an invulnerability window.
Air Tricks fail
Gain safe height, press X in air, and keep the landing lane visible.
Camera follows the wrong target
Toggle V off, rebuild the group in view, and lock only when one target is the deliberate focus.
Rebinding and accessibility
The public description provides defaults but does not confirm a complete in-game rebinding menu. Use Roblox’s current settings and any Web Rush controls screen that is visible in your build. Prioritize actions that must be reached while moving and controlling the camera.
Frame rate, input latency, camera sensitivity, and device ergonomics can affect movement. A timing comparison should record those conditions. Do not call a key “broken” before testing the same action in open space and a fresh server.
Keep the control map current
Compare the live experience description after updates. If the creator changes an input, the official page should replace the old row. Community videos remain useful demonstrations, but the in-game prompt and current official description decide the active mapping.