# Add and Configure Input Mappings

{% hint style="info" %}
*Please note that the current version of this tutorial uses the now deprecated input mappings. As of Unreal Engine 5.1, the engine has moved to fully support Enhanced Input Mappings. Currently, the process outlined on this page will still work, but an updated version of this tutorial will be coming soon. It is recommended to move to the Enhanced Input Mappings if you already know how to do this.*
{% endhint %}

Open your Project Settings by clicking **Project Settings** in the **Edit** menu.

<figure><img src="https://lh5.googleusercontent.com/UoUqq5ACezFRQ_LNRUMbfmjvVhBno7xwrp4fcGvLbZkNaCsEd5M1KA2fVKiP3bnuMgPjchJn3JOscDO6Z0qzZj2RnRgUwr0K8FI3-T-mrsSQxK7KYJrliyBjea5mktZo1DrT1slpLCoaux7dFP2Wgok" alt=""><figcaption></figcaption></figure>

Navigate to the **Input** settings and add 5 Action Mappings and 1 Axis Mapping.

<figure><img src="https://lh3.googleusercontent.com/0-pFZrFjaNHZRZLY2ybNctHnobwxa3rtnEKHlyPP-PWtVmrXDbN2F4bqNmDguNMnVyeVmHhWOCeZiASV70X1PdgXVpvY501NMFkuesoRVnWhJ4ExMSUyTWLhE-DLqTJ_jh5JcZkqx4jEgCWCduo5L50" alt=""><figcaption></figcaption></figure>

Set up the mappings with names and default bindings as shown in the below screenshot. Please note that you may wish to create additional bindings, or not use some of these. These are the bindings that will be covered by this tutorial.

<figure><img src="https://lh5.googleusercontent.com/xgx3ldqj0XE--Tebp9EuoI8U7SiS30NlDz_DpLGAaxuXSqCzZnVhGcGlkjNljL8urCnfNEJN44tAhz4B4KD0PzqTAe-SBAOK2nXySyS4INawapc5WuFUaQf8rBLGRw4Ar0VpTOjnl-3uh0JnGhgfXpg" alt=""><figcaption></figcaption></figure>

Close your project settings and return to the event graph within your controller blueprint. You should now be able to add input mapping event nodes for each of the mappings created in the prior step by right clicking within the graph and searching for them by name.

<figure><img src="https://lh5.googleusercontent.com/B6GeX4al_iOjVKsT4qIBNu0PUSZw6ENnAT1J1PBRmnAbMaEDZH-Vk3k1dBx5TZY_NaHMZOFrgs3uD5MeKpOcfsoytJQM3g-4HvEDX9dIdQrbEhNJ6Ezd55GxJhaw06In3uHhX-4lKsqbD3WNqtz0UHQ" alt=""><figcaption></figcaption></figure>

### Create Toggle Map Logic

Add the **Toggle Map** input mapping event. Use a reference to the **BP\_QuestMapPro\_Component-Map** component to add the **Toggle Visibility** node and connect it to the **Pressed** execute pin. Ensure that the input boolean **Animate** is set to **true**.

<figure><img src="https://lh3.googleusercontent.com/dM8Ew-9GnUE6nt3tzUZWfdh5Yt1ltBcMDrhF7fd6TmujnPRnyPW-RbLAY3rGxgwBadO7BygkOiBWhlOmcXG_ql5zCMul96uWYxBHV4OjJqdN2lQPX_9HOh-B5A-ygjNJldVjVQ2xOytPENeY7_5vGls" alt=""><figcaption></figcaption></figure>

### Create Toggle Mini Map Logic

Add the **Toggle Mini Map** input mapping event. Add a **Flip Flop** node connected to the **Pressed** execute pin. Use a reference to the **BP\_QuestMapPro\_Component-Map** component to add the **Toggle Minimap** node. Connect both **A** and **B** execute pins from the **Flip Flop** node to the **Toggle Minimap** execute pin. Use a **NOT Boolean** to invert the **Flip Flop** output **Is A** and hook it up to the **New State** input on the **Toggle Minimap** node.

<figure><img src="https://lh6.googleusercontent.com/8E5jbKdfNz4alCVJnm0q7yK59H6m_O4xxFIA5M1-n0kVBG2RKJEkdpJBwzfVAZejkboj4-I8m43ODnvA5UHwHrIcQ__YrbvgjE-omkGf1sT7kMAbfAuZcv9z8zBymHKzydJSO4Aeb98ufpw3-xIpzGU" alt=""><figcaption></figcaption></figure>

