> For the complete documentation index, see [llms.txt](https://docs.odyssey.stream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.odyssey.stream/realtime-configurator/level-and-object-configurator/object-configurator.md).

# Object configurator

**Object Configurations** are a way for you to add configuration data *per Imported Actor.* The defined configuration UI will show up in your actor menu after being placed.

{% hint style="warning" %}
Make sure you have set up your **Object Library** and at least one **Imported Actor** by following the instructions in [Actor importer](/realtime-configurator/actor-importer.md).
{% endhint %}

## Create a configurator dataset

1. In your project's content browser, right click and go to **Odyssey -> Odyssey Configurator Dataset.** Name it after your Imported Actor.<br>

<figure><img src="/files/Dz42NX2ZSXSCL1qgUPHK" alt="" width="265"><figcaption></figcaption></figure>

2. Open your `Odyssey Configurator Objects Library` asset (created in [Actor importer](/realtime-configurator/actor-importer.md)).
3. In the row that holds your object, under **Configurator Dataset ->** Add your newly created configurator dataset.

{% hint style="info" %}
You will need to follow these steps for every Imported Actor you want to attach configuration properties to.
{% endhint %}

## Create a configuration property

1. Open your Configurator Dataset asset.
2. &#x20;Add a Configurator key to the Dataset using the Add button:<br>

   <figure><img src="https://files.readme.io/977e050-obraz.png" alt=""><figcaption></figcaption></figure>
3. Fill your configuration data in your newly created row. Each configuration needs a **Display Name, Type,** and a **Default Value.**

   <figure><img src="https://files.readme.io/6e8926d-obraz.png" alt=""><figcaption></figcaption></figure>

## Add configuration logic

1. Open your **Imported Actor** blueprint (type `OdysseyConfigurable`).
2. Override the `Handle Configuration State Change` function

<figure><img src="https://files.readme.io/0eda8dd-configurator_objects_step3.gif" alt=""><figcaption></figcaption></figure>

3. Connect your custom configuration logic to the exec pin of the newly created event.

<figure><img src="https://files.readme.io/af22460-obraz.png" alt=""><figcaption></figcaption></figure>

4. From this point you can follow the guide [Configurator blueprint API](/realtime-configurator/level-and-object-configurator/configurator-blueprint-api.md) to learn how to set up events and hooks from your configurator properties.


---

# 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://docs.odyssey.stream/realtime-configurator/level-and-object-configurator/object-configurator.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.
