7 commits

Author	SHA1	Message	Date
Jason Penilla	5513f8a795	patches ...	2023-12-05 20:00:14 -07:00
Nassim Jahnke	2a1ace0cf2	Prepare for 1.20.3 dev	2023-12-05 18:20:55 +01:00
Owen	9271ee7643	Dont resend blocks on interactions (#9413) ... In general, the client now has an acknowledgment system that will cause block changes made by the client to be reverted correctly. Essentially: The client enters a "prediction" stage, where any block changes made will have its old blockstate captured (this is referred to as "server state"). If you update blocks during this stage, the client will update this captured server state as long as they're still currently predicting. After prediction is done (via an ack packet) all captured blockstates are reverted to their captured server state. This means that if the server actually updated a block and send a block update packet, it's correctly set, while if a block wasn't updated on the server but WAS updated on the client (server state wasn't updated), that change will be reverted. It should be noted that this system does not yet support block entities, so those still need to be resynced when needed. I discovered this when noticing that blocks broken outside of the player's valid interaction distance are still properly reverted, even though the server doesn't send any block updates, only an ack packet.	2023-12-02 22:41:35 -05:00
Jake Potrebic	0cdce89d59	Fix a bunch of stuff with player spawn locations (#9887) ... If a playerdata doesn't contain a valid, loaded world, reset to the main world spawn point	2023-11-04 14:11:55 -07:00
TomTom	487109fddc	Readd 0414 use distance map to optimise entity tracker (#9868)	2023-11-03 14:05:57 +00:00
Jason Penilla	b974a6b6f3	Update paperweight to 1.5.9 (#9872)	2023-10-26 16:34:58 -07:00
Spottedleaf	84556f3cda	Add lag compensation for breaking blocks	2023-09-23 22:31:42 -07:00

Renamed from patches/server/0465-Extend-block-drop-capture-to-capture-all-items-added.patch (Browse further)