`PlayerAttackEntityCooldownResetEvent` cancellation is non-functional

[TheBentoBox]

Expected behavior

Canceling PlayerAttackEntityCooldownResetEvent should prevent the player's attack cooldown from resetting, meaning they should be able to immediately attack again at full power.

Observed/Actual behavior

Canceling this event doesn't do anything. The player's attack cooldown still resets.

Example with listeners for the damage in a damage event and PlayerAttackEntityCooldownResetEvent, hitting twice quickly with a Sharpness V netherite sword.

Corroborated by Barty from the PaperMC Discord who did his own testing.

Steps/models to reproduce

1. Register a listener for PlayerAttackEntityCooldownResetEvent which always cancels the event.
2. Strike an entity twice rapidly. The second hit will do reduced damage when it shouldn't.

Plugin and Datapack List

Tested on a minimal reproduction server. Used Skript with skript-reflect for ease of logging.

> plugins
[20:32:20 INFO]: ℹ Server Plugins (2):
[20:32:20 INFO]: Bukkit Plugins:
[20:32:20 INFO]:  - Skript, skript-reflect
> datapack list
[20:32:21 INFO]: There are 3 data pack(s) enabled: [vanilla (built-in)], [file/bukkit (world)], [paper (built-in)]
[20:32:21 INFO]: There are no more data packs available

Paper version

> version
[20:33:03 INFO]: Checking version, please wait...
[20:33:03 INFO]: This server is running Paper version 1.21.11-99-main@81b9122 (2026-01-20T19:08:30Z) (Implementing API version 1.21.11-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21.5-2429-9d0aa8e (MC: 1.21.5)

Other

Here's a minimal script that relies on just Skript and skript-reflect should that be your cup of tea.

import:
    com.destroystokyo.paper.event.player.PlayerAttackEntityCooldownResetEvent

on damage of living entity by player:
    broadcast "Damage: %final damage% hearts"

on PlayerAttackEntityCooldownResetEvent:
    event.setCancelled(true)
    event.getAttackedEntity().setNoDamageTicks(0)

[Doc94]

I check and the event avoid reset the internal value used also in https://jd.papermc.io/paper/1.21.11/org/bukkit/entity/HumanEntity.html#getAttackCooldown() then is correct... the issue is the "animation" calling in Player NMS a resetAttackStrengthTicker where the cooldown is reset again

[electronicboy]

I think that there was already an issue or PR surrounding this, the issue is that with the nature of latency and having to deal with cases where an existing cooldown is already in effect creates a whole host of other issues

[Doc94]

I think that there was already an issue or PR surrounding this, the issue is that with the nature of latency and having to deal with cases where an existing cooldown is already in effect creates a whole host of other issues

this #12806 ?

Also a workaround i found its listen PlayerArmSwingEvent and cancel because that avoid call later the whole animation and the method for reset...

[electronicboy]

Not that one; I don't remember where the disccusion was; I guess that was actually the item cooldowns, not this one

and yea, the attack AND the swing resets the cooldown, which means that you'd need to handle both events here

[TheBentoBox]

Can confirm that additionally canceling PlayerArmSwingEvent works.