Game Concepts for Server Side Game Developers
Game concepts on the server are the loop and data that drive a simulation. A game loop repeatedly processes input, updates state and sends results, usually at a fixed tick rate such as 30 or 60 per second, and the server's job is to keep one consistent game state for all players.
Stage: Foundations · Part of the Server Side Game Developer roadmap · Last reviewed 19 November 2026
What to learn in Game Concepts
- Implement a fixed timestep loop that avoids drift
- Choose a tick rate and explain its CPU and bandwidth cost
- Represent game state so it can be copied or serialised
- Process queued player inputs in order on each tick
- Separate simulation logic from network code
- Detect and log ticks that take too long
Game Concepts interview questions
What is a fixed timestep and why use it?
A fixed timestep advances the simulation in equal slices of time regardless of how long frames take. It makes physics and logic deterministic and stable, and lets the server catch up by running extra steps when it falls behind.
How does tick rate affect a game server?
A higher tick rate gives more frequent updates and finer responsiveness, but raises CPU use and bandwidth per player. The right value depends on the genre, and servers may send updates less often than they simulate.
Where Game Concepts fits in the Server Side Game Developer roadmap
Game Concepts belongs to the Foundations stage (beginner level), which takes about 6 hours. Language, networking and game concepts.
Other units in this stage
Back to the full Server Side Game Developer roadmap