> For the complete documentation index, see [llms.txt](https://hiveminddocs.gitbook.io/hivemind/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hiveminddocs.gitbook.io/hivemind/code-systems/ultimate-interaction-system-uis/classes/interfaces/activation-interface.md).

# Activation Interface

The default Activatable Actor that comes with this system (`BP_BUIS_Activatable`) is set up with this interface already, but if you need or want to create your own Activatable then you'll need to add this interface to your Activatable Actor.

## <mark style="color:blue;">Setting up your own Activatable Base Class</mark>

Head to your custom interactable class then go into the Class Settings Menu and then in the details panel look under Implemented Interfaces, and add the `BPI_BUIS_ActivationInterface`.

<figure><img src="/files/Cx5Inyk3f4ZAPu8Vg3fT" alt=""><figcaption></figcaption></figure>

You will now have two different functions underneath the Interfaces in the category to the left.

* <mark style="color:yellow;">Get Activation Component</mark>: Allows you to easily get the activation component of any actor implementing this interface.
* <mark style="color:yellow;">Can Activate</mark>: Easily Determine if you can activate this actor. This has to return true before the actor can be activated.

Its important that you implement both of these functions correctly.

First head into the <mark style="color:yellow;">Can Activate</mark> function and make sure that the return value is returning `true` and not false. If it returns `false`, then it'll fail to activate.

Then head into <mark style="color:yellow;">Get Activation Component</mark> and make sure it returns the Activation Component on your Activatable. If this function doesn't return the Activation Component then it'll fail to activate.

This is all that is required to set up your activatable. This should allow you to set up any form of logic to allow for determining if an activatable can be activated or not and even activate.


---

# 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://hiveminddocs.gitbook.io/hivemind/code-systems/ultimate-interaction-system-uis/classes/interfaces/activation-interface.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.