An online game feels like one shared world, but it is really many separate machines agreeing on what happened. Before you write any game server code, you need a clear picture of how that agreement works. This module covers the big ideas behind netcode, the networking code that keeps a multiplayer match consistent for every player.
You'll start with the two main network models, client-server and peer-to-peer, and why most competitive games use dedicated servers. Then you'll look at tick rate, the clock that decides how often a server updates the game world. After that you'll see how a real game, Overwatch, uses an authoritative simulation to stay responsive and accurate, and finish by connecting a game client to a server yourself.
With the shape of an online game in mind, you'll be ready for the next module, Pick a Server Language, where you choose the language you'll build your game servers with.
What you need to know about netcode: how clients and servers talk, the difference between dedicated servers and peer-to-peer, and why players feel lag.
How often a game server updates the world, why studios choose their tick rates carefully, and what it costs to run servers faster.
A look at how Overwatch runs a networked simulation that stays responsive and precise, from a Blizzard engineer at GDC.
A hands-on start to a multiplayer game in Unity: set up a server and connect clients to it.