Command error messages aren't printed into chat for certain /execute commands
I'm a bit confused here. When I run this command twice without moving:
/execute run setblock ^ ^ ^10 minecraft:gold_block
I get back "Could not set the block" after the second time. However, when I do the same thing with this command, I don't get that message on the second run:
/execute at @p run setblock ^ ^ ^10 minecraft:gold_block
Linked Issues
is duplicated by1
Created Issue:
Command error messages aren't printed into chat for certain /execute commands
I'm a bit confused here. When I run this command twice without moving:
/execute run setblock ^ ^ ^10 minecraft:gold_blockI get back "Could not set the block" after the second time. However, when I do the same thing with this command, I don't get that message on the second run:
/execute at @p run setblock ^ ^ ^10 minecraft:gold_block
There is no end to the mountain of crap that commands and command blocks are spewing instead of doing their job since 1.13 came out. I'm actually here right now because I'm looking for signs of people having the same two blatant /execute issues that I keep running into and want fixed.
is duplicated by
Thank you for your report!
We're tracking this issue in MC-125823, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Can confirm in 20w49a.
Can confirm in 20w51a.
Can confirm in 21w03a.
Can confirm in 21w05a.
Can confirm in 21w06a.
Can confirm in 21w07a.
Video attached.
Can confirm in 1.17.1.
Just curious, does the log report any brigadier errors?
Can confirm in 1.19. user-f2760, I don't believe so, no.
Can confirm in 1.19.2.