07-16-2018, 07:04 AM
To answer your question about prediction:
The server has the final say, although the vanilla implementation may not check everything the client sends to it (hence flyhack, etc.). The client does some prediction, mainly to smooth out animations. Things like projectiles (arrows, dropped items), the animation of pistons moving blocks, sun/moon position, block breaking, particle effects. To maintain sync, there are various packets to update velocity, position or state, and Cuberite sends these occasionally (algorithm at https://github.com/cuberite/cuberite/blo....cpp#L1872).
Unfortunately since our physics simulation is basic at best, there's a lot of jittery movement under Cuberite because of prediction failures. We're, uh, working on that
The server has the final say, although the vanilla implementation may not check everything the client sends to it (hence flyhack, etc.). The client does some prediction, mainly to smooth out animations. Things like projectiles (arrows, dropped items), the animation of pistons moving blocks, sun/moon position, block breaking, particle effects. To maintain sync, there are various packets to update velocity, position or state, and Cuberite sends these occasionally (algorithm at https://github.com/cuberite/cuberite/blo....cpp#L1872).
Unfortunately since our physics simulation is basic at best, there's a lot of jittery movement under Cuberite because of prediction failures. We're, uh, working on that