> For the complete documentation index, see [llms.txt](https://mirror-networking.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mirror-networking.gitbook.io/docs/manual/examples/additive-levels.md).
# Additive Levels
The Additive Levels example demonstrates the following:
* Using Additive Scenes with Scene Interest Management.
* Teleporting between levels via portals and respawning.
* Custom Scene Loading with Fade In / Out transition.
## Setting Up
For this example to work correctly, some setup is required.
First, add all the scenes to Build Settings:
Next, add a Player and Portal Layer to Project Settings under Tags and Layers:
... and in Physics settings set the matrix so that Portal only collides with Player:
Finally, open the Offline scene, and click Play in the editor, and click Host in the HUD.
* Player controls are WASD+QE to move and turn.
* Move into the Portal in the corner with a scene label over it. Your player will be changed to the other level scene.
* Move into the Portal in the corner of the 2nd scene, and your player will be changed back to the first scene
If you make a build and start two or more instances (one as Host or Server, the other(s) as clients, and move each one, you'll see that only players in the same level can see and collide with each other.
---
# 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://mirror-networking.gitbook.io/docs/manual/examples/additive-levels.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.