Question

I want my game to be entirely server side. Meaning, the client only sends their keystrokes. They then are given updates of the changed objects’ positions from the server. The client then renders everything each frame.

This is a 2D game

I was thinking of something like this:
calculate the inbetween frame using Box2D, and do not try to predict where the server is in fact going to be.

ServerPos -> ClientPos -> ServerPos -> …

If by a certain time we have not gotten a packet (dropped or something) then we just simulate the next frame on client. The idea is to avoid the server always correcting our position. We want the client to fill the inbetweens but not try to predict where the server is going to be.

We want to avoid at all costs moving the player in the opposite direction because the client over simulated, so we could multiply the resultant vector by a scalar like 0.98 which would mean the client would be slightly slower than the server and would help ensure a smooth transition to the server position.

Thanks

Answer 1

Just a thought, but I think you might be forgetting network latency.

Assuming you’re really sending the data 60 times per second in response to something the client sends. Than your maximum latency can be 1 second / 60 = 17ms. That will be a problem for just about any internet connection since your application is bound to introduce some latency aswell. So… if you want something like this to work, you’ll have to have a little buffer window to catch this delay. And that will make it feel less responsive.

There’s a reason that most online games have some prediction algorithms in place just in case the connection drops/stalls a bit.

I think the idea is nice, but in practice it probably won’t work that well.