PaperMC / PaperMC/Paper

Attribute modifiers don't reset after death 1.21.1

Open
#11,467 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #11580 by @electronicboy — closed without merging
status: accepted type: bug upstream: spigot version: 1.21.1 version: 1.21.11
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior
  1. the player have an attribute ( like this one for exemple : /attribute @p minecraft:generic.max_health modifier add 1 10 add_value
  2. the player died
  3. the attribute is reset because in this case, the attribute is not the Base attribute

here an exemple of vanilla 1.21.1

https://youtu.be/hHGpRTtGZJA

Observed/Actual behavior
  1. the player have an attribute ( like this one for exemple : /attribute @p minecraft:generic.max_health modifier add 1 10 add_value
  2. the player died
  3. the attribute still active ( and somes plugins are affected by that )
Steps/models to reproduce

how to make the bug:

  1. do that command: /attribute @p minecraft:generic.max_health modifier add 1 10 add_value
  2. play in gamemode survival and do some /kill @p
  3. the generic.max_health modifier is not reset and that is the bug
Plugin and Datapack List

no plugins

Paper version

This server is running Paper version 1.21.1-119-master@7cd4f2c (2024-10-03T15:19:34Z) (Implementing API version 1.21.1-R0.1-SNAPSHOT)

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

Reproduce the issue on Paper 1.21.1 using the /attribute command, then kill the player in survival mode and inspect whether the generic.max_health modifier remains active. Done means the modifier resets after death as described in the expected behavior; check the linked pull request for prior work before starting.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.