> 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/convert-a-single-player-game.md).

# Convert a single-player game

A single-player game that already runs in Play mode still makes every decision on that one machine. Multiplayer means the server owns the shared results, and each player gets a character they control. The rules are on [How multiplayer works](https://studio-docs.sandbox.game/multiplayer/how-multiplayer-works.md).

Work through the steps in order. Each one links to the page that has the detail.

## Step 1: List what every player must agree on

Write down the results that cannot differ between clients. Typical ones are:

* Damage and health
* Score
* Pickups and inventory
* Objective progress
* Enemy actions
* How the match ends

Anything on that list moves to the server. A local-only effect, such as a camera shake, can stay on the client.

## Step 2: Add the match scene and the spawn path

The level needs a `GameMode`, a `PlayerSpawner`, and at least one `PlayerStart`. A single-player game that creates its character in code, or drops one Pawn into the scene by hand, does not assign that character to the joining client.

Follow [Create a multiplayer game](https://studio-docs.sandbox.game/multiplayer/create-a-multiplayer-game.md).

## Step 3: Replace the movement

Use `MovementPawn` and the supported movement node. Predict on the owning client, and let the server correct. Keep `NetPredictionManager` starting in `onBeforeBeginPlay` when props need rewind.

Follow [Networked movement](https://studio-docs.sandbox.game/multiplayer/networked-movement.md).

## Step 4: Move the rules onto the server

Player actions go through a server RPC. Lasting values, including the ones from Step 1, are replicated properties. The client sends the request. The server decides the result.

Follow [Share state and actions](https://studio-docs.sandbox.game/multiplayer/share-state-and-actions.md).

Projectiles, enemies, and other objects created during play go through `MultiplayerSpawner`. An object added with a normal scene add stays on the machine that created it.

## Step 5: Add matchmaking and the server scene

Published players enter through a supported queue. In **Project Settings**, set **Server Default Scene** to the gameplay scene before you upload. A multiplayer upload is blocked until that scene is set.

Follow [Add matchmaking](https://studio-docs.sandbox.game/multiplayer/add-matchmaking.md), then [Publish a multiplayer game](https://studio-docs.sandbox.game/multiplayer/publish-a-multiplayer-game.md).

## Step 6: Test with two clients, then with an upload

Run at least two clients in Play mode and check ownership, movement, and the shared score. Then upload and play the hosted build with enough people for the queue.

Follow [Test multiplayer locally](https://studio-docs.sandbox.game/multiplayer/test-multiplayer-locally.md).

## What You've Done

The single-player rules that every player must share now run on the server, and each joining player gets their own character. The upload check is the last step on [Publish a multiplayer game](https://studio-docs.sandbox.game/multiplayer/publish-a-multiplayer-game.md).


---

# 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/convert-a-single-player-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.
