-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Minor
-
None
-
Affects Version/s: None
-
None
-
Environment:
1.16.4 java 13
-
1.16.4
-
Any usage of the basecomponent API (itemMeta.getLoreComponents() in this case)
-
Yes
Chat component extra and text properties are saved in wrong order.
What behaviour is expected:
"extra" chat components should save before "text" properties, vanilla code: https://media.discordapp.net/attachments/555462289851940864/798259050840064020/unknown.png?width=1440&height=600
What behaviour is observed:
text properties save before extra chat components, net.md_5.bungee.api.chat code: https://media.discordapp.net/attachments/555462289851940864/798258968853348362/unknown.png?width=1440&height=393
This results in invalid, unstackable items.
vanilla NBT:
{"extra":[{"text":"Some line in weapon lore"}],"text":""}
BaseComponent saved NBT:
{"text":"","extra":[{"text":"Some line in weapon lore"}]}
There may also need to be some kind of datafixer for pre-existing invalid items to reverse the save order back to vanilla.
