Add a dedicated event for Wind Burst effects
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
Research direction
The payload names no files. Start from the existing EntityAttemptSmashAttackEvent and EntityPushedByEntityAttackEvent in the Paper API, and check how Wind Burst's knockback is currently triggered and whether it has a player source. The design is not settled: the event's fields, whether it can cancel the whole effect, and how it relates to the existing events all need a maintainer decision first. Done means an agreed event shape, with the event firing when Wind Burst triggers and tests showing it can be cancelled.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?
When a player attacks a block-containing Sulfur Cube with a mace, the Sulfur Cube is immune to damage, so EntityDamageByEntityEvent is not triggered. However, the mace attack can still trigger Smash Attacks and the Wind Burst enchantment.
Although EntityAttemptSmashAttackEvent allows plugins to deny the Smash Attack using Result.DENY, this does not prevent the Wind Burst effect from activating.
Additionally, now Wind Burst appears to have a player source and can trigger EntityPushedByEntityAttackEvent. However, even when this event is cancelled, Wind Burst can still apply knockback to nearby entities within a limited range.
Describe the solution you'd like.
I would like Paper to introduce a dedicated EntityWindBurstEvent that is fired whenever the Wind Burst enchantment is triggered.
The event should provide:
Access to the player or entity that triggered Wind Burst.
Access to the original target of the mace attack.
Access to entities affected by the Wind Burst effect.
The ability to modify or cancel the resulting knockback.
The ability to cancel the entire Wind Burst effect, preventing it from affecting nearby entities.
This would allow protection plugins to properly identify the source of Wind Burst and enforce region protection rules consistently, without relying on indirect knockback events or temporary tracking mechanisms.
Describe alternatives you've considered.
Perhaps allowing left-click attacks against block-holding Sulfur Cubes to still trigger EntityDamageByEntityEvent could solve this issue?
Other
No response
- Dominant language
- Java
- Stars
- 12.8k
- Forks
- 3.6k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 19
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from PaperMC/Paper
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Add .getIgniter() to ExplosiveMinecartPossibly taken @WouterGritter claimed this 61 days ago. Openstatus: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PaperMC/Paper#14097 · 1 comment ·
Maintainers usually reply within 1 day
-
BlockType#isOccluding is incorrectly handledPossibly taken @ryoji-ikeda claimed this 205 days ago. Openstatus: accepted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PaperMC/Paper#13790 · 5 comments ·
Maintainers usually reply within 1 day
-
status: needs triage
Difficulty 4/5 3-5 days Newbie friendliness 43/100
PaperMC/Paper#14492 · 2 comments ·
Maintainers usually reply within 1 day
-
[Checkstyle] Ignore check for javadocs into method-local classesPossibly taken @Machine-Maker claimed this 2 days ago. Openstatus: accepted
PaperMC/Paper#14490 · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
floci-io/floci#8791 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
affects/8.10 affects/8.8 affects/8.9 area/reliability component/zeebe kind/bug likelihood/low severity/high
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
geonetwork/geonetwork#276 ·
Maintainers usually reply within 1 day