# Setup
## Prerequisites
Before you begin, ensure you have the following:
* Unity 6 LTS or higher.
* Input System 1.11.2 or higher.
{% hint style="warning" %}
Before installing the package, verify that the **Active Input Handling** is set Input `System Package (New)` or `Both` in `Project Settings → Player`.
{% endhint %}
## Installation
To install the Input Mapper package, follow the instructions below.
{% stepper %}
{% step %}
### :book-open: Open Unity Package Manager
Navigate to **Window** **→** **Package Manager** in the top menu.
{% endstep %}
{% step %}
### :searchengin: Search for the Package
In the **My Assets** tab, use search bar and find **Input Mapper for Unity**.
{% endstep %}
{% step %}
### :download: Download and Import the Package
Once found, Select the package and click **Download** then **Import.**
{% endstep %}
{% step %}
### :check: Verify Installation
After importing, the `InputMapper` folder should appear in `Assets/Plugins`.
{% endstep %}
{% endstepper %}
{% hint style="success" %}
After Installation, We recommend checking out the [example scenes](https://niam.gitbook.io/input-mapper-for-unity/getting-started/examples) to learn about most features and see how things set up.
{% endhint %}
## Create Your First Prompt
In the Hierarchy window, right-click and navigate to **UI → Input Mapper**, then select the appropriate boilerplate template for your use case.
* [**Input Prompt – Text**](https://niam.gitbook.io/input-mapper-for-unity/components/input-prompt-text)\
Display bindings as readable text, such as "Press E to Interact".
* [**Input Prompt – Sprite**](https://niam.gitbook.io/input-mapper-for-unity/components/input-prompt-sprite)\
Display bindings as icons/sprites (great for controller-heavy UI).
* [**Input Prompt – Binding**](https://niam.gitbook.io/input-mapper-for-unity/components/input-rebind-binding)\
Updates the binding path of a specific input binding of action at runtime.
* [**Input Prompt – Processor**](https://niam.gitbook.io/input-mapper-for-unity/components/input-rebind-processor)\
Expose sensitivity/invert/deadzone style processor tuning.
{% hint style="success" %}
Navigate to **3D Object → Input Mapper** for non-canvas input prompt templates.
{% endhint %}
## Best Practices
### Setting up Binding Order
Each binding is displayed in the same order defined in the Input Action Asset.
### Working with Composites
The Input Prompts ignore subsequent parts of a composite binding when they share the same name.
:xmark: Arrow Keys is omitted.
While moving the duplicate-name binding to the end works as a workaround, they are still treated as a single control, so the control separator is not applied.
:xmark: Shows both WASD and Arrow Keys, but no delimiter.
Instead, create a new composite binding and move the components with duplicated names into that composite.
:check: Shows both WASD and Arrow Keys with delimiter.
