> For the complete documentation index, see [llms.txt](https://docs.coherence.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coherence.io/2.3/manual/networking-state-changes/lifetime.md).

# Lifetime

### Session-based vs persistent

When a Client connects, the traditional approach is that all Entities originating on this Client are session-based. This means that when the Client disconnects, they will disappear from the network for all players.

When entities are configured as persistent, they will remain on the Replication Server instead, even when the Client or Simulator that created or last simulated it is gone.

Common examples of persistent objects could be:

* A door anyone can open, close or lock
* User-generated or user-configured objects left in the world to be found by others
* Game progress objects (e.g. in PvE games)
* Voice or video messages left by users
* NPC's wandering around the world using an AI logic
* Player characters on "auto pilot" that continue affecting the world when the player is offline
* And many, many more

A persistent object that is not *adopted* by any Client is called *an orphan.* Orphans can be configured to be auto-adopted by Clients or Simulators on a FCFS basis.

<figure><img src="/files/ww4nawRIvRKoOse6Whbo" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Persistence in this context refers to **session persistence only**. This means that players can leave the game, come back, and still find persistent objects and entities, as long as the World or Room is still alive.

However, as soon as a World or Room are being shut down, or the Replication Server is restarted, the state is lost.
{% endhint %}

{% hint style="warning" %}
Currently, the maximum number of persistent objects supported by the Replication Server is **32000**.
{% endhint %}


---

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

```
GET https://docs.coherence.io/2.3/manual/networking-state-changes/lifetime.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.