MultiConnectMultiConnectDocs Website home
MultiConnectSDK › Export to .NET

1. Which server should you build?

Start with a Unity server. It is the simplest path, and Build and Deploy Server handles everything. Move to .NET if you find you need what it offers.

Unity server .NET server
Setup Add components, and deploy from Unity A second project to create and maintain
Your code One project Scripts shared between two projects
Deploying One button in Unity Publish and upload, or use the CLI
Build size and memory Larger, because it includes the Unity engine Smaller, with no engine to carry
Start-up time Slower Faster, which helps on-demand servers
Build machine Needs Unity and Linux Build Support Needs only the .NET SDK
Debugging and tests Unity tools All the usual .NET tools
Unity features on the server Most of them, without graphics Only what is listed in Section 10

Benefits

Drawbacks

Choosing

Your game Build
You want to get running quickly Unity server
The server needs Unity's physics, animation or navigation Unity server
A card, board or turn-based game with simple server logic Either. .NET saves money at scale
Many short matches on on-demand servers .NET, for the faster start
The server only uses MultiConnectSDK physics .NET works well, as the Physics Guide explains