Input System workflows
Choose how your project reads input: through actions only, through actions and the Player Input component, or directly from devices.
Many projects use actions, which separate what the player does from the device controls they use. You can configure actions in the Input Actions Editor or in code. For simple projects or prototypes, you can skip actions and read device controls directly. Code examples in this documentation use different workflows, depending on the topic.
| Topic | Description |
|---|---|
| Input System workflows comparison | Compare the actions, Player Input component, and direct device workflows to choose how your project reads input. |
| Actions workflow | Follow this workflow to configure actions in the Input Actions Editor and read their values in your scripts, for most games and apps. |
| Actions and Player Input component workflow | Follow this workflow to connect actions to methods on your GameObjects without code that finds the actions, for event-driven input and local multiplayer. |
| Direct device workflow | Follow this workflow to read device controls directly in your scripts, for prototypes and single-platform projects. |