MC-101234Stack trace is not printed in log when exception occurs while running command
Introduction
Even though [Mojang] Grum (Erik Broes) wrote in his comment on MC-86949:
Using internals gives you internal errors
(Not sure if this applies here)
There are enough situations in which plain exceptions are printed in the log without a message like "Couldn't process command".
The bug
Using commands which do not run successfully because of an exception while executing them only prints the following in the log.
Couldn't process command: '[COMMAND USED]'
This makes it pretty difficult to find the reason why this happened. Instead the exception should be printed as well.
How to reproduce
- Use the reproduction steps of
MC-116927while having the world open - Use the /reload command
You cannot tell what why the command could not be executed. (In this case the advancement file had an invalid content)
Created Issue:
Unknown errors do not print exception into log
Introduction
Even though [Mojang] Grum (Erik Broes) wrote in his comment on
MC-86949:Using internals gives you internal errors
(Not sure if this applies here)
There are enough situations in which plain exceptions are printed in the log without a message like "Couldn't process command".The bug
Using commands that do not run successfully because of an exception while executing it only print in the log: "Couldn't process command: '[COMMAND USED]'"
This makes it pretty difficult to find the reason why this happened. Instead the exception should be printed as well.
How to reproduce
- Use the following command
/setblock ~ ~ ~ hopper 1 replace {Items:[{id:"stone",Count:1b}]}You cannot tell what the reason is why the command could not be executed. (In this case the meta data is invalid)
Introduction
Even though [Mojang] Grum (Erik Broes) wrote in his comment on
MC-86949:Using internals gives you internal errors
(Not sure if this applies here)
There are enough situations in which plain exceptions are printed in the log without a message like "Couldn't process command".The bug
Using commands that do not run successfully because of an exception while executing it only print in the log: "Couldn't process command: '[COMMAND USED]'"
This makes it pretty difficult to find the reason why this happened. Instead the exception should be printed as well.
How to reproduce
- Use the following command
/setblock ~ ~ ~ hopper 1 replace {Items:[{id:"stone",Count:1b}]}You cannot tell what
the reason iswhy the command could not be executed. (In this case the meta data is invalid)
Introduction
Even though [Mojang] Grum (Erik Broes) wrote in his comment on
MC-86949:Using internals gives you internal errors
(Not sure if this applies here)
There are enough situations in which plain exceptions are printed in the log without a message like "Couldn't process command".The bug
Using commands that do not run successfully because of an exception while executing it only print in the log: "Couldn't process command: '[COMMAND USED]'"
This makes it pretty difficult to find the reason why this happened. Instead the exception should be printed as well.
How to reproduce
- Use the following command
/setblock ~ ~ ~ hopper 1 replace {Items:[{id:"stone",Count:1b}]}You cannot tell what why the command could not be executed. (In this case the
meta data is invalid)Introduction
Even though [Mojang] Grum (Erik Broes) wrote in his comment on
MC-86949:Using internals gives you internal errors
(Not sure if this applies here)
There are enough situations in which plain exceptions are printed in the log without a message like "Couldn't process command".The bug
Using commands which do not run successfully because of an exception while executing them only prints the following in the log.
Couldn't process command: '[COMMAND USED]'This makes it pretty difficult to find the reason why this happened. Instead the exception should be printed as well.
How to reproduce
- Use the reproduction steps of
MC-116927while having the world open- Use the /reload command
You cannot tell what why the command could not be executed. (In this case the advancement file had an invalid content)
Unknown errors do not print exception into logStack trace is not printed in log when exception occurs while running command
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
relates to
is cloned by
Numeric metadata is no longer supported. The command gives a reasonable error now.
This is fixed in 1.12-pre3:
a.warn("Couldn't process command: " + string, throwable);