The Bug:
Execute commands no longer function when a forward slash is used within the subcommand.
This behavior worked in 1.12.2, but was lost in 1.13.
Steps to Reproduce:
Launch an instance of 1.12.2 and execute the command provided below where a forward slash is used within the subcommand.
/execute @e[type=minecraft:pig] ~ ~ ~ /say hiTake note of how the command ran successfully.
Launch an instance of the latest version of Minecraft and execute the command provided below where a forward slash is used within the subcommand.
/execute as @e[type=minecraft:pig] run /say hiObserve if the command ran successfully or not.
Observed Behavior:
Execute commands no longer function when a forward slash is used within the subcommand.
Expected Behavior:
Execute commands would function when a forward slash is used within the subcommand.
Attachments
Comments 3
Can also confirm. I guess the solution here is to just forget the forward slash, since it works without it. It might even be intentional
Thank you for your report!
After consideration, the issue is being closed as Working as Intended.
Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.
Full Version History – Snapshot Version History – The official Minecraft feedback site
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Can confirm.