Cross-Platform Dedicated Game Server
C++ · Libuv · UDP · Flecs ECS · Jolt Physics · CMake · Unreal Engine
- Target capacity
- 300 players / instance
- Platforms
- Windows + Linux
- Client bridge
- Unreal Engine plugin
Problem
Unreal Engine’s built-in server model was not going to carry the target: 300 players per instance, on both Windows and Linux, with state that behaves the same on either. The server needed to be its own system rather than an extension of the client.
Constraint
A dedicated server has to be deterministic, cross-platform, and connected back to an Unreal client without leaking engine assumptions into the server build. Build tooling, session lifecycle, and state sync are not glamorous — but if any of them are wrong, nothing else matters.
Decision
I designed a standalone C++ server around a multi-threaded, message-driven architecture:
- Libuv + UDP with a custom reliability layer for transport.
- Flecs ECS for game state and logic organization.
- Jolt Physics for simulation.
- CMake for cross-platform builds.
A separate Unreal Engine plugin bridges client and server: session lifecycle, state sync, and build tooling. The plugin is the contract surface — the server itself does not depend on Unreal.
Verification
The cross-platform build was exercised on both Windows and Linux targets. Client-server integration was verified through the plugin’s session and state-sync path, so the engine side sees a consistent view regardless of which platform hosts the instance.
Result
A cross-platform dedicated server targeting 300 players per instance, plus the Unreal plugin that makes it usable from the client.
The transferable lesson: owning the server meant owning the boring parts — build tooling, session lifecycle, state sync. That is where cross-platform actually lives.