New /execute syntax fails to be acknowledged when used in functions

Using the new /execute command syntax in behavior packs is dependent on two factors:

• Having the Upcoming Creator Features experiment enabled (which you have done here)

• Setting the pack's *minimum engine version* to 1.19.10 or greater.

{
  "format_version": 2,
  "header": {
    // ...
    "min_engine_version": [1, 19, 30]
}

Are both of these true?

Thank you for your report!

However, this issue has been temporarily closed as Awaiting Response.

Did you make sure to turn on the Upcoming Creator Features experimental toggle?

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki

@Sprunkles All creator features are enabled as mentioned in the report. My format version is 2. But my minimum engine version is 1.16.0. If I change this to 1.19.30 will it affect anything in any way? Or will the old syntax still be usable?

@Ch39 You may experience a few differences in the command engine as the minimum engine version increases. The notable one here is that the new /execute syntax is enabled for functions by setting it to 1.19.10 or greater, replacing the old syntax in the process. You will not be able to use the old syntax upon upgrading, but you can always set the min engine version to an older version (like the 1.16.0 you have it at now).

That really sucks… I would have to rewrite almost 30 hours of work for my add-on. I thought there was a system in place for add-ons to use both syntax. Anyway, thanks for the help😁