> For the complete documentation index, see [llms.txt](https://dojo-project.gitbook.io/flycast-dojo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dojo-project.gitbook.io/flycast-dojo/features/replays.md).

# Replays

To see a listing of your recorded replay sessions to play back, click on the "Replays" button on the Flycast main screen.

To record your netplay sessions, just check the box that says "Record All Sessions". This will create a new replay file for each netplay session you run and will be saved in the `replays/` subdirectory.

To play the replay file, just click on the corresponding entry, and the replay data will played back in its corresponding game.

<figure><img src="https://github.com/blueminder/flycast-dojo/raw/master/replay1.png" alt=""><figcaption></figcaption></figure>

###

### Public Replay Servers & Transmitting Game Sessions

If you wish to share your game sessions, there is an option to transmit to any replay server or to any listening spectator with the **RECEIVE** option set.

There is currently an experimental public replay server available at **match.dojo.ooo**. The server accepts transmissions at port **7000**, with an interface to search and download replays at <http://match.dojo.ooo:8000/replays>.

**Transmitting to Replay Server**

<figure><img src="https://github.com/blueminder/flycast-dojo/raw/master/transmission-replay-server.png" alt=""><figcaption></figcaption></figure>

**Replay Server Search Interface**

<figure><img src="https://github.com/blueminder/flycast-dojo/raw/master/replay-server-search.png" alt=""><figcaption></figcaption></figure>

Once some code cleanup and quality checks are done, the replay server will be made available in its own repository for anyone to be able to host themselves.


---

# 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://dojo-project.gitbook.io/flycast-dojo/features/replays.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.