PaperMC / PaperMC/Paper

[26.3]PlayerArmSwingEvent incorrectly triggers deprecated warning for PlayerAnimationEvent

Open
#14,277 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Expected behavior

Registering a PlayerArmSwingEvent should not trigger a warning about PlayerAnimationEvent due to its deprecated parent class.

Observed/Actual behavior

I created a minimal test plugin containing only this event handler, and it still triggers the deprecated event warning.

@EventHandler
public void onArmSwing(PlayerArmSwingEvent event) {
    getLogger().info(
        "PlayerArmSwingEvent successfully triggered by "
        + event.getPlayer().getName()
    );
}
[15:32:21 WARN]: [PaperEventTest] "PaperEventTest v1.0.0" has registered a listener for org.bukkit.event.player.PlayerAnimationEvent on method "public void test.EventTestPlugin.onArmSwing(io.papermc.paper.event.player.PlayerArmSwingEvent)", but the event is Deprecated. "Server performance will be affected"; please notify the authors [].
Steps/models to reproduce

1.Create a plugin containing the method above, or use any plugin that listens for the PlayerArmSwingEvent.
2.The deprecated event warning appears.

Plugin and Datapack List
> datapack list
[15:48:12 INFO]: System chat: There are 2 data pack(s) enabled: [vanilla (built-in)], [paper (built-in)]
[15:48:12 INFO]: System chat: There are no more data packs available
> plugins
[15:48:24 INFO]: ℹ Server Plugins (1):
[15:48:24 INFO]: Bukkit Plugins:
[15:48:24 INFO]:  - PaperEventTest
Paper version
> version
[15:48:43 INFO]: Checking version, please wait...
[15:48:43 INFO]: This server is running Paper version 26.3-19-dev/26.3@b4c7d16 (2026-09-18T20:29:40Z) (Implementing API version 26.3.build.19-alpha)
You are running the latest version
Previous version: 26.3-rc-3-1-2307f8f (MC: 26.3 Release Candidate 3)
Other

No response

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

Start with the minimal plugin and the onArmSwing(PlayerArmSwingEvent event) handler shown in the issue, then reproduce the deprecated-event warning during listener registration. Trace the event registration and deprecation-warning entry point involved in PlayerArmSwingEvent and its parent PlayerAnimationEvent. Done means registering only PlayerArmSwingEvent no longer emits the PlayerAnimationEvent deprecation warning.

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
Active
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.