3. Test your game locally
Last updated
Was this helpful?
SDK 1.6
Last updated
Was this helpful?
Now we can build the project and try out network replication locally. To do so, we need to launch and connect to a .
You can run a local Replication Server directly on your machine! You can either:
Go to: coherence > Local Replication Server > Run for Rooms or Run for Worlds
In the Hub, open the Replication Server tab. From here, you can run a server for Rooms or Worlds:
Regardless of how you launch it, a new terminal window will open and display the running Replication Server:
If the console opens correctly and you don't see an error line (they show up in red), it means your Replication Server is running! Now you should be able to connect to it, in the game.
It is often useful to be able to run multiple instances of your game on the same device. This allows you to simulate multiple player connections.
There are multiple ways to do this:
Dive into the individual pages to see our recommendation for each option.
With the game and the RS running, you can now connect and play the game.
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.
Time to bake!
In this section, we:
Ran a local Replication Server
Saw how to run multiple instances of the game
Connected to the Replication Server
Whether you run a Replication Server for Rooms or for Worlds depends on , which in turn requires the correct corresponding .
of the game
Use the package (recommended, only available in Unity 6)
Use a third-party plugin, such as
Connecting is done using our API. For now, use one of the Sample UIs we provide. You should already have one in the scene if you followed the steps in the section.
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:
Now that we know things work locally, it's time to !
