EntityExplodeEvent javadoc confusing in wind charge cases
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
The EntityExplodeEvent javadoc states:
The event isn't called if the GameRules.MOB_GRIEFING is disabled as no block interaction will occur.
This comment should likely be edited as it's confusing.
Observed/Actual behavior
This isn't accurate, because at least for Wind Charges, the event does fire and the explosion result is trigger_block.
Steps/models to reproduce
N/A
Plugin and Datapack List
LuckPerms, NBTAPI, prism, WorldEdit
[vanilla (built-in)], [file/bukkit (world)], [paper (built-in)]
Paper version
Paper version 1.21.11-53-main@b6b53a6 (2025-12-23T16:13:14Z) (Implementing API version 1.21.11-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
Locate the EntityExplodeEvent javadoc in the Paper API and review the statement about GameRules.MOB_GRIEFING against the reported Wind Charge behavior, where the event fires with trigger_block. Clarify the comment without asserting that the event never fires, then verify the updated API documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100