No break block animation showing to other players. Start Break Action and Stop Break Action not being sent properly.
When players begin to break a block there is no action of this being performed to any other clients connected to the server. The only animation is of the player punching the block but there is no animation of the block in the process of being broken (the lines i.e the second screenshot).
Linked Issues
Created Issue:
No break block animation showing to other players. Start Break Action and Stop Break Action not being sent properly.
When players begin to break a block there is no action of this being performed to any other clients connected to the server. The only animation is of the player punching the block but there is no animation of the block in the process of being broken (the lines i.e the second screenshot). On closer inspection the client is not sending the “Start Break Action” in the PlayerActionPacket (0x20). And once the block is broken the “Stop Break Action” (2) gets sent in a separate PlayerActionPacket (0x20) just before another gets sent with the broken block location and face. Usually all of this is this (action id, broken block location, and face) are sent in one packet PlayerActionPacket.
When players begin to break a block there is no action of this being performed to any other clients connected to the server. The only animation is of the player punching the block but there is no animation of the block in the process of being broken (the lines i.e the second screenshot).
On closer inspection the client is not sending the “Start Break Action” in the PlayerActionPacket (0x20). And once the block is broken the “Stop Break Action” (2) gets sent in a separate PlayerActionPacket (0x20) just before another gets sent with the broken block location and face. Usually all of this is this (action id, broken block location, and face) are sent in one packet PlayerActionPacket.
duplicates


Still broken in 0.15.1 alpha build 1
Please respond and add the current version if you can reproduce this issue.
Still broken in 0.15.4 tested with 2 android devices.