Multiplayer for Unreal Engines
Unreal multiplayer uses a server-authoritative model built into the engine. The server owns the true game state and replicates actor properties and function calls to clients. Properties are marked as replicated, and RPCs run code on the server or clients. Understanding roles, ownership and relevancy is key to avoiding desync.
Stage: Release · Part of the Unreal Engine roadmap · Last reviewed 19 November 2026
What to learn in Multiplayer
- Explain the difference between server, client and listen server setups
- Mark a variable as replicated and respond with a RepNotify function
- Write server and client RPCs and know which actor can call them
- Decide which classes exist on the server only, clients only, or both
- Test with multiple players in the editor using net mode settings
Multiplayer interview questions
Why is Unreal's networking server-authoritative?
The server holds the real game state and validates actions, which limits cheating and keeps all players consistent. Clients send requests, and the server decides outcomes and replicates the results back, so clients do not trust their own state.
Where does the GameMode exist in a multiplayer game?
GameMode exists only on the server, so clients cannot read it. Data that clients need, such as scores or match state, should live in GameState or PlayerState, which replicate to everyone.
Where Multiplayer fits in the Unreal Engine roadmap
Multiplayer belongs to the Release stage (advanced level). Polish and ship.
Other units in this stage
Back to the full Unreal Engine roadmap