PaperMC / PaperMC/Paper

[API Bug] Cancelling `EntityPushedByEntityAttackEvent` does not stop entities from Wind Burst explosions from being knocked back

Open
#13,079 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

status: accepted version: 1.21.8
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior

When a player uses a mace enchanted with Wind Burst in a group of entities, causing an explosion, and the EntityPushedByEntityAttackEvent is called for each entity, cancelling it should stop the entities from being knocked back.

Observed/Actual behavior

When a player uses a mace enchanted with Wind Burst in a group of entities, causing an explosion, and the EntityPushedByEntityAttackEvent is called for each entity, cancelling it does not stop the entities from being knocked back.

Steps/models to reproduce
  1. Set up a plugin with a listener for EntityPushedByEntityAttackEvent which cancels it
  2. Get a mace and enchant it with Wind Burst 3
  3. Set up a group of mobs all near each other
  4. Fall from a few blocks, and hit one of the mobs on the way down, causing a Wind Burst explosion
  5. Observe as the entities get knocked back, despite the event being cancelled
Plugin and Datapack List

Only the plugin with the EntityPushedByEntityAttackEvent listener.

Paper version

[16:39:28 INFO]: Checking version, please wait...
[16:39:28 INFO]: This server is running Paper version 1.21.8-60-main@29c8822 (2025-09-06T21:49:13Z) (Implementing API version 1.21.8-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21.8-29-3d1425f (MC: 1.21.8)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Use EntityPushedByEntityAttackEvent dispatch and the Wind Burst explosion behavior as the entry points; the issue names no files or tests, so locate where explosion knockback is applied after the event is called. Reproduce with a cancelling listener and a Wind Burst 3 mace, then verify that cancelling prevents every affected entity from being knocked back.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.