In a previous bug report I complained that you can not execute various commands
because the result won't output to the player chat.
Searge pointed it out "as intended" - hell knows why thats the case but never mind...
But you can not deny, that it is not a bug if you want to run the following command in a commandblock
execute @p ~ ~ ~ help
execute @p ~ ~ ~ help 2
If you do so, it won't output the help chat to the player.
the output of the commandblock you can see in the screenshots.
For the 1st command is says sth about "/effect" what doesn't make any sense
and for the 2nd command it just won't accept it.
This is no duplicate of MC-62352 even though I still can't understand why that should "work as intended"
But in this case this defenitely is a bug, as you can see by the error in the command block.
If you think that once again "this is working as intended" then ***** reconsider this please!
The command structure is "/execute <entity> <x> <y> <z> <command>"
and not /execute <entity> <x> <y> <z> <some random commands I think they might be ok, you won't need them anyway>"
So every! command should work with "execute" or this just useless bullcrap
Linked issues
is duplicated by 2
Attachments
Comments 5
Quote from MC-62352
Another example:
execute @p ~ ~ ~ /help
What I expect:
It should show the help menu to the target playerWhat actually happens:
nothing - , nothing is shown in the chat, also no errors.
what's the difference to this report ?
if you have a look at the output in the commandblock, you will see that there is a error/abnormality.
If you execute "/help" then there is no way the output will say something about "/effect"
Also the other commands like "/seed" they DO work. They just ouput the result in the commandblock and not to the players chat.
But for "/help" this will cause a error.
+ I in this report i pointed out, that according to the commands strukture, this ought be able to work
So reopen this report and let someone responsible decide!
Because of these unnecessary actions, bugs keep getting ignored and stay in the game forever.
Some commands are intended only to affect the person who runned the command.
Beside the fact that its really a bug that it displays "/effect ..." when the /execute @p ~ ~ ~ help command is executed by a command block it seems that various "non ingame related" commands like /help, /seed are treated like that.
I think its more a developers decision that they don't want some commands (works as intended MC-62352 ) to be done via /execute command block.
Either way, this is still a dupe of MC-62352
Please don't try to dupe your own tickets!
MC-62352 was resolved as "Working as Intended" by Mojang.