> For the complete documentation index, see [llms.txt](https://rocket-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://rocket-networking.gitbook.io/docs/basics-of-rocket-networking/persistent-objects-on-the-server.md).

# Persistent Objects on the Server

So far we have seen 2 important concepts

1. State Sharing in Rooms
2. Sending a Single Message to a Client

Now let's talk about Persistent Objects. These are special objects that are stored on the server and do not 'belong' to any client like entities. They can be created room wise.

Anyone can Create, Edit, Delete these special objects because no one Client 'owns' it.

For example there is a ball on the server.\
Some client can join, move it around and leave.\
Then another client can join and move it starting from the same place the previous client left it.


---

# 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://rocket-networking.gitbook.io/docs/basics-of-rocket-networking/persistent-objects-on-the-server.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.