2 ms·
With a central-server game all clients agree on the game state (it's the server's state). With a peer-to-peer game you need more complicated protocols, but you
by lmm 7y ago
With a central-server game all clients agree on the game state (it's the server's state). With a peer-to-peer game you need more complicated protocols, but you still fundamentally end up with all clients agreeing on the game state.
Suppose Player A in San Francisco and Player B in London see each other on their screens and both click the shoot button. Neither of them can know who shot first until a network roundtrip has happened between them - hell, if their timing was precise enough then under relativity it might be physically impossible to categorically state that one was before or after the other. So either each sees (on their own screen) that they have shot first and this is later contradicted for one of them, or neither of them sees their shot being made until after the network roundtrip has happened. That choice and that tradeoff has to be made, and I don't see that cloud gaming makes any difference: either you have latency for everything you do (and whether that latency is between a thin client communicating with the game server or a thick client communicating with another thick client is really neither here nor there), or you will see inconsistencies.