89cbe03ebe
The host ignored ServerboundPunchPacket, so a guest mining or hitting swung only on its own screen; only the first swing a guest's use ever started went out, the host's own swings never did, the host drew no swing on guests' bodies and a guest's client ignored ClientboundSwingAnimationPacket. The host now swings the guest's hand on a punch (handlePunch), sends each tick's guest swings to the players around and the host's own to the guests, and swings and ticks the guests' bodies it draws. A use the server ran that swung goes back to the guest too: Horizon's client does not run uses itself, so it never predicted that swing (the hoe). The guest's client swings itself or the other entity on the packet. lan_e2e.py swings: mining swings seen from each side, and the guest's own hoe swing. Part of #848 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>