# SORTING LAYERS

### Overview

As you can see, the demo scene has platforms of different height levels. To make them sorted correctly, each height level is put at a different `Sorting Layer`. Inside each `Sorting Layer`, objects also have different `Order in Layer` values.

<img src="/files/L03VLZjxK2IDYcNDLzkT" alt="" width="375">

For collision to work correctly in each height level, objects in different `Sorting Layer` should also be put into corresponding `Layer`.

In order to make the player object able to travel between different layers. There is a `Edge Collider 2D`  with `Stair Layer Trigger`  script attached. When the player object touches the trigger, it will be sent to the layer and sorting layer defined in the script.

<figure><img src="/files/ejMxCvlBHa9vD6Wo6cQe" alt="" width="375"><figcaption></figcaption></figure>

### Import Tags & Layers Settings

The demo scene needs proper tags & layers settings to work properly. In order to include the tags & layers settings, the asset is uploaded as a complete project. On import, you should be able to see the project settings included.

If you did not import the tags & layers settings on import, you can still set it by clicking the slider icon at the top right corner of the Tags & Layers settings and select the preset included in the asset.

<div><img src="/files/AYjFNQs6h1ihbdsIhKzj" alt="" width="279"> <img src="/files/tYrk8tnmPolTcN5jzE1h" alt="" width="344"></div>

<div><img src="/files/s9JN25eBP3cRvIZIDJUj" alt="" width="352"> <img src="/files/fNimuZi6a2Kfv3REEyIQ" alt="" width="269"></div>


---

# Agent Instructions: 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:

```
GET https://docs.cainos.net/pixel-art-top-down-basic/sorting-layers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