### Create Toggle Compass Logic

Add the **Toggle Compass** input mapping event. Use a reference to the **BP\_QuestMapPro\_Component-Compass** component to add the **Toggle Visibility** node and connect it to the **Pressed** execute pin. Ensure that the input boolean **Animate** is set to **true**.

<figure><img src="https://lh5.googleusercontent.com/3jLiYMekxvYJfSRxLQN3iXEL7Egg5NnU62FgZ6UvQE7tPs-H_dVeRD5WapDEoOuv_HQrNi5DHszJV7lVkY1s1Yt1ZC4pVK5ajggUrbPIb1rdGlEYQ1Xl9xtHd14CTvYYzado0VChP7HCQ_SNOMrVCGU" alt=""><figcaption></figcaption></figure>

### Create Map Zoom Logic

Add the **Map Zoom** input mapping. Add a **Compare Float** node and hook the **Axis Value** up to the **Input** value. Leave the **Compare With** value at **0**. Use a reference to the **BP\_QuestMapPro\_Component-Map** component to add the **Trigger Map Zoom** node twice. Connect one of these nodes up to the **>** execute pin on the **Compare Float**, and the other to the **<** execute pin on the **Compare Float**. Leave the **=** execute pin unconnected. Ensure that both **Trigger Map Zooms** have their target connected to the component reference. On the node connected to the **>** execute pin, ensure that **Zoom In** is set to **true**.

<figure><img src="https://lh4.googleusercontent.com/hZnKmBciar85jxffLZgA9BD_qrb-S8PN4B57K1KQXrDF3KYo_zk8FGMKCFmZStliryoQg5niMOr2yG2DRIIC97QjuqWQjrLrny_wj8HUcF_FC764VDG3nX4dNsB7KASSaOcx9X4z5xlXn7qvOGZS0U0" alt=""><figcaption></figcaption></figure>

### Create Center Map On Player Logic

Add the **Center Map On Player** input mapping. Use a reference to the **BP\_QuestMapPro\_Component-Map** component to add the **Center On Location** node. Ensure that the **Map Type** is set to **World Map**. Use a reference to your player character as the input target on the node **Get Actor Location** and hook up the output vector as the **Location** input.

*Note: If you do not have a reference to your player character, you can use the **Get Controlled Pawn** node, though this may not be appropriate for all projects.*

<figure><img src="https://lh5.googleusercontent.com/KqAN_Z7VVhtPmIHYrrr8Fav0CmgUNLxjzNaWqzpEPEL3jvmUpNwrS30YQbWBnfbYUm9HkS21SUAR7nzvH-ebYuu9EbhqNN3Y6iaK4Mx-u5VL9WNGzLNAJEDXaJkX62f2PCfmzRI6YsC-QobngteGng0" alt=""><figcaption></figcaption></figure>

### Create Cycle Mini Map Zoom Logic

Add the **Cycle Mini Map Zoom** input mapping. Use a reference to the **BP\_QuestMapPro\_Component-Map** component to add the **Cycle Mini Map Zoom** node.

<figure><img src="https://lh4.googleusercontent.com/ZSSt0lO3NUWXlrWd6GTBo7EGRxCDN2mQ-SNkslu5JDGlPqKGeo8PZBznnOBBmxARSiWBNLtJ2OmCWQxUqWTh8NJwCtayObTcMPANZsTegG1Nbcq4dJnqPHFRiIAxisgPxXOvWlGz98cFeWJ6NrPr9Yo" alt=""><figcaption></figcaption></figure>

<details>

<summary>A note on a previous version of this step</summary>

Note: In a previous version of the integration, this process was recreated manually. Since the 1.1 update, on January 2nd, 2023, this process has been built into Quest Map Pro and made significantly more streamlined. If you followed the previous version, that will still work, but this newer setup allows more control and dynamism. It is recommended you switch to this setup instead.

</details>

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Go Back:</td><td><strong>Add Interface to your Character</strong></td><td></td><td><a href="add-interface-to-your-character">add-interface-to-your-character</a></td></tr><tr><td>Next Step</td><td><strong>Add and Configure the Map Helper</strong></td><td></td><td><a href="add-and-configure-the-map-helper">add-and-configure-the-map-helper</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://dapper-raptor.gitbook.io/quest-map-pro/getting-started/integration/add-and-configure-input-mappings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
