Multiplay by Rocket Science - Onboarding
Last updated: April 28, 2026
This document details the required steps to onboard to the Multiplay by Rocket Science platform.
Once you’ve engaged with our Live Ops team to inform them of your chosen Fleet, they will let you know when everything is in place to begin end-to-end testing.
To ensure your onboarding is as smooth as possible, our engineering teams have completed the following:
Data Importer: We’ve built a dedicated tool that will seamlessly port your existing configurations directly from Unity.
Unity Validated Testing: To ensure a secure and successful transition, we have rigorously tested and validated our migration pathways alongside Unity.
We have segmented our step-by-step documentation to align with your specific architecture, depending on which matchmaker, API, SDK or CLI tool you're utilising.
Multiplay CLI
If you're currently using the Multiplay CLI tool, please download the Rocket Science version of this tool.
You can find our documentation on using this tool on our documentation site
Unity v2 Matchmaker
If you're currently using the Unity v2 Matchmaker you will need to first update to using the latest v3 Matchmaker. Please work with your Unity account team to facilitate this move.
Once this has been completed you will be able to move on to the next steps below.
Unity v3 Matchmaker
For a step-by-step guide on the required changes for integrating the Unity Matchmaker service with Multiplay, please review the Rocket Science documentation here:
📄 Unity Matchmaker (Cloud Code) Integration Guide.
Unity Matchmaker Backfill Integration Guide for Multiplay
Unity and Unreal SDKs
These SDKs provide functionality that obtains latency to a number of QoS servers hosted by Unity. If you're using these, this functionality will continue to work following March 31st, when Unity will be ending their support for the platform.
Whilst it is Unity's intention to keep this service running, the number of supported locations will be reduced. This will result in a less optimal regional selection for your players.
Our recommendation is to update your SDKs to the Rocket Science SDKs at your earliest convenience:
Clanforge API (multiplay.com or multiplay.co.uk endpoints)
If you've been utilising the Clanforge API, please take note of the following steps:
Update all API calls to point to multiplay.dev instead
Production‑side fleet setup
Your fleets will be created in our production environment.
We will test that server scaling functionality behaves as expected.
Please note: Reference documentation for the API can be found at https://docs.multiplay.dev
End‑to‑end matchmaking flow
We will then verify that a player request results in:
A server allocation on one of our machines.
Successful client connection and gameplay.
Unity API (services.unity.com endpoints)
As mentioned, if you have your own matchmaking solution, please take note of the following steps:
Endpoints to be correctly amended
You should update all Unity API endpoints (services.api.unity.com) to point at the new Rocket Science API endpoints, which will be at multiplay.dev
Basic fleet import and auth work
We’ll validate your server binaries start without error.
You'll need to inform our team of fleet details and email addresses for users to access our platform.
Capacity and allocation on the test machine
A single GCP Cloud machine (in an agreed region) will be created on your migrated fleet with several game servers which can be allocated.
We'll work with you to verify that the flow from matchmaker to successful client connection works as expected.
Initial functionality testing
We will check and verify that logs/metrics show traffic hitting the correct fleets/machines and that we see no incorrect routing.
If the above is successful and there are multiple fleets, we will check that each fleet that’s been set up can successfully allocate servers.
As always, if you have any questions or need help with the above, please reach out to our team in Slack who will be more than happy to help.