- Fri Sep 30, 2011 10:02 pm
#34476
I have made a change to the core minecraft server file, regarding how blocks break:
Whenever a player breaks a block, the server will (should) now send a packet to the client, confirming that the block has been broken immediately. However, this is not yet saved on the server.
Separate checks are then done, and it's confirmed if the block did indeed break (if you're in a realm, etc) - if it did break, it then will drop the relevant item from that block. If not, it will send to the client to revert the change. This should remove block breaking lag (teleporting you back when you break 2+ blocks in a short amount of time), as confirmation that it was broken is sent immediately.
Let me know if you notice/find any issues.
Thanks!
Whenever a player breaks a block, the server will (should) now send a packet to the client, confirming that the block has been broken immediately. However, this is not yet saved on the server.
Separate checks are then done, and it's confirmed if the block did indeed break (if you're in a realm, etc) - if it did break, it then will drop the relevant item from that block. If not, it will send to the client to revert the change. This should remove block breaking lag (teleporting you back when you break 2+ blocks in a short amount of time), as confirmation that it was broken is sent immediately.
Let me know if you notice/find any issues.
Thanks!
"When you do things right, people won't be sure you've done anything at all."