Block data is not resent after breaking a block damage cancelled block
Open
Nobody has claimed this yet.
status: accepted
type: bug
version: 1.20.6
version: 1.21.7
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
Block data should be sent
Observed/Actual behavior
Block data is not being sent
Steps/models to reproduce
cancel block damage event
break a skull for example
Plugin and Datapack List
not important
Paper version
Paper version 1.20.6-86-master@9bf4855 (2024-05-20T18:22:30Z) (Implementing API version 1.20.6-R0.1-SNAPSHOT)
Other
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Reproduce on Paper 1.20.6 by cancelling block damage and breaking a skull, then trace the block-data sending path; done when block data is sent after the cancelled damage event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100