MC-96757Parsing exceptions count as unsuccessful execution but still execute the command
The bug
When a parsing exception inside a nested command occurs the command returns that it ran unsuccessful, however it still gets executed.
How to reproduce
Use the following command and place a comparator next the command block or a conditional chain command block with a command
/setblock ~ ~1 ~ oak_sign{Text1:"\"Q\"",Text2:"\"Q\"",Text3:"\"Q\"",Text4:"Not JSON!"}
The first JSON data for Text4 is invalid, but instead of not placing the sign at all or ignoring this, it places the sign but states it was unsuccessful
Created Issue:
Parsing exceptions count as unsuccessful execution but still execute the command
The bug
When a parsing exception inside a nested command occurs the command returns that it ran unsuccessful, however it still gets executed.
How to reproduce
Use the following command and place a comparator next the command block or a conditional chain command block with a command
/setblock ~ ~1 ~ standing_sign 0 replace {Text1:"{\"test\"}",Text2:"[\"\"]",Text3:"[\"\"]",Text4:"[\"\"]"}The first JSON data for Text1 is invalid, but instead of not placing the sign at all or ignoring this, it places the sign but states it was unsuccessful
![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
relates to
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
![[Helper] Lord_Quadrato](../../../data/avatars/users/26105.png){kind=small}
The bug
When a parsing exception inside a nested command occurs the command returns that it ran unsuccessful, however it still gets executed.
How to reproduce
Use the following command and place a comparator next the command block or a conditional chain command block with a command
/setblock ~ ~1 ~standing_sign 0 replace{Text1:"{\"test\"}",Text2:"[\"\"]",Text3:"[\"\"]",Text4:"[\"\"]"}The first JSON data for Text1 is invalid, but instead of not placing the sign at all or ignoring this, it places the sign but states it was unsuccessful
The bug
When a parsing exception inside a nested command occurs the command returns that it ran unsuccessful, however it still gets executed.
How to reproduce
Use the following command and place a comparator next the command block or a conditional chain command block with a command
/setblock ~ ~1 ~ oak_sign{Text1:"{\"test\"}",Text2:"[\"\"]",Text3:"[\"\"]",Text4:"[\"\"]"}The first JSON data for Text1 is invalid, but instead of not placing the sign at all or ignoring this, it places the sign but states it was unsuccessful
The bug
When a parsing exception inside a nested command occurs the command returns that it ran unsuccessful, however it still gets executed.
How to reproduce
Use the following command and place a comparator next the command block or a conditional chain command block with a command
/setblock ~ ~1 ~ oak_sign{Text1:"{\"test\"}",Text2:"[\"\"]",Text3:"[\"\"]",Text4:"[\"\"]"}The first JSON data for Text
1is invalid, but instead of not placing the sign at all or ignoring this, it places the sign but states it was unsuccessfulThe bug
When a parsing exception inside a nested command occurs the command returns that it ran unsuccessful, however it still gets executed.
How to reproduce
Use the following command and place a comparator next the command block or a conditional chain command block with a command
/setblock ~ ~1 ~ oak_sign{Text1:"\"Q\"",Text2:"\"Q\"",Text3:"\"Q\"",Text4:"Not JSON!"}The first JSON data for Text4 is invalid, but instead of not placing the sign at all or ignoring this, it places the sign but states it was unsuccessful
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Duplicate of
MC-94178I would rather say relates to. Even if the error message is correctly shown, it can still happen that the sign is placed.
Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.
This is an automated comment on any open or reopened issue with out-of-date affected versions.
Confirmed in 1.16.1.
Can confirm in 20w49a.
Cannot reproduce in 21w03a. Please let us know if you can still reproduce this.