quote:Original post by Taulin
Any time the client is allowed to make world state changes, it leads to cheating and stabability problems, much like a peer to peer network game works, and why most people choose client-server now.

The server should do world calculations like hit detection and such to keep the game world data accurate, and send out delta info. The client should do only the amount needed for prediction (i.e. starting with QuakeWorld). Again, it is good if you can let the client do some of the work, but be carefull of cheating.




interNEKO

quote:Original post by SGreth
Do you have any reccomendations as to how much processing the client should actually do? How laggy/appropriate would it be for the clients to only report delta''s in speed and orientation and then have the server relay that info to all other clients?

quote:Original post by Taulin

quote:Original post by SGreth
Do you have any reccomendations as to how much processing the client should actually do? How laggy/appropriate would it be for the clients to only report delta''s in speed and orientation and then have the server relay that info to all other clients?

Sorry, I didn''t mean it that way. The server reports deltas TO the client. It is important that the client recieves them though, so you might consider sending whole world states ever X seconds for full sync (depending on game,and importance priority).

Think of it this way. The client''s screen is a window to the server. The client''s controls are only inputs to the server.

As I said, and Inmate confirmed, anytime the client does calculations that change the real world state, you are opened for hacks.


interNEKO