> For the complete documentation index, see [llms.txt](https://malbersanimations.gitbook.io/animal-controller/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://malbersanimations.gitbook.io/animal-controller/how-to-ac/input-to-an-action.md).

# Connect Inputs to the Controller

## Overview

To connect any Input to the Animal Controller you can use the [**Malbers Input** ](/animal-controller/main-components/malbers-input.md)component

<figure><img src="/files/Wn4kqWgP0QQwkFUFi1R7" alt="" width="557"><figcaption></figcaption></figure>

## &#x20;Automatic Connections

All the States, Modes, Abilities and Stances have an Input parameter to connect any input to the activation of the logic automatically.&#x20;

{% hint style="warning" %}
The name of the Input of each logic  must match the Malbers Input component name
{% endhint %}

### Connecting States

For the States, find the Enter Input and Exit Input. Make sure the Name matches in both components:

<figure><img src="/files/dfHfOCN4rGaeMh2jRpvw" alt="" width="563"><figcaption></figcaption></figure>

### Connecting Modes

For the modes, find the Input Parameter in the General Tab

<figure><img src="/files/L3XqbP1w8tbD7QsJvvHs" alt="" width="563"><figcaption></figcaption></figure>

### Connecting Abilities inside modes

Sometimes you will need to connect a specific ability to an Input. Find the Input for an ability after selecting the Mode, then the Ability, and then, on the General Tab the input parameter.

<figure><img src="/files/A30yTlSdEashiae2RHJf" alt=""><figcaption><p> </p></figcaption></figure>

### Connecting the Stances

For the Stances, you can find it when a stance is selected.

<figure><img src="/files/fuQWnQC6XYTaGJDAsGhX" alt="" width="563"><figcaption></figcaption></figure>

## Manual Connections

Not all logic has automatic connections, in that case, you will need to go directly to the Input Events and use the events to call the methods directly. Here are some examples:

<figure><img src="/files/U8LTYoMr0C3RHwaqpBbo" alt="" width="559"><figcaption><p>The Sprint Input is connected dynamically to the Animal.Sprint property. </p></figcaption></figure>

<figure><img src="/files/mna7HbyN314buH7msbCE" alt="" width="557"><figcaption><p>The Interact Input is connected to the Pick Up Logic</p></figcaption></figure>

<figure><img src="/files/k4YPRP47Qm7XwwP74JAL" alt="" width="560"><figcaption><p>The Mount Input is connected to the Rider.MountAnimal Logic</p></figcaption></figure>

Other scripts like the [**Weapon Manager**](/animal-controller/main-components/weapon-manager.md#inputs) also have Automatic connections.


---

# 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://malbersanimations.gitbook.io/animal-controller/how-to-ac/input-to-an-action.md?ask=<question>&goal=<endgoal>
```

`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.