-
Bug
-
Resolution: Unresolved
-
None
-
1.19.60.25 Preview, 1.19.60.24 Preview, 1.19.50, 1.19.51, 1.19.60
-
None
-
Confirmed
-
Windows
-
939952
All command blocks with new /execute format that's created before 1.19.50 update doesn't work now.
command block with new /execute format in the video (Written before 1.19.50): /execute positioned 978 -59 1018 run testforblocks ~ ~ ~ ~ ~ ~ ~ ~-3
It somehow results error with "run" part and this shouldn't happen...
at least I can fix it when I write something random and update the command block and revert the change to original command block, as you can see in the video,
but this is extremely annoying bug as i wrote like 500+ command blocks with new format in 1.19.40
Note: It seems that command block with "Version 21~24" will result in error with new /execute format. I used my data editor to rewrite version "24" into "25" and the command block worked correctly.
(One at the top is a repeating command block which doesn't work since 1.19.50, it's version value is "24".
And other one is a repeating command block which I fixed using the method above, it's version value is "25")
- is duplicated by
-
MCPE-164716 The Execute Command Stopped Working...
- Resolved
-
MCPE-164722 The Execute Command Stopped Working...
- Resolved
-
MCPE-164732 Existing command blocks with new execute commands do not work with errors until changes are made
- Resolved
-
MCPE-164738 "execute @p" command does not work
- Resolved
-
MCPE-164832 Correct Command Wont Work
- Resolved
-
MCPE-165819 /execute Command Blocks no longer work after ~1.19
- Resolved
-
MCPE-167143 Old execute syntax still works in command blocks that were placed before 1.19.50 and have not been updated by a player interaction
- Resolved