gerrybrano
MC-81237
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
stat.damageTakendoes notincrement when player has absorption hearts.stat.damageTaken fails to increment when player has absorption hearts.
stat.damageTaken fails to increment when player has absorptionhearts.
With an objective tracking stat.damageTaken,
taking damage while having any amount ofabsorption heartswillfail to cause the score of said objective to increase.With an objective tracking stat.damageTaken, damage taken to absorption hearts fail to cause the score of said objective to increase.
The spacing between the first and second lines in all instances of hover text
aregreater than that of any following lines.Here is the command used to generate the example image:
tellraw @a { "text":"hover", "hoverEvent":{ "action":"show_text", "value":"Here are some words\nHere are more words\nHere are last words" } }The spacing between the first and second lines in all instances of hover text is greater than that of any following lines.
Here is the command used to generate the example image:
tellraw @a { "text":"hover", "hoverEvent":{ "action":"show_text", "value":"Here are some words\nHere are more words\nHere are last words" } }
Summary:
Using /attribute to change the max_health base value to a value lower than the "Health" value does not update the "Health" value as would be expected.
Repo Steps:
Create a new world and run
{{/attribute @s minecraft:generic.max_health base set 1}}Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running{{ /data get entity @s Health}} will show a value of 20.0f.
Summary:
Using /attribute to change the max_health base value to a value lower than the "Health" value does not update the "Health" value as would be expected.
Repo Steps:
Create a new world and run /attribute @s minecraft:generic.max_health base set 1
Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running /data get entity @s Health will show a value of 20.0f.
Summary:
Using /attribute to change the max_health base value to a value lower than the "Health" value does not update the "Health" value as would be expected.
Repo Steps:
Create a new world and run
/attribute @s minecraft:generic.max_health base set 1Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running /data get entity @s Health will show a value of 20.0f.
Summary:
Using /attribute to change the max_health base value to a value lower than the Health value does not update the Health value as would be expected.
Repo Steps:
Create a new world and run:
/attribute @s minecraft:generic.max_health base set 1Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running the following will show a value of 20.0f:
/data get entity @s Health
Summary:
Using /attribute to change
themax_health base value to a value lower than theHealth value does not update theHealthvalueas would be expected.Repo Steps:
Create a new world and run:
/attribute @s minecraft:generic.max_health base set 1Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running the following will show a value of 20.0f:
/data get entity @s HealthSummary:
Using{{ /attribute}} to change{{ minecraft:generic.max_health}} base value to a value lower than the Health value does not update the Health value as would be expected.
Repo Steps:
Create a new world and run:
/attribute @s minecraft:generic.max_health base set 1Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running the following will show a value of 20.0f:
/data get entity @s Health
Summary:
Using{{ /attribute}} to change
{{ minecraft:generic.max_health}} base value to a value lower than theHealth value does not update the Health value as would be expected.Repo Steps:
Create a new world and run:
/attribute @s minecraft:generic.max_health base set 1Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running the following will show a value of 20.0f:
/data get entity @s HealthSummary:
Using{{ /attribute}} to change minecraft:generic.max_health base value to a value lower than the Health value does not update the Health value as would be expected.
Repo Steps:
Create a new world and run:
/attribute @s minecraft:generic.max_health base set 1Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running the following will show a value of 20.0f:
/data get entity @s Health
Summary:
Using{{ /attribute}}to change minecraft:generic.max_health base value to a value lower than the Health value does not update the Health value as would be expected.Repo Steps:
Create a new world and run:
/attribute @s minecraft:generic.max_health base set 1Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running the following will show a value of 20.0f:
/data get entity @s HealthSummary:
Using /attribute to change minecraft:generic.max_health base value to a value lower than the Health value does not update the Health value as would be expected.
Repo Steps:
Create a new world and run:
/attribute @s minecraft:generic.max_health base set 1Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running the following will show a value of 20.0f:
/data get entity @s Health
/attribute max_health does not modifyhealth value./attribute max_health does not modify Health value.
/attributemax_healthdoes not modify Health value.Reducing max health using /attribute does not reduce current health
Summary:
Using /attribute to change minecraft:generic.max_health base value to a value lower than the Health value does not
update the Health value as would be expected.Repo Steps:
Create a new world and run:
/attribute @s minecraft:generic.max_health base set 1Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running the following will show a value of 20.0f:
/data get entity @s HealthSummary:
Using /attribute to change minecraft:generic.max_health base value to a value lower than the Health value does not reduce the Health value as would be expected.
Repo Steps:
Create a new world and run:
/attribute @s minecraft:generic.max_health base set 1Expected Result:
Only 1, half-filled heart container visible.
Actual Result:
Only 1, fully filled heart container visible.
Verifying:
Running the following will show a value of 20.0f:
/data get entity @s Health
This bug is a multiplayer issue only. It happens when the server is set to peaceful difficulty before a player joins and then gets set to something other than peaceful, after. The client seems to not get updated by the server of the change. If you check your difficulty in the options menu when you first join, it will correspond to the current difficulty of the server and does not update when you change the difficulty through the console. As a result the client renders the hunger as if it was still in peaceful, causing it to always refill. However, your hunger value is actually still going down. If the player re-logs after experiencing this, their hunger will display its proper value, the hunger bar will act as it should, and the difficulty setting in the options menu will show the correct difficulty.
Yes, TrazLander. See my comment above.
This started in 15w33c. "Malformed JSON at line 1 column 1" has nothing to do with character count of the command block as "summon MinecartCommandBlock ~ ~.5 ~ {Command:say 1,Riding:{id:MinecartCommandBlock,Command:say 2}}" produces the same message. Something is fundamenatlly broken with stacked minecart command blocks.
Pasting a command with maximum character count (32,500) into a command block in 15w45a no longer causes disconnects and minecart command blocks no longer cause a crash.
Confirmed for 16w06a.
Confirmed for 1.10
Both score and selector tags do not work in books. However, with the score tag, If you use a UUID for the name it will work for non-ops as well.
Still occurs in 17w50a.
Yes husky2490. Read my first comment.
Still affect all versions up to 18w03b, which is the latest snapshot as of this message.