> 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/prefabs.md).

# Prefabs

### Creating Prefabs

Prefabs must be created in the editor by right clicking in the [Hierarchy](/using-the-editor/hierarchy.md)and selecting "create prefab".

When you do this, a new asset will be created in your asset explorer window that can be dragged into the scene.

To edit a prefab, right click on it and click "Edit Prefab" which will open a new window to make changes to those entities.

When you save a prefab, all instances of that prefab in your scene will automatically be updated.

### Limitations

{% hint style="info" %}
The All Out prefab system is currently very early in development and doesn't allow for dynamic fields on each instance of a prefab (except position of the prefab). This means you cannot have many copies of a prefab with different values (for example cost of an upgrade or tier of an item)
{% endhint %}

### Unlinking Prefabs

You can change an instance of a prefab in your scene back into its individual entities by right clicking it in the hierachy and selecting "unlink". This can be useful if you need to add dynamic fields.


---

# 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/prefabs.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.