> 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/1.2.4/getting-started/setup-a-project/local-development.md).

# Local development

Now we can build the project and try out network replication locally. This example will show you how to launch a local [Replication Server](/1.2.4/manual/replication-server.md) and connect multiple instances of the game to it.

## Running a Replication Server locally

You can run a local Replication Server from:

*coherence > Local Replication Server > Run for Rooms / Run for Worlds*

<img src="/files/5fqMS5WcVgMXPs0GMMAD" alt="" width="375">

As with most features found in the menu, you can find local Replication Server functionality in the *coherence Hub* as well.

Open the *Replication Servers* tab and run a Room or a World Replication Server:

<img src="/files/2BWBjVRvENWtSbqUpPke" alt="" width="375">

{% hint style="info" %}
Whether you run a Replication Server for Rooms or for Worlds depends on [which setup you plan to use](/1.2.4/manual/replication-server/rooms-and-worlds.md), which in turn requires the correct corresponding [Sample UI](/1.2.4/getting-started/setup-a-project/samples-connection-uis.md).
{% endhint %}

Regardless of how you launch it, a new terminal window will open and display the running Replication Server:

<img src="/files/ewgMyNuSx6DrhBmw1f3a" alt="The Replication Server runnning in the terminal" width="375">

{% hint style="success" %}
Done! If the terminal opens correctly and you don't see an error line, it means your Replication Server is running! Now you should be able to connect in the game.
{% endhint %}

{% hint style="warning" %}
**If you can't connect**

Did you change something in the configuration of your connected Prefabs? You have to bake again, and restart the Replication Server.

You will notice it because there will be a little chef's hat next to the coherence folder, or a warning sign on Bake buttons.\
\ <img src="/files/AAffTiDtI7enhQJqOXJ5" alt="" data-size="original"><img src="/files/Jfuo23JOsEMLFnWo5EHG" alt="" data-size="original">\
\
Time to bake!
{% endhint %}

## Testing the Game

* [Using Player Builds](/1.2.4/getting-started/setup-a-project/local-development/local-testing-using-builds.md)
* [Using MPPM](/1.2.4/getting-started/setup-a-project/local-development/multiplayer-play-mode.md)
* [Using ParrelSync](/1.2.4/getting-started/setup-a-project/local-development/local-testing-via-parrelsync.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 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/1.2.4/getting-started/setup-a-project/local-development.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.