> For the complete documentation index, see [llms.txt](https://guide.strikepack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.strikepack.com/horizon/strikepack-horizon-app-guide/shooter-studio-guide/6-action-button-mapping.md). # 6 - Action Button Mapping

Action Button Mapping

STRIKEPACK HORIZON™ Gaming Adapters

{% embed url="" %} Watch Video on YouTube **In the video above,** you'll learn how to use the **STRIKEPACK HORIZON** app to map to the STRIKEPACK HORIZON adapter's four numbered **Action Buttons** (Paddles). **Written Steps:** {% stepper %} {% step %} Each profile has its own separate **Mapping Settings**, so start by going to your profile. This will take you to the **Overview** screen. *** {% endstep %} {% step %} To open **Mapping Settings**,

**tap** the **Mapping** button on the bottom-bar. *** {% endstep %} {% step %}

**Tap** the **Edit** button for **Action 1** (*or whichever numbered Action Button/Paddle you want to map to*). *** {% endstep %} {% step %} To map a button,

**tap** the **on-screen button** to highlight and select it. * You can map up to four controller buttons per Action Button. *

**Tap** individual **on-screen buttons again** to remove their mapping, or **Clear Action** to start fresh. *** {% endstep %} {% step %} Now use the **Arrows** to switch to another Action Button. *** {% endstep %} {% step %} Besides the **Standard** mapping, you can change the **Action Button Mode** to **Override**, which will block the original button, preventing it from being accidentally pressed. *** {% endstep %} {% step %}

**Tap** the **Back Arrow** to return to the **Mapping Settings**. You can see your updated configuration at a glance. *** {% endstep %} {% step %} Tap the **Mapping** button again to close Mapping Settings. {% endstep %} {% endstepper %} *** Now you're all set to experiment with different mapping configurations. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://guide.strikepack.com/horizon/strikepack-horizon-app-guide/shooter-studio-guide/6-action-button-mapping.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.