I could be wrong, but I do not believe this is a bug. In the latest snapshot, executing as an entity and executing at an entity are broken up. When you type in the command /execute as @p run teleport @e[type=armor_stand,limit=1,sort=nearest] ~ ~ ~2, it executes the command as run by the the player, but the location of it is still relative to the command block(or where the command was executed). In other words, it executes the command as the player, but the relative coordinates are not at the player. In 1.12, executing as the entity and at the entity were the same thing, which is why the first command works in 1.12. In the snapshot and forward, you would have to add an "at @s" after the "as @e" to change the relative coordinates of the command. Like this for example: /execute as @p at @s run teleport @e[type=armor_stand,limit=1,sort=nearest] ~ ~ ~2
Jack Lanois
I could be wrong, but I do not believe this is a bug. In the latest snapshot, executing as an entity and executing at an entity are broken up. When you type in the command /execute as @p run teleport @e[type=armor_stand,limit=1,sort=nearest] ~ ~ ~2, it executes the command as run by the the player, but the location of it is still relative to the command block(or where the command was executed). In other words, it executes the command as the player, but the relative coordinates are not at the player. In 1.12, executing as the entity and at the entity were the same thing, which is why the first command works in 1.12. In the snapshot and forward, you would have to add an "at @s" after the "as @e" to change the relative coordinates of the command. Like this for example: /execute as @p at @s run teleport @e[type=armor_stand,limit=1,sort=nearest] ~ ~ ~2