mojira.dev
MC-90711

Marker ArmorStands cannot be selected within r=0

If an ArmorStand has Marker:1b set, it cannot be found with r=0.

Setup:
Stand somewhere, without moving
/summon ArmorStand ~ ~ ~ {Marker:1b}
/testfor @e[r=0]

What should happen:
Found {player}
Found Armor Stand

What actually happens:
Found {player}

This is not because of the relative position of the stand; If you walk a bit away and run
/execute @e[type=ArmorStand,c=1] ~ ~ ~ testfor @e[r=0]
the command will fail.

Other entities may be selected within the range, however; If the first experiment is run with a NoAI Sheep summoned as well, at exactly the same position, the command will find the player and the sheep, but not the stand.

Notes:

  • A range of 1 or more results in correct behavior of commands.

  • Non-Marker stands can be selected with r=0

  • A possible cause of this may be the way entities in range are checked in the code; As the Marker ArmorStand has no hitbox, selection by range may be inherently buggy due to the calculation method.

Comments 16

confirmed for windows 7 as well

Heavy editing due to further testing; Confirmed for 15w45a.

Confirmed for 15w52a.

Oh, sorry, meant 51b.

6 more comments

putting down the version only already is a log of the versions + "added affected version" also goes in the activity feed + you have a history tab about the comments section that also records this

Apparently, r=0 is totally broken now.

This is still an issue even though r=0 now does r=0.25.

Under the new selector order, seems fixed.

Ozone Smith

(Unassigned)

Community Consensus

armor_stand, entity, marker

Minecraft 15w42a, Minecraft 15w45a, Minecraft 16w02a, Minecraft 16w03a, Minecraft 16w04a, Minecraft 16w05a, Minecraft 16w05b, Minecraft 16w06a, Minecraft 16w07a, Minecraft 1.9 Pre-Release 1

Minecraft 1.9 Pre-Release 4

Retrieved