> For the complete documentation index, see [llms.txt](https://october-studio.gitbook.io/monster-survivors-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://october-studio.gitbook.io/monster-survivors-documentation/game-structure/game-scene.md).

# Game Scene

<figure><img src="/files/zg8DuGDNITLj5b378TmU" alt=""><figcaption><p>Game Scene Hiererchy</p></figcaption></figure>

## Game Management

This GameObject contains all of the components that manage the various systems of the game.

<figure><img src="/files/4KLTgSIzhGgnIRaX69z8" alt=""><figcaption><p>Game Management Hierarchy</p></figcaption></figure>

<table data-full-width="false"><thead><tr><th width="181">Component</th><th>Description</th></tr></thead><tbody><tr><td>Abilities Manager</td><td>This component is responsible for managing abilities. To find out further, read <a href="/pages/BvLvMKIKpbXjamDgKvZN">Abilities System Structure page</a></td></tr><tr><td>Drop Manager</td><td>This component manages drop - the items that spawn when enemy dies, such as gold, healing, chest, magnet, bomb, gems</td></tr><tr><td>Easing Manager</td><td>Easing Manager is an in-house analog of the DoTween asset, that is build on top of Coroutines. It provides an easy way to animate gameObjects.</td></tr><tr><td>Enemies Spawner</td><td>This component is responsible for spawning enemies and bosses</td></tr><tr><td>Experience Manager</td><td>This component manages experience points and level ups the player </td></tr><tr><td>Field Manager</td><td>This component controlls ground, spawns end despawns <a href="/pages/a0KTcm1CVtUViv1acTFx#stage-background">chunks of ground</a>  </td></tr><tr><td>Pools Manager</td><td>This component provides access to a simple <a href="https://learn.unity.com/tutorial/introduction-to-object-pooling#">pooling system</a>. </td></tr><tr><td>Safe Area Manager</td><td>This is a small components that manages safe area on mobile platforms</td></tr><tr><td>Stage Director</td><td>This component is responsible for running the stage timeline</td></tr></tbody></table>

***

### Canvas

Game Canvas consists of the three screens and three windows

<figure><img src="/files/M9372I5Mcis9TgcjR4k7" alt=""><figcaption><p>Game Canvas Hierarchy</p></figcaption></figure>

<table><thead><tr><th width="226">UI</th><th>Description</th></tr></thead><tbody><tr><td>Game Screen</td><td>The main ui of the game that the player will see 95% of the time. Contains xp progressbar, timer, joystick, coins and kills indicators, and abilities, chest, pause windows</td></tr><tr><td>Abilities Window</td><td>This window shows up every time the player levels up. The player is presented with three random abilities to choose from</td></tr><tr><td>Chest Window</td><td>Chest window shows up every time the player picks up the chest drop item. It rewards player with 1, 3 or 5 random abilities</td></tr><tr><td>Pause Window</td><td>This window lets the player to toggle sounds, music and vibration, and to exit to the main menu</td></tr><tr><td>Stage Failed Screen</td><td>This screen shows up when the player dies. The player can choose whether to revive (if the <a href="/pages/JeiPat8SkvqMYZpgeOso">revive upgrade</a> is bought) or to exit to main menu</td></tr><tr><td>Stage Complete Screen</td><td>This screen shows up when the player successfully finishes the stage</td></tr></tbody></table>


---

# 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://october-studio.gitbook.io/monster-survivors-documentation/game-structure/game-scene.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.
