Affects Version/s: 188.8.131.52, 184.108.40.206
Fix Version/s: 220.127.116.11
Platform:Windows 10 - PC
Selector arguments such as c, r, dx, dy, and dz work entirely on the block level – an entity that is physically outside the range will still be detected if it anywhere is inside a block that is partially inside the range.
1. Teleport yourself to the center of some block: /tp @s 0 64 0
2. Summon an armor stand 1.5 blocks away from you: /summon armor_stand ~ ~ ~1.5
3. Run a selector from the armor stand: /execute @e[type=armor_stand,c=1] ~ ~ ~ say @a[r=1]
Expected result: empty output since the player is further than one block away.
Actual result: player is found.
The player can continue moving even further away from the armor stand – any position in the block teleported to will be found by the selector, even those that should not be. Even if the armor stand is in a position such that the r=1 "sphere" barely overlaps a block, entities will be found regardless of where they are in that block.
In practice, this makes precise position selectors difficult or impossible – despite the existence of decimal selector arguments, all searches are done on a per-block level. I used integers exclusively to demonstrate here, but this is easily reproducible with the decimal ones: /execute @e[type=armor_stand,c=1] ~ ~ ~ say @a[r=0.001] should almost never find players, but in reality it finds every player that shares a block with it.