> For the complete documentation index, see [llms.txt](https://niam.gitbook.io/input-mapper-for-unity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://niam.gitbook.io/input-mapper-for-unity/getting-started/setup.md).
# Setup
Welcome to the Input Mapper package! This guide will help you get started with the package, covering the initial setup, basic usage and best practices.
## Prerequisites
Before you begin, ensure you have the following:
* Unity 6 LTS or higher.
* Input System 1.16 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, a popup window will appear prompting you to import the TextMeshPro Essential Resources.
{% 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**](/input-mapper-for-unity/components/input-prompt-text.md)\
Display bindings as readable text, such as "Press E to Interact".
* [**Input Prompt – Sprite**](/input-mapper-for-unity/components/input-prompt-sprite.md)\
Display bindings as icons/sprites (great for controller-heavy UI).
* [**Input Prompt – Binding**](/input-mapper-for-unity/components/input-rebind-binding.md)\
Updates the binding path of a specific input binding of action at runtime.
* [**Input Prompt – Processor**](/input-mapper-for-unity/components/input-rebind-processor.md)\
Expose sensitivity/invert/deadzone style processor tuning.
{% hint style="success" %}
Navigate to **3D Object → Input Mapper** for non-canvas input prompt templates.
{% endhint %}
## Pro Tips & Best Practices
### Setting up Binding Order
Keep in mind that Input Mapper displays bindings in the exact order they are arranged in your `Input Action Asset`. If you want a primary key to show up first, make sure it's at the top of the list!
### Working with Composites
When dealing with composites (like 2D Vector with WASD and Arrow Keys), Input Prompts will ignore subsequent parts of a composite binding if they share the exact same name (e.g. Up, ~~Up~~, Down, ~~Down~~, Left, ~~Left~~, Right, ~~Right~~).
:xmark: Arrow Keys is omitted.
While moving the duplicate-name binding to the end of the list works as a hacky 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 brand new composite binding and move the alternative controls (like the Arrow Keys) into that separate composite. This keeps things organized and lets Input Mapper format them beautifully!
:check: Shows both WASD and Arrow Keys with delimiter.
