> For the complete documentation index, see [llms.txt](https://docs.monaverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monaverse.com/create/building-spaces/adding-interactivity.md).

# Adding Interactivity

There are two ways to add interactivity to a Mona Space : Visual Scripting and Reactor. Custom scripting is currently not supported due to security concerns in a WebGL environment.

Visual scripting is a method of creating game logic using a visual interface instead of writing code in another programming language. This makes it easier for creators to make incredible experiences, all inside Unity 3d. You may have seen this in Unreal with Blueprints. For more information go to [Visual Scripting](/create/building-spaces/adding-interactivity/visual-scripting.md).

Reactor is Mona's approach to interactivity by using events (such as walking into or interacting with a collider) to trigger parameters in the Animator component. This basically removes the need to program anything and focuses on transitioning between different animations that you create when an event happens.&#x20;

If you want a detailed overview of the Reactor process, you can go to the [Mona Reactor](/create/building-spaces/adding-interactivity/mona-reactor.md). If you have a good understanding of Unity's Animation and Animator toolset you could go to [Reactor Overview](/create/building-spaces/adding-interactivity/mona-reactor/reactor-overview.md).

Choosing which method depends on what you are trying to do, but understanding both would definitely allow you to create the best experiences for your space as both are pretty powerful in their own way.


---

# 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://docs.monaverse.com/create/building-spaces/adding-interactivity.md?ask=<question>&goal=<user_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.
