> For the complete documentation index, see [llms.txt](https://docs.allout.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allout.game/using-the-editor/hierarchy.md).

# Hierarchy

### Entities

Entities are the building blocks of worlds in All Out. Every player and object in games is an "Entity" and the hierarchy is where you can see all of the entities in your game world.

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

You can click on any entity in your game to highlight it in the hierarchy.

When an entity is selected in the hierarchy, its properties (like size, position, and layering) can be changed in the [Inspector](/using-the-editor/inspector.md)

#### Creating New Entities

There are 3 ways to make new entities in your scene

* Press the "+" button at the top of the hierachy
* Right click empty space on the hierachy and click "New Entity"
* Drag an [Asset Catalog](/using-the-editor/asset-catalog.md) asset into the scene

### "Folders"

To make the equivalent of a folder, just create a new entity and drag other entities on top of it to group them.

This is especially useful if you have a set of entities you want to duplicate because you can hit ctrl+d with the "folder" entity selected and it will also duplicate all of the child entities grouped under it.


---

# 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.allout.game/using-the-editor/hierarchy.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.