Skip to content

Properly handle block change acknowledgements in 1.18.2 -> 1.19#4093

Draft
RaphiMC wants to merge 1 commit into
masterfrom
fix/block-change-ack
Draft

Properly handle block change acknowledgements in 1.18.2 -> 1.19#4093
RaphiMC wants to merge 1 commit into
masterfrom
fix/block-change-ack

Conversation

@RaphiMC

@RaphiMC RaphiMC commented Aug 13, 2024

Copy link
Copy Markdown
Member

Recoded block change acknowledgement handling to fix block placement and block breaking lag issues.

Comparison video with 1 second simulated ping: https://upload.raphimc.net/file/0ZtebB8Se2NJrSQN/adx9mAEt2pcj7ytc/idea64_ZBLOxYOdHa.mp4
Left is with my patch and right is without my patch (Both running connected to a 1.8 server over ViaProxy)

I left the bukkit code mostly untouched. Might be worth to consider removing the bukkit code because the protocol level fix is almost perfect and the bukkit code has its own issues (#3643)

@RaphiMC RaphiMC marked this pull request as draft August 14, 2024 11:22
@RaphiMC

RaphiMC commented Aug 14, 2024

Copy link
Copy Markdown
Member Author

Not ready to merge yet. WorldGuard protected regions are no longer working on non bukkit platforms

@michaello01

Copy link
Copy Markdown

I think with these changes and commented this line

Via.getManager().getProviders().use(AckSequenceProvider.class, new BukkitAckSequenceProvider(plugin));

it works smooth and without any problems, tested on bukkit platform. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants