> For the complete documentation index, see [llms.txt](https://studio-docs.sandbox.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio-docs.sandbox.game/multiplayer/publish-a-multiplayer-game.md).

# Publish a multiplayer game

A multiplayer upload uses the same panel as [Uploading Your Project](https://studio-docs.sandbox.game/publishing/uploading-your-project.md). Two extra things have to be true first: the dedicated server has a scene, and the upload is packaged for online play. Turning the game on in `Edit Game` is a later step, on [How to Publish](https://studio-docs.sandbox.game/publishing/how-to-publish.md). That listing switch does not start a multiplayer server.

Local Play mode is not this test. The **Multiplayer** checkbox next to Play only affects that local session. Run it first, on [Test multiplayer locally](https://studio-docs.sandbox.game/multiplayer/test-multiplayer-locally.md). The cloud game has its own **Multiplayer** switch.

## Step 1: Confirm the server scene

In **Project Settings**, set **Server Default Scene** to the scene the dedicated server loads. Set it even when that scene is the same map the game already loads. The project stores the choice as `defaultServerScene`. Save with `Ctrl+S` / `Cmd+S`.

A multiplayer upload is blocked until that scene is set. The Upload dialog names the problem and opens Project Settings. The checks are on [Create a multiplayer game](https://studio-docs.sandbox.game/multiplayer/create-a-multiplayer-game.md).

## Step 2: Package the upload for online play

The cloud game has a **Multiplayer** switch, described as **Package uploads to play online**. Turn it on and save it before you upload.

Turning the switch on does not upload the project, and it does not validate the project. The next upload is the one that gets packaged.

## Step 3: Upload the project

In the editor title bar, or the app menu, choose **Upload Project**. If the project is not linked to a cloud game yet, create or select one. The project stores that game id. The panel is the one on [Uploading Your Project](https://studio-docs.sandbox.game/publishing/uploading-your-project.md).

Stay until the transfer finishes. Every upload is checked. When **Multiplayer** is on, a build that passes is also packaged as a server version, so the game can play online. Validation usually takes a few minutes.

You can produce the build from the project directory with the SDK CLI (`genesys-sdk build`, or `genesys-sdk build -p <project>`). Publishing for online play still goes through **Upload Project** with **Multiplayer** enabled, so the platform can package the server version.

## Step 4: Read the status on the game card

The same status appears on the game card in the dashboard and in the **Upload Project** button tooltip in the editor title bar. The tooltip opens for a few seconds when the status changes.

| Status                    | What it means                                                                                                               |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| `Multiplayer: preparing…` | Validation is still running                                                                                                 |
| `Multiplayer ready`       | The build passed and a server version is available. If a version is already live, the tooltip names the version players get |
| `Multiplayer rejected`    | The latest build failed validation. The tooltip includes the reason. A previous live version stays up                       |
| `Multiplayer: try again`  | Validation failed on the platform side. Upload again to retry                                                               |

`Multiplayer ready` means the server build passed preparation. It does not mean a match has been played. A rejected build can still have a game page. Fix the reported issue, upload again, and wait until the badge reads **Multiplayer ready**. A rejected upload leaves the previous ready build in place.

## Step 5: Play the uploaded build

Open the uploaded game with enough people for the queue you chose. The queue sizes are on [Create a multiplayer game](https://studio-docs.sandbox.game/multiplayer/create-a-multiplayer-game.md).

Confirm each of these:

1. The game loads from the uploaded build.
2. A player can enter matchmaking and the queue returns a match.
3. The hosted server accepts the connection.
4. Each player spawns in their own character.
5. The shared score updates for everyone.
6. Everyone is on a client and server build that can talk to each other. A protocol or schema mismatch closes the connection (`protocol-version-mismatch` or `schema-hash-mismatch`).

{% hint style="info" %}
*NOTE: `Published` in Edit Game lists the game for discovery. It is not the multiplayer status. A build can be `Multiplayer ready` and still be unpublished.*
{% endhint %}

## What You've Done

The project has a server scene, an online package, and an upload you can join through matchmaking. Listing it publicly is on [How to Publish](https://studio-docs.sandbox.game/publishing/how-to-publish.md).

*The Multiplayer switch and the game card statuses were checked on 16 October 2026.*


---

# 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://studio-docs.sandbox.game/multiplayer/publish-a-multiplayer-game.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.
