The Lore strings cannot be formatted in json
As the title says, the Lore strings cannot be formatted as json, it'll just show the direct string:
example, use:
give @s stick{display:{Lore:["{\"text\":\"Hello\"}"]}}
Side note: a new function may want to be added for loot tables, for the same reason as the set_name function got added.
Side note 2: might as well be changed to a single string rather than a list of strings.
Linked Issues
Created Issue:
The Lore strings cannot be formatted in json
As the title says, the Lore strings cannot be formatted as json, it'll just show the direct string:
example, use:
give @s stick{display:{Lore:["{\"text\":\"Hello\"}"]}}
As the title says, the Lore strings cannot be formatted as json, it'll just show the direct string:
example, use:
give @s stick{display:{Lore:["{\"text\":\"Hello\"}"]}}Side note: a new function may want to be added for loot tables, for the same reason as the set_name function got added.
As the title says, the Lore strings cannot be formatted as json, it'll just show the direct string:
example, use:
give @s stick{display:{Lore:["{\"text\":\"Hello\"}"]}}Side note: a new function may want to be added for loot tables, for the same reason as the set_name function got added.
As the title says, the Lore strings cannot be formatted as json, it'll just show the direct string:
example, use:
give @s stick{display:{Lore:["{\"text\":\"Hello\"}"]}}Side note: a new function may want to be added for loot tables, for the same reason as the set_name function got added.
Side note 2: might as well be changed to a single string rather than a list of strings.
relates to
Confirmed 18w21a.
18w22a
1.13-pre3 still affected
Still affects 18w20a.
Still affects 18w07a; since it's still not fixed I'd say it's probably intentional.
Which makes translations in items a lot less useful.
18w10b affected
Affects release 1.13.1
wellp it's in release 1.13 no surprise there
Affects pre4
They are currently not json strings, see MC-123772.
Wouldn't using HideFlags to hide regular enchantments and then using lore fulfil this (after MC-123772 is fixed)?
That one works for /tellraw, at least in my testing:
/tellraw @p {"translate":"enchantment.damage.all"}
If you mean as lore, then no, it isn't possible in-game yet (until lore is changed to components), but that's MC-123772.
Great. Now that this is fixed, can someone fix MC-123772 which is a little bit more important? (And which has been around for way longer)
A similar issue occurs with version numbers in the Singleplayer world selection menu, it shows the entire unformatted JSON string (e.g. "TextComponent:{text='1.12.2', siblings=[]..." instead of formatting it (e.g. "1.12.2"). (Not sure if that classifies as a separate issue though)
That's
MC-123764.The same goes for display:{Name:
display.Name can have json just file.
give @s stick{display:{Name:"{\"text\":\"Hello\"}"}}This still affects 18w02a. Please update.
Is this technically a feature request just like
MC-119795? I know that the feature is finally creeping in with the latest snapshots, but I think it only applies to actual names (according to the 18w01a changelog), not things like Lore? Or perhaps they mentioned somewhere that that's supposed to be affected too? I mean, it'd make obvious sense for it to work for Lore even if they didn't explicitly say so, but I figured I'd mention it anywayIn the r/minecraftcommands discord server, dinnerbone stated that Lore would be translatable strings as well, that they're not is as such unintentional.
Still affects 18w03a, sadly.
Affects 18w05a
Still affects 18w08b.
WHYYYY
This damn bug still affects 18w09a.
Just posting to say I'd also like to see this bug resolved.
Confirmed for 18w11a.
Confirmed in 15a and earlier.
Also missing corresponding loot table function for raw json to go with the associated set_name function:
and adds a line of lore to the list of lore.
Edit: potentially better syntax:
Confirmed for 18w20c
Can confirm for 22c.
Affects 1.13-pre6!
Affects pre-7.
Affects 1.13-pre8. Jeez Mojang. You fixed team display names, but not LORE? One of those is obviously more important...
Affects 1.13-pre10
Affects 18w31 and 32a.
Confirmed for 1.13.2-pre2.
Finally resolved in 18w43a/b
<3 <3 <3