# Button/Key

*<mark style="color:orange;">Versions before 4.0 all handled key input with the</mark> <mark style="color:orange;"></mark><mark style="color:orange;">`InputSystemController`</mark> <mark style="color:orange;"></mark><mark style="color:orange;">script on individual components. Which is optional now.</mark>*

*Input is handled with two different scripts.*&#x20;

## *<mark style="color:yellow;">1. Button Input Processor</mark>*

*Controls the behavior of the UI on the scene. Dictates if they should individually handle by the components themselves or by the button input processor.*

{% content-ref url="/pages/otTYcsPO0a5yrLIW6OyF" %}
[Button Input Processor](/modular-3d-text/input/button-key/button-input-processor.md)
{% endcontent-ref %}

##

## *<mark style="color:yellow;">2. Button Input System</mark>*

*Attached to UI elements that can/should be controlled. If individual controls are selected, this controls the button input as well, otherwise, it is called by the button input processor when required and this calls the proper methods for the UI element like list.*

{% content-ref url="/pages/6kK3RWu6ohSq9dgxiG1P" %}
[Button Input System](/modular-3d-text/input/button-key/button-input-system.md)
{% endcontent-ref %}


---

# 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://ferdowsur.gitbook.io/modular-3d-text/input/button-key.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.