VehicleDestroyEvent fire aspect issue
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
A player destroying a boat with a fire aspect weapon should still show the attacker as the player
Observed/Actual behavior
If you destroy a boat with a fire aspect weapon, the e.getAttacker() in the VehicleDestroyEvent is null. This makes it impossible to get the player from this event if they use fire aspect
Steps/models to reproduce
- Destroy boat with fire aspect weapon
- See how the e.getAttacker() is null
Plugin and Datapack List
N/A
Paper version
This server is running Paper version 1.21.1-132-ver/1.21.1@b48403b (2024-11-21T10:14:27Z) (Implementing API version 1.21.1-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21.1-DEV-164e116 (MC: 1.21.1)
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
Reproduce the issue on Paper 1.21.1-132 by destroying a boat with a fire aspect weapon and inspect the VehicleDestroyEvent handling, especially e.getAttacker(). Trace how the attacker is assigned for this case; done means the event reports the player rather than null.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100