The bug
With the new /execute command syntax, the subcommands if block and if blocks take a world position, but the autocomplete for the block's position suggests a number past the integral value. This is inconsistent with other commands pertaining to blocks, whose autocomplete suggests integer values as blocks are aligned to the block grid.
Steps to reproduce:
Set up a new world with the Upcoming Creator Features experiment enabled.
Start typing out the command below while aiming at a block:
/execute if block
→❌ The autocomplete for the position suggests a float value.
Attachments
Comments 4
Confirmed but this is the same for all bedrock block commands
EDIT: ah it is a bit different because tab suggests float coords instead of integer ones
I'm having somewhat of a similar problem, however I am using execute @a[m=c,tag=brush] ^ ^ ^10 clone xyz uvw ~-3 ~-2 ~-3 masked normal. This command I use everyday to paint a selected region wherever my cursor is facing. Normally this would would work within a specific range of the repeating command block, and if I get out of range of the command block I place another with the same command. This is where it messes up the secondary repeating command block suddenly does not recognize the player even when I have the tag (brush) enabled. Even if I get rid of my primary repeating command block the command still executes where the original command block was and still will not run the command at the secondary. And yes I do have my render distance to 40 and I can even look at the region of blocks I am trying to clone. This issue seems similar to your report so I thought I'd give my two sense because I really need this fixed in order to keep building my large scale map.