Day 210: Dedicated Server Tests
The next major development topic was largely invisible during play: multiplayer networking. Using Unreal Engine 4, the team began building a client-and-server model in which the server controlled the shared world.
One shared version of the world
The server’s role was to update connected clients and make important gameplay decisions. Each client maintained an approximation of that server world. The development note used a simple rule to explain the design: a player’s movement and death happened on the server, rather than being accepted solely because a local machine reported them.
Following a shot through the network
Pressing the fire button sent an action to the server. The server then performed the necessary checks and calculations, created a bullet at the weapon’s muzzle in its firing direction, and broadcast the result to the clients. The description explains the intended flow of a firing action; the surviving text does not provide latency measurements or detailed test results.
Why authority mattered
The stated goal was to reduce cheating in multiplayer. Letting one shared authority decide important outcomes was central to that approach. The entry calls this authoritative mode. It records the team’s networking direction, without establishing that every possible exploit had been prevented. The next entry turns to safe houses and window defenses, another system whose state would matter to everyone in the city.
Historical source: p-425-lang-en-us.md. Independently edited from the surviving development notes; missing media is not reproduced.
Return to the development timeline