> For the complete documentation index, see [llms.txt](https://docs.sollumz.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sollumz.org/documentation/maps/entities.md).

# Entities

Entities represent props, buildings, terrain, or any other models placed in a map. Each entity is linked to a Blender object in the scene. The object defines the archetype name and world transform of the entity.&#x20;

All entity properties and functionality can be found in the Entities tab panel in the sidebar.

<figure><img src="/files/6u1q5n2F44uoKOc04m94" alt="Entities panel" width="375"><figcaption><p>Entities tab panel</p></figcaption></figure>

#### Operators

<table><thead><tr><th width="313.333251953125"></th><th>Description</th></tr></thead><tbody><tr><td><strong>Add Object(s) as Entity</strong></td><td>Add the selected objects in the scene to the map as an entity for each object.</td></tr><tr><td><strong>Go To Entity</strong></td><td>Select the object linked to the entity and move the view to its location.</td></tr><tr><td><strong>Instance Entities</strong> / <strong>Remove Instances</strong></td><td>Re-create the entities linked objects after import or delete them. The entities still exist in the map, only the Blender objects are removed from the scene.</td></tr><tr><td><strong>Show / Hide Entities</strong></td><td>Toggle the visibility of entity objects at specific LOD levels.</td></tr></tbody></table>

#### **Properties**

<table><thead><tr><th width="192.6666259765625">Property</th><th>Description</th></tr></thead><tbody><tr><td><strong>LOD Parent</strong></td><td>The parent entity of this entity in the <a href="/pages/8OyW4BCQg4AOZsXOVwLN">LOD hierarchy</a>.</td></tr><tr><td><strong>LOD Level</strong></td><td>Level of this entity in the LOD hierarchy.</td></tr><tr><td><strong>LOD Distance</strong></td><td>Override the distance at which the object unloads. The default -1 uses the LOD distance defined in the archetype.</td></tr><tr><td><strong>Child LOD Distance</strong></td><td>Override the LOD distance of the children entities of this entity in the LOD hierarchy.</td></tr><tr><td><strong>Priority Level</strong></td><td>Only relevant for <strong>HD</strong> entities. Determines whether the game is allowed to skip creating this entity when loading the map in certain cases. </td></tr><tr><td><strong>Natural AO Multiplier</strong></td><td>Natural ambient occlusion multiplier.</td></tr><tr><td><strong>Artifical AO Multiplier</strong></td><td>Artificial ambient occlusion multiplier.</td></tr><tr><td><strong>Tint Value</strong></td><td>Palette index for models using tint shaders.</td></tr></tbody></table>

#### Entity Extensions

<table><thead><tr><th width="197.3333740234375">Extension</th><th>Description</th></tr></thead><tbody><tr><td><strong>Door</strong></td><td>Additional settings for door entities.</td></tr><tr><td><strong>Spawn Point Override</strong></td><td>Used to override settings from spawn points in the archetype.</td></tr><tr><td><strong>Light Effect</strong></td><td>Used to override settings from lights found in the base model.</td></tr></tbody></table>

***

To quickly view the entity properties associated with the selected object, you can use the "Sollumz > Map Entity Properties" panel in the object properties tab.

<figure><img src="/files/yrmkoeLCHeOvatCtZtBi" alt="" width="375"><figcaption><p>Entity properties of the selected object</p></figcaption></figure>

The "View in Sidebar" button synchronizes the selection in the Entities list with the selected objects in the scene.&#x20;

### MLO Instances

MLO instances are used to place interiors in maps. There are two main ways to create MLO instances:

* From an MLO created in the same `.blend` file.
* From an asset library.

The MLO panel in the sidebar has a "Create MLO Instance" button that creates a copy of your MLO as a single object, ready to be placed in a map. The refresh button next to it is used to update all existing instances to reflect the latest changes in the MLO, generally added or deleted entities.

<figure><img src="/files/XCBsuGX16sHE7QH5D4C1" alt="Location of &#x22;Create MLO Instance&#x22; button" width="375"><figcaption><p>Location of "Create MLO Instance" button</p></figcaption></figure>

When using an [asset library](/documentation/asset-libraries.md) created from a YTYP with MLO, you can simply drag and drop the MLO asset into the scene.

<figure><img src="/files/D3Ab1rSDnjTM0CBHzYp1" alt="MLO instance from asset library"><figcaption><p>MLO instance from asset library</p></figcaption></figure>

Now, you can add the MLO instance objects to a map like any other entity object, for example using "Add Object(s) as Entity". The new entity should be marked as MLO and the MLO-specific properties appear in the panel.

<figure><img src="/files/N09S8VkTcDnMWzi9y3oq" alt="MLO instance properties" width="375"><figcaption><p>MLO instance properties</p></figcaption></figure>


---

# 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.sollumz.org/documentation/maps/entities.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.
