When using the new components of the new function, the game detects the command as an error (I tested with the new and the old ones and it only detects the new ones as wrong).
Linked issues
is duplicated by 1
Attachments
Comments 5
This is not a bug, you just need to enable “upcoming creator features” inside your world. Although, it will disable the use of the old execute format. (e.g. new format: execute as @s run say hi) (e.g. old format: execute @s ~~~ say hi)
I have a 1.19.51 world with the new "execute as" syntax in use when using the interactive commands via chat.
The same commands do not work when they are used in an mcfunction file, with a parsing error thrown as shown below
[Commands][warning]-Error on line 1: command failed to parse with error 'Syntax error: Unexpected "@e": at "xecute as >>@e<<[type=twf:"'
The problem is not resolved with enabling "upcoming creator features" inside the world.
If you are experiencing this behaviour, make sure your Behavior Pack manifest.json entry is set correctly to align with the new execute syntax:
"min_engine_version": [1, 19, 50]
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Is this still an issue in the latest version? If yes, can you please add it to the affected versions (or mention it if you are not the reporter)? Also, could you please attach an example addon showcasing the issue?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki
This is not a bug, you just need to enable “upcoming creator features” inside your world. Although, it will disable the use of the old execute format. (e.g. new format: execute as @s run say hi) (e.g. old format: execute @s ~~~ say hi)