MultiConnectSDK › Developer Guide
1. Overview
What you get
- Rooms and matchmaking: public, private, offline and spectator rooms, with automatic player matching
- Compact messages: add one attribute to a class and send it
- Reliable and unreliable delivery: choose per message; MultiConnectSDK picks the carrier for each platform
- One button to go live: build and deploy your server from inside Unity
- Analytics: players, sessions, matchmaking and your own custom events
Two ways to run your servers
| MultiConnectCloud | Your own servers | |
|---|---|---|
| Use Custom Hosting | Off | On |
| SDK key | Free key from the dashboard | Free key from the dashboard, or a key of your own |
| Analytics | Included | With the free key |
| How clients connect | By SDK key; MultiConnectCloud finds the server | By address |
| Deploys | Build and Deploy Server in Unity, or the CLI | You copy and start builds |
| Rollouts | Zero downtime, with automatic rollback | You manage them |
TLS for wss:// |
Handled for you | You supply a certificate |
| Scaling and regions | Set on the dashboard | You run the servers |
Your game code is the same either way, so you can start on one and move to the other. We recommend creating the free account either way: it takes a minute, and it gives you analytics wherever your servers run.
Supported platforms
You choose how a message is delivered; MultiConnectSDK chooses what carries it:
| Platform | McProtocol.Reliable |
McProtocol.Unreliable |
|---|---|---|
| Windows/Mac/Linux, iOS/Android | Raw TCP, or WebSocket (ws:// / wss://) |
UDP |
| WebGL | WebSocket (ws:// / wss://) |
WebRTC data channel (unordered, never resent) |
- Reliable follows the server: it listens for raw TCP or for WebSocket (Use WebSocket), never both. Use WebSocket for any game with a WebGL build.
- Unreliable needs Use UDP on server and client. A WebGL build opens its WebRTC channel automatically, on the server's same port.
- Where no unreliable path works, Unreliable sends go as Reliable (Allow Udp Fallback).

