> For the complete documentation index, see [llms.txt](https://docs.sparkframework.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sparkframework.dev/documentation/user-guide/core-systems/scenes.md).

# Scenes

The Scenes plugin manages scene loading and transitions. It provides a structured way to define game scenes as database entries and handle loading between them.

## Scene Entries

Create scenes in the Spark Editor under the **Scenes** tab. Each **Scene Entry** represents a game scene (level, area, town, dungeon, etc.).

Scene entries store:

* **Display Name**: The area name shown to players.
* **Description**: Description of the area.
* **Icon**: A loading screen image or map icon.
* **Scene Reference**: The actual Unity scene file this entry points to.

By defining scenes as database entries, other systems can reference them by ID. Quest objectives can require visiting a specific area. Triggers can teleport the player to a scene. NPCs can offer travel to different locations.

## Scene Management

The Scenes plugin handles:

* Loading scenes with transitions
* Passing data between scenes (which spawn point to use, etc.)
* Loading screen management

## Using Scenes

Scenes are referenced by their entry ID in triggers, quests, and other systems. For example:

* A trigger that teleports the player: references a scene entry ID.
* A quest objective: "Visit the Iron Mines" references the Iron Mines scene entry.
* An NPC travel option: "Travel to the Capital" loads the Capital scene.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sparkframework.dev/documentation/user-guide/core-systems/scenes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.