> For the complete documentation index, see [llms.txt](https://fish-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://fish-networking.gitbook.io/docs/guides/features/scene-management.md).

# Scene Management

## General

The [**SceneManager**](/docs/fishnet-building-blocks/components/managers/scenemanager.md) Component has many scene features to support your multiplayer needs. The links below will take you to the different guides for each feature that the [**SceneManager**](/docs/fishnet-building-blocks/components/managers/scenemanager.md) has to offer.

{% hint style="success" %}
Visit the [**API**](https://fish-networking.com/FishNet/api/api/FishNet.Managing.Scened.SceneManager.html) to see the public items exposed to the user in the SceneManager.
{% endhint %}

## Sub pages

### [Automatic Online and Offline Scenes](/docs/guides/features/scene-management/loading-scenes/automatic-online-and-offline-scenes.md)

If you simply want an online scene to be loaded when the network starts and a different one to be loaded when it stops, then you can do that with a single component.

### [Scene Events](/docs/guides/features/scene-management/scene-events.md)

"Scene Events" are the Invoked Events that happen along the loading and unloading method.

### [Scene Data](/docs/guides/features/scene-management/scene-data.md)

The Data Classes that are needed for the various features to function.

### [Loading Scenes](/docs/guides/features/scene-management/loading-scenes.md)

Information on how to "load" scenes and the options available to the user while loading.

### [Unloading Scenes](/docs/guides/features/scene-management/unloading-scenes.md)

Information on how to "unload" scenes and the options available to the user while Unloading.

### [Scene Stacking](/docs/guides/features/scene-management/scene-stacking.md)

"Scene Stacking" is the ability for server or host to load multiple instances of a scene at once, usually with different observers in each scene.

### [Scene Caching](/docs/guides/features/scene-management/scene-caching.md)

"Scene Caching" is the ability for the Server to keep a scene loaded when either all clients have unloaded that scene, or stopped observing that scene.

### [Scene Visibility](/docs/guides/features/scene-management/scene-visibility.md)

"Scene Visibility" guide offers details of using the "Scene Condition" with the [**ObserverManager**](/docs/fishnet-building-blocks/components/managers/observermanager.md), and how to manage Observers in a Scene.

### [Persisting NetworkObjects](/docs/guides/features/scene-management/persisting-networkobjects.md)

"Persisting NetworkObjects" is the ability to keep a network object's state when loading and unloading scenes.

### [Custom Scene Processors](/docs/guides/features/scene-management/custom-scene-processors.md)

Fishnet has the ability for users to create their own Custom Scene Processor for loading and unloading scenes. Using Addressables for example, would need a Custom Scene Processor created.


---

# 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://fish-networking.gitbook.io/docs/guides/features/scene-management.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.