setNoDamageTicks is broken
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
setNoDamageTicks should make a given player invulnerable for the given amount of ticks
Observed/Actual behavior
They still take damage (in my case from explosions)
Steps/models to reproduce
player.setNoDamageTicks
world.createExplosion next to the player
they die from explosion damage
Plugin and Datapack List
N/A
Paper version
This server is running Paper version 1.21.4-DEV-main@a35cfe9 (1970-01-01T00:00:00Z) (Implementing API version 1.21.4-R0.1-SNAPSHOT)
You are 1 version(s) behind
Download the new version at: https://papermc.io/downloads/paper
Previous version: 1.21.4-DEV-cd9d6d6 (MC: 1.21.4)
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 with the setNoDamageTicks API entry point and reproduce the issue using world.createExplosion next to a player. Trace how explosion damage checks the player's invulnerability ticks, then verify that damage is prevented for the requested duration and add or update coverage if the relevant test location is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100