Movement

[LEPA4]

• Client-Side Input
• Server-Side Calculation
• Packet-Player Updating

[LEPA4]

How should movement be managed?

Maybe have the client manage if the player can move somewhere and then send it to the server to beam it out to the others. ->
Pros: The client runs smoothly, simple to implement
Cons: Hacking, less equal in updating

Some form of representation of the map (and items on it) on the server side and manage position there and the updating of it. ->
Pros: Everyone updates the exact same, less hackable, more functionality can be tied to it
Cons: Complex, slower for the clients to update (and more memory required on the server)

[darkninja1]

Bro no ones gonna try hacking also who cares about their movement It's all about the shots those need to go through server

[darkninja1]

on second thought if we want restricted areas we will need this

[darkninja1]

server map works best

[LEPA4]

It's a little more complicated than that... and it's not only about hacking, but also collisions in general... and also glitches as the server will be able to prevent people from glitching into an object.

[LEPA4]

Solution: We use another Godot project to be the server so that we can simulate where everything is (very basic visuals to save space)...

This is why server meshing is important for large-scale games because the processing power it would take to simulate a huge planet is fairly difficult.

[LEPA4]

The server updates at a fixed rate (i.e runs a constant 30 frames per second) to avoid those with higher fps from gaining an advantage (it may increase process time)