
Listen Server
A listen server runs the match inside one player’s game while that player also plays. Many engines call it host mode, and it is the host-client form of peer-to-peer networking. It needs no game server, so there is no server bill, though connecting players often needs a relay. In exchange, the host usually plays with no network delay, often holds authority over the match, and the match typically ends when they leave unless the game supports host migration.
Also called
host mode, player-hosted server
,
What Does “Listen Server” Mean in Unreal, Unity and Godot?
The same design goes by different names, so documentation written under one name is easy to miss when searching for the other.
Unreal Engine and Valve’s Source engine call it a listen server.
Unity netcodes usually call it the host, or host mode: Netcode for GameObjects and Mirror start one with
StartHost(), Fish-Networking starts a server and a client in the same game, and Unity’s documentation files it under “listen server host architecture” (Unity docs). Photon Fusion has a Host mode too. Its Shared mode is a different design, where authority is spread across clients.Godot doesn’t give it a name. The peer that creates the server takes ID 1, and Godot’s own example registers that peer’s player like any other (Godot docs).
Each describes one player’s game running the server and that player’s client side by side, while everyone else connects to it. It is the host-client form of peer-to-peer.
In web and backend code, “listen” means something unrelated: the call that opens a port for incoming connections.
Article's key insights
Short answer: A dedicated server holds the true game state on hardware no player controls, the model behind most competitive games. In peer-to-peer, one player’s machine usually owns the match and can alter it. A relay only forwards packets past NAT and hides IPs: it fixes connectivity, not cheating.
Authoritative Servers: one server holds the true game state and validates what every player does. When it runs on infrastructure no player controls, it's a dedicated server, the model behind most competitive games.
Relays: a relay forwards packets between players who can't connect directly. It fixes connectivity and hides IP addresses, but runs no game logic, so one player's machine still owns the match.
Peer-to-Peer: players' machines connect directly, either to one player hosting the match or to every other peer. It has no server cost, but the host can alter the game and NAT blocks some connections.
Additional Insights Covered in This Article
Two separate questions: "who owns the game state" (authority) and "whose hardware runs it" (hosting) are different choices, and a relay answers neither of them.
Relays are safer than raw P2P, not safe: the host can still alter the match, and the authoritative logic ships inside a build any player can decompile.
An extensible relay runs on your own dedicated server: players connect out to a relay the studio deploys and can extend; the host owns the match until the studio adds game logic.
Dedicated servers come in sizes: from a small dedicated server or a multi-room server up to a full simulation, each keeps authority on a machine players don't control.
Peer-to-peer fits a narrow set of games: friends-only sessions and deterministic lockstep titles, with no ranked play or economy to protect.
How Does One Game Act as Both Server and Player?
A listen-server game runs in three roles, not two: the server, a remote client, and the host, which is both at once. Code written for “server” and “client” often misses the third, and some bugs only appear there.
Unity’s Netcode for GameObjects exposes
IsHostalongsideIsServerandIsClient, for code running as both a server and a client.Unreal Engine handles replication callbacks differently by language. Epic’s documentation notes that RepNotifies “work differently in Blueprint than they do in C++”: a Blueprint
Setnode calls the RepNotify, while a C++OnRep_function is called on clients (Epic docs). In C++, the host’s own player can miss an update every other player receives, unless the code calls the function itself.
The host role also hides the network. The host’s inputs never cross one, so the host sees the game with no delay, no lost packets and no corrections. A team that playtests mostly as the host can ship rubberbanding or late hits that only remote players meet. Many engines and netcodes include network emulation for testing as a remote client with added latency and loss.
Why Does the Host’s Machine Set the Pace of the Match?
On a listen server, the server’s work runs inside the host’s game, often in the same frame loop as its rendering. When the host’s frame takes longer, because of a heavy scene, high graphics settings or another program, server updates can arrive late for every player in the match. A tick rate chosen in a project’s settings holds only as well as the host’s machine can keep up.
The host’s hardware is whatever that player owns, from a gaming PC to a phone, and on mobile the operating system decides when the game runs. Unity’s documentation notes that on Android an app in the background “pauses regardless of the Application.runInBackground option”, and that iOS “ignores this property” (Unity docs). A host who switches apps to answer a message can pause the match for everyone.
The host’s home connection carries every other player’s traffic, which peer-to-peer covers in more detail. Together, the host’s machine and connection set a ceiling the rest of the match can’t rise above.
What Changes When a Listen-Server Game Moves to Dedicated Servers?
Much of the netcode often carries over, because most engines run the same game code as a host or as a server: Unreal builds a separate server target, Unity netcodes start a server instead of a host, and Godot can export a project as a dedicated server (Godot docs). What changes sits around the host:
The host-only code goes: With no player on the server, the third role from Part 2 disappears, and so do the bugs that live only there.
Local-player assumptions come out of the server build: Camera, UI and input code that expects a player on the machine has to be kept out of a headless build.
A session starts differently: A matchmaker or server browser starts or finds a server, instead of a player pressing Host.
A player leaving no longer ends the match: No player owns the match, so host migration is no longer needed.
Where the server runs then becomes a choice. Independent replays of a AAA publisher’s live traffic measured a 58% reduction in average round-trip time with dedicated servers placed near its players, compared with public-cloud relay placement (Edgegap platform data, page updated 29 October 2026).
A word from our sponsor (ourselves!)
Most lag comes from distance, not from code. Edgegap's Edge Cloud is a distributed network with up to 615+ locations available on demand, so each match runs at the best available location for its players. Independent replays of live studio traffic measured a 58% drop in average round-trip time compared with public cloud.
Edgegap's Take (just our opinion, take it with a grain of salt!)
Run Your Listen-Server Game Through a Relay You Control, So It Can Grow Into a Dedicated Server
A listen-server game doesn’t have to choose between player hosting and a full server rewrite on day one. An extensible relay, such as LightNet for Unity netcodes, runs on a dedicated server you deploy. The host keeps hosting with the same netcode, while every player connects out to the relay, in locations you choose, with their IP addresses hidden from attacks on their connection.
From there, a game can stay on cost-effective relay hosting for modes played among friends, or add server-side logic to the relay over time, from room passwords to gameplay validation, which can turn it into a multi-room game server, and later move to full dedicated servers. Until that logic is added, the host’s game still holds the match, as with any relay.
A useful first step: list each mode by who plays in it. Modes among friends can stay on the relay. Modes where strangers meet are usually the first to give server authority.
Philip Coté, CTO
,










