|Part of a series on|
|Internet hosting service|
|Application-specific web hosting|
|By content format|
A game server (sometimes host or shard) is a server which is the authoritative source of events in a multiplayer video game. The server transmits enough data about its internal state to allow its connected clients to maintain their own accurate version of the game world for display to players. They also receive and process each player's input.
Dedicated servers simulate game worlds without supporting direct input or output, except that required for their administration. Players must connect to the server with separate client programs in order to see and interact with the game.
The foremost advantage of dedicated servers is their suitability for hosting in professional data centers, with all of the reliability and performance benefits that entails. Remote hosting also eliminates the low-latency advantage that would otherwise be held by any player who hosts and connects to a server from the same machine or local network.
Dedicated servers cost money to run, however. Cost are sometimes met by a game's developers (particularly on consoles) and sometimes by clan groups, but in either case, the public is reliant on third parties providing servers to connect to. For this reason, most games which use dedicated servers also provide listen server support.
Listen servers run in the same process as a game client. They otherwise function like dedicated servers, but typically have the disadvantage of having to communicate with remote players over the residential internet connection of the hosting player. Residential connections rarely support the upload requirements of games with many players; the typical limit is 16. Performance is also reduced by the simple fact that the machine running the server is also generating an output image. Furthermore, listen servers grant anyone playing on them directly a large latency advantage over other players ("host with most") and cease to exist when that player leaves the game.
But listen servers have the advantage of being essentially free and not requiring any special infrastructure or forward planning to set up, which makes them common at LAN parties where latency and bandwidth issues are not a concern. They are also common in console games.
In the client/server model outlined elsewhere in this article, clients receive processed data from the server and display it without much thought. In the alternative "peer-to-peer" model there is no server: each "peer" instead receives the raw input streams of each other player and determines the results itself.
Peer-to-peer is generally considered obsolete for action games, but it still common in the real-time strategy genre due to its suitability for games with large numbers of tokens and small numbers of players. Instead of constantly transmitting the positions of 1000 troops, the game can make a one-off transmission of the fact that 1000 troops are selected and that the player in command of them just issued a move order.
However, peer-to-peer has many disadvantages:
- It is very difficult to keep all peers synchronised. Minute differences between peers can escalate over time to game-breaking paradoxes.
- It is very difficult to support new peers joining part-way through a game.
- Each peer must communicate with all other peers, limiting the number of connected players.
- Each peer must wait for every other peer's message before simulating the next "network frame", resulting in all players experiencing the same latency as the player with the worst connection.
The rate at which a game server runs simulation steps is commonly referred to as its "tickrate". A "tick" is a number associated with each simulation step which is broadcast to clients to help them synchronise with the server.
There are three reasons to limit the frequency of server simulation steps to a predefined tickrate: to conserve server and client bandwidth, to conserve server CPU time, and to allow clients to be certain of how much time has elapsed between each tick. The last point is important for internet games, as network updates from the server can arrive at different intervals or even an incorrect order.
Servers, particularly those of PC games, can generally be customized in ways that still allow unaltered clients to connect to them. These customizations can include tweaks to built-in game settings, content that is downloaded by clients when they join the game, and new code which changes the way that the server behaves.
While server customization is popular with server administrators and players, it can be at odds with the desire of developers and other players for the game to be experienced as intended. It can also aggravate players by enabling abusive administrators to lie about what their server offers.
- Weilbacher, Michael (March 2012). "Dedicated Servers in Gears of War 3: Scaling to Millions of Players". GDC 2012. GDC Vault.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
- Bernier, Yahn (2001). "Latency Compensating Methods in Client/Server In-game Protocol Design and Optimization". Valve Corporation. Retrieved 17 September 2011.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
- Armstrong, Andrew (2009). "The Mammoth Dedicated Server Guidebook". Mammoth Media.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
- Fiedler, Glenn (24 January 2010). "What every programmer needs to know about game networking".<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
- "Source Multiplayer Networking". Valve Developer Community. Retrieved 13 February 2013.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
- "HTTP Fast Download". Steam Support. Valve Corporation. Retrieved 5 May 2012.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
- "Server Plugins". Valve Developer Community. Valve Corporation. Retrieved 5 May 2012.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
- Bowling, Robert (21 October 2009). "Modern Warfare 2 For PC". Archived from the original on 21 October 2009.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
- Denton, Jon (July 4, 2012). "Battlefield 3: How Fan-Run Servers Are Ruining DICE's Game". Eurogamer.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
- Walker, Robin (12 March 2009). "And that's what ye git fer toochin that!". Team Fortress 2 Blog. Valve Corporation.<templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>