Unity Multiplayer and Backend Development
Connect players or participants in a shared Unity experience. XGameDev develops multiplayer systems and supporting services for games and applications, including sessions, synchronised state, communication and the infrastructure needed to run the agreed product.
Hubub: Unity multiplayer, Node.js and WebRTC
What multiplayer development includes
We define how participants join, what they share and which decisions the server controls. The scope can include lobbies, matchmaking, sessions, state synchronisation, reconnect behaviour, persistence, leaderboards and accounts. We work with managed platforms or custom Node.js services according to the product's requirements and operating budget. Real-time voice or video, monitoring and deployment can form part of the build. Before implementation, we agree expected usage, regions, latency tolerance and how to test disconnected or untrusted clients so the architecture matches the experience.
How your shared experience takes shape
Describe the session
Tell us who joins, what they do together, expected session sizes and the existing game or application.
Agree the architecture
We define server responsibilities, data flows, infrastructure assumptions and acceptance checks for the first working milestone.
Review connected builds
Test the agreed features across multiple clients, including relevant reconnect and interrupted-session cases.
Prepare operation
Agree deployment, monitoring, account access and running costs, then document handover and ongoing responsibilities.
Multiplayer, voice and video for Hubub
On Hubub’s Unity virtual campus, Jacques developed the Unity C# and Node.js software, worked on multiplayer and WebRTC voice and video, and handled AWS deployment. Melanie assembled levels, worked on characters and coordinated the project.
See the Hubub virtual campus projectQuestions about multiplayer delivery
Can you estimate the networking before we know the final player count?
Give us the expected session size, what players share and what needs to persist between sessions. If the networking is still uncertain, we can scope a prototype to test those assumptions before estimating the full system.
Can you extend our existing networking stack?
Yes, subject to reviewing the code, platform limits and service access. We agree which systems to retain and the boundary of our work.
Should we use a platform or custom servers?
A managed platform can suit its supported session model. Custom services may fit other requirements; we compare control, operations and running costs.
Can you guarantee capacity before testing?
Capacity depends on workload and infrastructure. Agree representative load, latency and recovery tests; hosting and third-party subscriptions remain separate operating costs.
Describe what participants need to share
Send the current stack, session size, target platforms and the behaviour you need to build or fix. Include any release deadline.