256ecc4daa
A guest's STOP_DESTROY_BLOCK cleared the digging before the host's own count was done, so a block the client broke stayed on the server and the player fell through or froze on it. The host now follows ServerPlayerGameMode: it breaks the block when its progress since START is at least 0.7 and otherwise finishes the dig alone (the delayed destroy). Block acks go out after the tick's block updates, and the client keeps predicted blocks until the server acknowledges them (BlockStatePredictionHandler), so a refused break comes back instead of being lost. Fixes #500 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>