PlayerReadyArrowEvent is fired on two different occasions
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
From the description of the docs, PlayerReadyArrowEvent is meant to be fired when a player is firing a bow and the server is choosing an arrow to use.
Observed/Actual behavior
Instead, the event is fired when the player starts charging their bow shot, AND when they fire their bow.
For reference: https://gyazo.com/69d88758ac6e1054c0cd4824d4d8f6d0
Steps/models to reproduce
- Have a plugin that listens to the event PlayerReadyArrowEvent.
- Charge your bow shot. Event gets fired.
- Shoot! Event gets fired, and so does your arrow.
Plugin and Datapack List
Plugins: ATHENA, LuckPerms, Vault
No datapacks installed.
Paper version
This server is running Paper version git-Paper-379 (MC: 1.19.3) (Implementing API version 1.19.3-R0.1-SNAPSHOT) (Git: 567ff90)
You are running the latest version
Previous version: git-Paper-371 (MC: 1.19.3)
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
Start by locating PlayerReadyArrowEvent and comparing its documented firing point with the two reproduction steps in the issue on Paper 1.19.3. Confirm the event behavior during charging and firing, then verify that the event occurs only when the server chooses an arrow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100