Published controls
The experience description publishes one control line for each device. It does not publish a full binding chart.
| Device | Published control | Still unpublished |
|---|---|---|
| PC | WASD + mouse | Which mouse button jumps, boosts, shoots, or moves the camera |
| Mobile | On-screen controls | The names and positions of those buttons |
| Console | A compatible controller | Supported pads and the button map |
WASD is the published PC movement scheme: W, A, S, and D. The mouse is named, and the button layout is not.
Learn the buttons your client shows
- Join a server and find open space before you challenge for the ball.
- On PC, tap W, then S, then A, then D. Confirm that the car moves in the direction you expect.
- Press one extra mouse button or on-screen button at a time. Watch the car, then try the next button.
- On a controller, test face buttons and shoulders one at a time. The listing only says a compatible controller works.
- Keep the binding that your client just demonstrated. Another car-soccer game's chart belongs to that other game.
Where the word Boost appears
Boost shows up in two places in the description.
- The customization sentence lists boosts with skins, wheels, and decals.
- A short keyword line reads Car, Soccer, Ball, Boost.
Neither line names a boost key, a boost meter, a duration, or a speed value. If your client shows a boost control, test a short burst in open space and use what the car does. If your client shows a boost cosmetic in a garage, treat that as customization. The boosts entry keeps those two readings separate.
Mobile and console
Mobile players use the buttons drawn on the screen. There is no published diagram of that layout, so the on-screen labels are the authority for a phone or tablet session.
Console players need a controller the experience accepts. If one button does nothing, try the next button rather than assuming a layout from a different game.
What to write down
After one open-space pass, you should know how your device steers and which extra button your client uses for the actions it actually has. Bring that personal map into a real match. Ranked advice that depends on an unpublished button does not belong in a plan yet.