As of 1.21.5, empty keys in raw NBT generated from heterogenous lists in JSON are no longer exposed in SNBT, and empty keys in NBT paths and JSON compounds (representing arbitrary NBT data) are now illegal/invisible making it impossible to create them naturally. This means that all issues described in this bug report are handled without issue now.
The only place that empty keys could still be written is when the game writes compounds which are outside of that abstracted raw NBT structure - i.e. compounds that are artificially given an empty key or were given one in a previous version of the game. From what I can gather from comments by certain devs, and the nature of the recent changes, this case seems to be somewhat “unsupported“ and cannot naturally be achieved anymore so is not really relevant to the bug report.
I believe this report should now be marked either as Resolved or WAI.
@MrMuskle I updated my graphics drivers as requested and the issue was resolved 👍
Confirmed
Correction: It doesn’t just make the border brighter, it makes the whole tooltip opaque 🙂
This is simply outdated syntax. The correct syntax would be
/tellraw @a ["",{text:"try click this link here",click_event:{action:"open_url",url:"https://bugs.mojang.com/"},color:"aqua"}]
which works as intended.
Can confirm
Yes this could be considered MC-274632 but it pertains specifically to the latest changes which spread the issue to far more places as text components in NBT appear everywhere, including item stacks, entity data, etc.
Confirmed in 1.21.4 Pre-Release 3
Nevermind, this is entirely innacurate in a vanilla environment. My bad
This also affects leather armour, dyed wolf armour, potions, tipped arrows, coloured firework stars, grass blocks, and all types of tinted foliage. This would in theory also affect spawn eggs but, due to MC-269723, that cannot be observed. This also does not affect azalea leaves which the current description seems to suggest.
I've uploaded crash-2024-10-16_15.26.28-server.txt which happened in 1.21.2 Pre-Release 5 🙂
I will update the server as soon as possible and stay vanilla and let you know as soon as we get another crash 🙂
Happened again whilst running a vanilla dedicated server in Pre-Release 4
I can reproduce this issue. Notably if there are any normal glyph characters in that line of text then the sprites render as expected.