It's possible to have higher maximum health than actual health (see MC-16345) because the helth doesn't adequately update server-side when an attribute stops being applied.
In this state, when the player takes more damage than its max health, the client will show the death screen. However, since the maximum health has not actually been updated yet on the server side, the player doesn't die server-side. When the player then clicks "Respawn", the game continues as if the player hadn't died.
This is a client-server desync where on the client-side, the player dies, but server-side, it doesn't.
To reproduce
Place a wither rose
Switch into survival mode
Give yourself this item:
/give @p dirt{AttributeModifiers:[{AttributeName:"generic.max_health",Name:"generic.max_health",Amount:20d,Operation:0,UUID:[I;0,1,2,3],Slot:"mainhand"}]}Select the dirt block
Run this command to fill your health:
/effect give @p minecraft:instant_health 1 3Deselect the dirt block
Walk into the wither rose
→ ❌ You die immediately (because the server sends to the client "decrease health by 20 because max health changed")
→ ❌ On the death screen, you continue to take damageClick "Respawn"
→ ❌ You don't respawn, but are still at the same location as if nothing happened
These actions can also cause this bug from being triggered, apart from being damaged by a wither rose:
Instant health effect
Instant damage effect
Poison effect
Suffocation
Drowning
Starvation (Hunger)
Hitting a wall with elytra
Linked issues
relates to 1
Attachments
Comments 49
It's still happening in Minecraft 1.6.2. Check MC-29319 for simpler repro steps.
Confirmed for
14w30c
14w31a
Minecraft 1.8-pre 1
Form MC-33827:
Give yourself an item with the max health attribute
/give @p dirt 1 0 {AttributeModifiers:[0:{AttributeName:"generic.attackDamage",Name:"generic.attackDamage",Amount:10000,Operation:0,UUIDLeast:894654,UUIDMost:2872},1:{AttributeName:"generic.movementSpeed",Name:"generic.movementSpeed",Amount:2.5,Operation:1,UUIDLeast:111113,UUIDMost:1111},2:{AttributeName:"generic.maxHealth",Name:"generic.maxHealth",Amount:40,Operation:0,UUIDLeast:111113,UUIDMost:1111}],display:{Name:"GodSword 2.1",Lore:["The Ultimate Power","By Vengeur69"]}}Give yourself constantly the instant health effect by a clock or just use this command:
/effect @p instant_health 300000 5Get hurt (this doesn't always work on the first try, the best way is to use this command; seems not to be necessary)
/effect @p instant_damage 300000 1And now select and deselect the item with the max healt attribute very often
I know some of the steps here use other bugs, but this also works without using these bugs
I am able to reproduce this, while healing with Regeneration, as I took damage, it showed I died, but my health is still full. And my health is still Regenerating. Once I hit the respawn button, I went all sideways (half dying animation). I'm playing on 1.8.1
The more you do it, the lower the player gets
Also it is only visible to you, not anybody else
Confirmed for
15w46a
Please include a way to reproduce:
Give yourself an item with the max health attribute
/give @p dirt 1 0 {AttributeModifiers:[{AttributeName:"generic.maxHealth",Name:"generic.maxHealth",Amount:40d,Operation:0,UUIDLeast:111113,UUIDMost:1111,Slot:"mainhand"}]}Give yourself constantly the instant health effect by a clock or just use this command:
/effect @p instant_health 300000 5Get hurt (this doesn't always work on the first try, the best way is to use this command; seems not to be necessary)
/effect @p instant_damage 300000 1And now select and deselect the item with the max healt attribute very often
It's still working in 16w03a.
Still in 16w06a
Still in 1.9 pre-realase 2.
Still in 1.9-pre3
Still in 1.9-pre4
Still in release 1.9
Still in 1.9.1-pre1
Still in 1.9.1-pre3
Can confirm for 1.9.1 & 1.9.2, you can tell it is a fake death, because it does not show up on statistics.
Still in 16w15b
Having a health value above your maxHealth attribute and then taking certain types of damage cause the false death.
fire, poison, suffocation, and drowning cause false death.
melee, fall, momentum damage do not cause false death
confirmed for 16w41a
@unknown, 16w41a is already marked as affected
Can confirm for MC 1.12.1.
@colton Jelsema, More specifically, If health is greater than or equal to 2*maxhealth, the fake death occurs upon updating your health. This is likely do to the game causing damage to the player equal to (health-maxhealth) (when maxhealth<health) upon a health update occurring, and with the condition I gave above, the game would consider this damage to be a fatal hit to a player (health=2*maxhealth, damage=2*maxhealth-maxhealth=maxhealth), thus triggering the death screen. However, since the player's health (now equal to maxhealth) is still greater than 0, no death actually occurs.
confirmed for MC 1.14.1
confirmed for MC 1.14.2
confirmed for MC 1.14.3
confirmed for MC 1.14.4
Confirmed for MC 1.15 and MC 1.15.2
This issue could easily be resolved by updating the players maxHealth value to match the attribute when it is modified
Really hard to believe this is still an issue after all of these years
So many closed duplicates...
It's really too bad that this is marked low priority. This would be a simple fix, and causes a big headache to many map makers. With the addition of the new /attribute command introduced in 20w17a, this could be a great opportunity to finally take care of this bug.
Affects 1.16.1
Affects 20w27a
for any one heaving problems with this bug
if you want to control player heath
heath boost is a good work around
it will display to hafe heart and dosent glitch
effect give @s minecraft:health_boost 1 3 true
attribute @s[scores={health=1}] minecraft:generic.max_health base set 1
X20
effect clear @s minecraft:health_boost
attribute @s minecraft:generic.max_health base set 20
i was messing with this bug and i noticed something: the more times you repeat the glitch the more inclined the player gets, so i thought, can i get the player to be upside down?, well, unfortunately, no, you can't, however i managed to get the player stuck in a infinite respawn screen, if immediateRespawn is active you can interact with the world, but you cannot move. As usual, relogging fixes the infinite respawn screen.
Can confirm for 20w29a.
In 1.16.2 Pre-1
Confirmed on 1.16.2.
@unknown already added to the affected versions
How to fix
look at attribute command
attribute @s generic.max_health modifier add 22e67162-454c-4125-9ff5-cb71365a41a8 "mat.damage" -15 add
effect give @s instant_health
will not do fake death.
If my max health is below 20 when i take damage higher than my health it will create "fake death"
For example
5 max hp.
20 hp (hp not reduced to max, because i don't get any heal or damage)
effect give @s intant_healt - take 15 damage to reduce my health to maximum.
How to fix - always reduce health to maximum
bug -
if hp>maxHp
then "damage on client side"="real damage"+hp-maxHp
else "damage on client side"="real damage"
fix -
if hp>maxHp then hp=maxHp
If you do /attribute @s minecraft:generic.max_health base set 1 and take any damage, I think the client(or the server, I don't know so much about this) will think that you are half a heart, but the server(or the client) will think will are 1 heart, causing this bug to happen.
I can get this to work by just
/attribute @p minecraft:generic.max_health base set 10which should set my max health to 5 hearts
/data get entity @p Healthshows I have 20 health
now, I set up a dispenser with arrows hooked up to a pressure plate, should be 3 damage
It does the fake death, click respawn, everything back to normal, 5 hearts
this is on 1.16.4
edit this doesn't trigger when zombies attack and it seems like health is correctly 10
Can confirm in 20w51a.
Can confirm in 21w05b.
Can confirm in 21w06a.
Can confirm in 21w07a. Video attached.
Can confirm in 21w11a
but if modifying health with the /attribute command you have to specify your name (@s doesnt work)
Can confirm in 21w17a.
I see this is "In Progress". Perhaps fix it and make it also a feature somehow?
Fixed!
Erik Broes
Seems like a combination of MC-18027 and the issue where getting healed at the same time as you die causes you to turn sideways (which I can't seem to find).