-
Bug
-
Resolution: Cannot Reproduce
-
None
-
Minecraft 15w39c, Minecraft 15w40b, Minecraft 15w42a, Minecraft 15w46a, Minecraft 16w06a, Minecraft 1.9 Pre-Release 1, Minecraft 1.9 Pre-Release 4, Minecraft 1.9, Minecraft 1.9.1 Pre-Release 3, Minecraft 1.9.2, Minecraft 16w15a, Minecraft 16w15b, Minecraft 1.9.4, Minecraft 16w21b, Minecraft 1.10.2, Minecraft 16w42a, Minecraft 1.11, Minecraft 16w50a, Minecraft 1.11.2, Minecraft 1.12.2, Minecraft 17w50a, Minecraft 18w03b, Minecraft 1.13-pre8, Minecraft 1.13, Minecraft 18w30b, Minecraft 18w31a, Minecraft 18w32a, Minecraft 18w33a, Minecraft 1.13.1-pre1, Minecraft 1.13.1, 1.15.2, 1.16 Release Candidate 1, 1.16
-
Confirmed
-
(Unassigned)
The bug
Selector arguments which select entities based on their position fail finding them if they have been moved to a different chunk in the same tick. Moving the entity to the next chunk might not always cause this bug since the initial entity search area can be larger than the specified values.
The root cause is likely MC-108469 because at least in 1.12.2 selectors get the entities to check from the respective chunks and if the entity lists have not been updated the entities will not be found.
Note: This does not affect the @s selector.
Affected selector arguments
Last updated for 17w50a
- distance
- dx
- dy
- dz
How to reproduce
- Place an impulse command block with the following command
/execute as @e[type=armor_stand] at @s run teleport @s ~33 ~ ~
- Place an always active chain command block with the following command behind it
/execute as @e[type=armor_stand] at @s run say @e[distance=0]
- Place an armor stand
- Power the impulse command block
→
It fails finding itself
