> For the complete documentation index, see [llms.txt](https://docs.twgamesdev.com/uhfps/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.twgamesdev.com/uhfps/guides/managing-inputs/adding-inputs-to-ui.md).
# Adding Inputs to UI
{% hint style="info" %}
Newly created inputs are not automatically added to the options settings, so you need to do a few extra steps to see the newly added inputs and be able to rebind them.
{% endhint %}
1. Open the **GAMEMANAGER** / **MAINMENU** prefab. Both prefabs can be found in the **UHFPS -> Content -> Resources -> Setup** folder.
2. Find the **Panel\_Controls** object in both **GAMEMANAGER** and **MAINMENU**.
3. Under the Viewport -> Content inside **Panel\_Controls** you will notice many binding objects. Those represent the actual controls that are shown in the options.
4. To add a newly created control, simply duplicate the **Binding\_Forward** or another binding object.
5. Select the duplicated binding and in the **Input Options** component, assign the newly created input to the **Input Reference** field.
6. Finally, in the **GLoc Text** component, select **Gloc Key** that represents the localization key for the input binding.
{% content-ref url="/pages/9EMA4QvNmnZw3Q6klDyG" %}
[Localization](/uhfps/guides/localization.md)
{% endcontent-ref %}
{% hint style="info" %}
To display a newly created input actions in both the Main Menu and Pause Menu, you must perform the same steps in the GAMEMANAGER and MAINMENU prefabs.
{% endhint %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.twgamesdev.com/uhfps/guides/managing-inputs/adding-inputs-to-ui.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.