# Behavior Framework

**Behaviors** are custom programs external to Morpheus Platform. They implement event-based interactivity of Artifacts. Artifact developers can extend platform functionality using behaviors to make complex features out of simple blocks. For example, Scoreboard is a Content Display that changes its text every time it is hit by a Boxing Glove.

**Behaviors are ‘plugins’ of Morpheus.**

## Why Behaviors <a href="#why-behaviors" id="why-behaviors"></a>

True platform should allow not just to add different kinds of [**Content**](https://platform.morpheusxr.com/for-content-creators) like Worlds and Artifacts, but also to implement interactive behaviour of such Content. This must be done neither by changing client apps nor by changing backend servers.

Third-party Artifact developers should be able to make interactive objects and host their code (scripts) on their own servers. And our platform should give them tools to connect those scripts to Artifacts.

Behaviors focus on **separation of custom interactivity** from platform features. They use **Channels** for interoperability, **Planes** for visibility, and **Messaging** for connecting custom scripts with internals of Morpheus Platform.


---

# 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://platform.morpheusxr.com/platform-modules/external-integrations/behavior-framework.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.
