Log stripping is mistakenly considered as a place action
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
No block place event shall be dispatched when stripping a log.
Observed/Actual behavior
A block place event is dispatched when stripping a log.
Steps/models to reproduce
A minimal plugin reproducing the issue is available here.
Plugin and Datapack List
Plugins:
[23:59:57 INFO]: ℹ Server Plugins (1):
[23:59:57 INFO]: Paper Plugins:
[23:59:57 INFO]: - MinimalPlugin
Datapacks:
[00:00:22 INFO]: There are 3 data pack(s) enabled: [vanilla (built-in)], [file/bukkit (world)], [paper (built-in)]
[00:00:22 INFO]: There are no more data packs available
Paper version
[23:36:48 INFO]: This server is running Paper version 1.21.4-207-main@1a7288a (2025-03-09T18:15:59Z) (Implementing API version 1.21.4-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21.4-117-a35cfe9 (MC: 1.21.4)
Other
This unexpected behavior caused my plugin to put unwanted tags (more details here).
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
Start by running the minimal plugin reproduction linked in the issue and observe the block place event produced by stripping a log. Trace the server's block-interaction and event-dispatch entry points to identify why log stripping is classified as placement. Done means stripping a log dispatches no block place event while normal placement still does.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100