Illegal Soccer Controls

§Start here: where the game keeps its own control settings#

Your client is the source of truth. Read it before you read anything else, including this page.

Every Roblox experience exposes a control surface through the client, and the mapping it shows is the mapping that build is using. Open the in-experience menu, find the settings or controls area, and read what is listed there. If you have rebound anything before, that panel is where the change is visible too.

That habit solves the question permanently. A key table on a website can be accurate on the day it is written and wrong after the next update, and this game is updated regularly, so the in-client list is both faster and more reliable than any page.

§Officially supported actions#

The action layer is settled; only the input layer is undocumented.

Two different things get muddled in control questions: the action the game supports, and the input your client binds to it. The first is documented. The developer's own description names kicking, tackling, fighting and the use of guns, grappling hooks and jetpacks, and every platform client supplies movement, camera, jump and a menu. That is the list this page treats as official.

What no first-party source documents is the mapping: which input performs each action on your device. That is why the third column below points at your client rather than at a key.

§Community-reported keybinds, kept separate#

Community-reported: verify in your client. Not confirmed by Roblox or Repotted as of 2026-09-14.

Third-party guides publish PC key tables and head them with the word confirmed. That word is the third-party site's label for its own table, not the developer's, and no first-party source backs it. We keep that material in its own lane and mark it as unverified rather than printing the strings as a reference you could trust.

That is a deliberate refusal of false precision. A key string copied from a page you cannot date can be wrong after a single update, and copying it would make it look official. The table below separates the actions community tables claim inputs for from the verification step that settles each one.

§What to check before you rebind anything#

Three checks that prevent most self-inflicted control problems.

• Confirm which action you are actually failing at. Most frustration in this game comes from timing and positioning, not from a key being in the wrong place.
• Check for a conflict before you commit. Two actions on one input usually means one of them silently stops working.
• Change one thing at a time. Rebind a single action, play a match, and keep the change only if the match felt better.

§PC, mobile and console are different surfaces#

Availability is platform-wide; the control surface is not.

The official listing makes the experience available across the platform's clients on Windows, MacOS, iOS, Android, Xbox, PlayStation and Meta Quest. That tells you where you can play; it does not tell you that the controls are the same, and they are not. A touch layout, a keyboard and a controller present the same actions in different places.

Practically, this means control advice has to name its device to be useful, and any list that does not is probably copied from somewhere else. Our advice is deliberately device-neutral, because your own settings panel is the only thing that knows your surface.

§The four things most players end up changing#

Named as intentions, not as inputs. Find each one in your own list and set it where your hand expects it.

• Camera control. Looking up while travelling with the ball is the single most useful habit in this game, so anything that makes camera movement awkward is worth fixing first.
• Movement and sprinting. If you cannot move and look at the same time comfortably, fix that before you touch anything else.
• The primary action you use most, usually the kick. Putting it where your hand rests reduces the delay between seeing a chance and taking it.
• Sensitivity. A setting that is too high makes small adjustments impossible; one that is too low makes you slow to turn. Change it once, then leave it alone for a week.

§Why this page publishes no keybind table#

Because a table would be read as authoritative, and nothing authorises it.

Community pages do publish key tables, and at least one labels its own table as confirmed. That label is the third-party site's own assertion, not the developer's, and no first-party source documents input mapping for this experience. Printing such a table here would launder somebody else's guess into something that looks official.

Instead, this page describes what to change and why, and leaves the actual input to the panel that owns it. If the developer ever publishes control documentation, this page will be replaced with real references on the day it appears.

§What we cannot confirm about controls#

The gaps, stated plainly so you know what you are not reading.

• Any default keybind, button layout or gesture, on any platform.
• Whether the developer supports rebinding at all, beyond what the client's own settings surface offers.
• Whether control behaviour differs between the mobile, console and desktop clients in any specific way.
• Any aim assist, sensitivity curve or accessibility option that a first-party source has not described.