> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/systems/systems-intro/game-controls.md).

# Game Controls

***For a list of current controls and control ideas see link below.***

{% content-ref url="/spaces/hffJRpQgXgXOOhvtML3c/pages/hJmI2FHP0R9XOTPv2Zvd" %}
[Broken mention](broken://spaces/hffJRpQgXgXOOhvtML3c/pages/hJmI2FHP0R9XOTPv2Zvd)
{% endcontent-ref %}

## Input Actions

***All implemented controls are (and must be) in Content/Systems/Input/Controls.inputactions***

If you are not familiar with the new input system, here are two [good ](https://docs.unity3d.com/Packages/com.unity.inputsystem@1.0/manual/Actions.html#using-actions)[guides](https://gamedevbeginner.com/input-in-unity-made-easy-complete-guide-to-the-new-system/#action_maps) for almost everything you might need.

After saving Controls.InputAction, it regenerates Console class in Scripts/SS3D/System/Inputs. You can use Controls class in your script by getting Input property in InputSystem through Subsystems.

All actions and action maps should be named in PascalCase with spaces between words. (Toggle Run, Snap Right, Snap Left, etc). Avoid long names.

All handlers, that subscribe to actions, have to contain InputAction.CallbackContext argument. Handlers have to be subscribed to actions in OnStart() and unsubscribed in OnDestroyed().

If you want to Disable/Enable some acitons (or action maps), use Toggle methods in InputSystem, otherwise, it will  cause issues.

Input Consumption is enabled. It means, in actions with modifiers you have to press modifiers first and binding last. This feature prevent multiple actions from being performed unintentionally (For example, if you have E action and CTRL+E action and you pressed CTRL+E, E action won't be performed).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ss3d.gitbook.io/systems/systems-intro/game-controls.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.