> 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/building-worlds.md).
# Building Worlds
### Layering and Depth Offset
Sprite\_Renders and Spine\_Animators have two unique properties that determine which is on top as they move up and down in the scene.
**Layer** is the broad and simple way of deciding what goes on top. Elements with a low layer will be behind everything. Some recommended values might be:
* Map background textures: -100 layer
* Players, NPCs, Cars: 0 layer
* Overlays, clouds, particles: 100 player
**Depth Offset** is more precise and lets you determine when something will go behind something else if it's **on the same layer**.
* Adjust the depth offset easily using the depth offset tool in the top left of the scene view.
The player will appear behind the object when it is above the red line, and in front of the object when it's below.
### Schleem for Scale
To easily check the sizing and layering of elements in your game, you can preview a player's character by holding `ctrl+spacebar` and moving your mouse around the scene window.
---
# 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/building-worlds.md?ask=&goal=
```
`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.