MC-94178A non-JSON-text on a sign produces an unknown error
This issue is related to MC-87143
So according to the "fixed" issue named above it seems to be intended that you have to write JSON-text on signs now.
So that command works just fine:
/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"[\"test\"]",Text2:"[\"\"]",Text3:"[\"\"]",Text4:"[\"\"]"}
while the following just produces an empty sign:
/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"test",Text2:"",Text3:"",Text4:""}
However, what is probably not intended is that the 2nd command produces the following error text in the command block output line even though the sign gets placed:
An unknown error occurred while attempting to perform this command
Environment
Windows 10
Java 1.8.0_25 64 bit
![[Mod] NeunEinser](../../../data/avatars/users/39263.png){kind=small}
Created Issue:
A non-JSON-text on a sign produces an unknown error
This issue is related to
MC-87143
So according to the "fixed" issue named above it seems to be intended that you have to write JSON-text on signs now. So that command works just fine/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"[\"test\"]",Text2:"",Text3:"",Text4:""}while the following just produces an empty sign
/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"test",Text2:"",Text3:"",Text4:""}However, what is probably not intended is that the 2nd command produces the following error text in the command block output line:
An unknown error occurred while attempting to perform this commandeven though the sign got placed.
Environment
Windows 10
Java 1.8.0_25 64 bit
This issue is related to
MC-87143
So according to the "fixed" issue named above it seems to be intended that you have to write JSON-text on signs now.So that command works just fine/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"[\"test\"]",Text2:"",Text3:"",Text4:""}
while the following just produces an empty sign/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"test",Text2:"",Text3:"",Text4:""}However, what is probably not intended is that the 2nd command produces the following error text in the command block output line
:An unknown error occurred while attempting to perform this commandeven though the sign got placed.
This issue is related to
MC-87143
So according to the "fixed" issue named above it seems to be intended that you have to write JSON-text on signs now.
So that command works just fine:/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"[\"test\"]",Text2:"",Text3:"",Text4:""}while the following just produces an empty sign:
/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"test",Text2:"",Text3:"",Text4:""}However, what is probably not intended is that the 2nd command produces the following error text in the command block output line even though the sign got placed:
An unknown error occurred while attempting to perform this command
This issue is related to
MC-87143
So according to the "fixed" issue named above it seems to be intended that you have to write JSON-text on signs now.
So that command works just fine:/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"[\"test\"]",Text2:"",Text3:"",Text4:""}while the following just produces an empty sign:
/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"test",Text2:"",Text3:"",Text4:""}However, what is probably not intended is that the 2nd command produces the following error text in the command block output line even though the sign g
otplaced:An unknown error occurred while attempting to perform this commandThis issue is related to
MC-87143
So according to the "fixed" issue named above it seems to be intended that you have to write JSON-text on signs now.
So that command works just fine:/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"[\"test\"]",Text2:"",Text3:"",Text4:""}while the following just produces an empty sign:
/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"test",Text2:"",Text3:"",Text4:""}However, what is probably not intended is that the 2nd command produces the following error text in the command block output line even though the sign gets placed:
An unknown error occurred while attempting to perform this command
This issue is related to
MC-87143
So according to the "fixed" issue named above it seems to be intended that you have to write JSON-text on signs now.
So that command works just fine:/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"[\"test\"]",Text2:"",Text3:"",Text4:""}while the following just produces an empty sign:
/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"test",Text2:"",Text3:"",Text4:""}However, what is probably not intended is that the 2nd command produces the following error text in the command block output line even though the sign gets placed:
An unknown error occurred while attempting to perform this commandThis issue is related to
MC-87143
So according to the "fixed" issue named above it seems to be intended that you have to write JSON-text on signs now.
So that command works just fine:/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"[\"test\"]",Text2:"[\"\"]",Text3:"[\"\"]",Text4:"[\"\"]"}while the following just produces an empty sign:
/setblock ~ ~1 ~ minecraft:standing_sign 0 replace {Text1:"test",Text2:"",Text3:"",Text4:""}However, what is probably not intended is that the 2nd command produces the following error text in the command block output line even though the sign gets placed:
An unknown error occurred while attempting to perform this command
![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
[Mojang] Grum (Erik Broes)A comment with security level 'global-moderators' was removed.
relates to
relates to
Duplicate of MC-94178
That error message doesn't say anything wrong.
Uhm, actually it does. The error is known, since you can describe it and know when it happens. So it should not be just described as an "unknown error" what is generally a bad thing for a compiler.
Plus it is not even an error. It just can't work with the string, so it returns an empty sign. So it works perfectly fine and it does not cause any problem. It should just say "Block placed".
Reopened for Mojang to decide.
This is behaving as intended.
Internally a NullPointerException gets thrown because a line ends up being null instead of an object. This results in the vague error. There is no intention to fix this since its internal state being messed with.
A page text in a book doesn't get set to null when it's a non-JSON text:
/give @p written_book 1 0 {pages:["a","b","c"],title:"a",author:"a"}It works just as expected. Which behavior is correct, the signs setting to null or the book accepting it?