Maybe cause for:
The bug
When a tag in the Pose tag of an armor stand contains the default values, it gets removed. This might be useful for saving the NBT data, but this way it is impossible to use NBT comparison to test if one of the tags in Pose has the default values.
How to reproduce
Place an armor stand
Run this command:
/data get entity @e[type=armor_stand,limit=1] Pose Result: Pose:{ Head:[ 0:2.8267171f, 1:-5.086746f, 2:0.0f ], Body:[ 0:0.0f, 1:1.7570348f, 2:0.0f ] }Run this command:
/data merge entity @e[type=armor_stand,limit=1] {Pose:{Body:[0f,0f,0f]}} Result: Pose:{ Head:[ 0:0.702278f, 1:1.4992895f, 2:0.0f ] }
Default values (1.9)
Head: 0.0f, 0.0f, 0.0fBody: 0.0f, 0.0f, 0.0fLeftArm: -10.0f, 0.0f, -10.0fRightArm: -15.0f, 0.0f, 10.0fLeftLeg: -1.0f, 0.0f, -1.0fRightLeg: 1.0f, 0.0f, 1.0f
Linked issues
is duplicated by 4
MC-80974
ArmorStand has missing pose entries
Resolved
MC-123213
Armor stand's nbt: Head Pose is ignored when its Head Pose data is [0.0f,0.0f,0.0f]
Resolved
MC-132845
Some nbt set to default values disappear immediately
Resolved
MC-265398
The data like Pose.Head might unexpectedly be invalid
Resolved
relates to 2
Comments 27
MC-80974 is the expression of this issue, the armorstands are placed with arm and leg poses of 0 and therefore are removed as is described here.
Use
/entitydata @e[r=3] {Pose:{Head:[0.0d,0.0d,0.0d]}}The correct useage of the Pose tag uses double not float. Make sure you put 0.0 or 0.0d
@unknown like I said in MC-80973 ArmorStand have always pretermined pose values. So they are never 0.
@unknown The values are floats. The data structure I provided is the one you recieve when using /entitydata.
Could you merge this post with MC-80974, this is just twice the same issue under another name, since, as you've described yourself already, a NBT Pose tag does not exist when it is 0.