gegy

Thank you for your report!
After consideration, the issue is being closed as Won't Fix.

Please note that this is not the same as Working as Intended, as this bug report correctly describes behavior in the game that might not be the intended or desirable behaviour, but it will not be fixed right now. Sometimes, this is because the issue reported is minor and/or impossible to change without large architectural changes to the code base.

If you'd like to post a suggestion or give further feedback, please visit the Minecraft Feedback Site or choose a link below.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Thank you for your report!
After consideration, the issue is being closed as Invalid.

You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit The official Minecraft feedback site or visit the Minecraft Feedback Discord server.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

Hi! Can you attach a screenshot of the issue present with F3 visible? Thanks!

It looks like these players both changed their usernames - so the UUIDs are correct, even if the name outdated for their accounts. 🙂
If they were to join again, these would be updated in the usercache JSON.

Hi, thanks for the report! 🙂 It looks like there is a remaining issue here with the SNBT form of entity data - I’ve reopened the issue as this should be addressed, but you should be able to work around it for now by updating the selector syntax:

"when": {
  "id": "minecraft:item_frame",
  "Invisible": true
}

Hi! Does MC-300129 describe your issue? 🙂

Hi! Is this still present in 1.21.8 Release Candidate 1 or newer?
We were not able to reproduce this issue specifically ourselves, but fixed some related issues on Intel graphics cards in this Release Candidate which we believe could be related. 🙂
Thanks!

This bug only affects names of items inside of entities (but not the player). If you are seeing a different issue, a new report would be best 🙂

Thank you for confirming that you are still experiencing this issue! It seems like there have been two separate issues with crashes on AMD graphics cards. The one fixed in the Release Candidate 2 we will keep tracked in this bug, and track the issues you are still experiencing in MC-299144.

Hello! Thank you for this report - we have been investigating this issue, and encountered some other problems on an ARM64/Windows device. Are you by any chance experiencing these same issues on your devices? 🙂

• Selecting text (for example in the creative inventory search) causes many other UI elements to appear fully white, pink, or cyan

• Selecting text in a Book & Quill causes the game to crash

• The screen intermittently flickers with a fully black frame

This is likely an issue with the “Boosted Brightness” Resource Pack you are using, it has not been updated to the latest version. 🙂

The equippable component is missing the `equip_on_interact` field, if this is included it can be equipped as expected. 🙂

Dialogs are supported in configuration phase, but from the log (Expected non-null compound tag) it looks like some malformed data is included in that packet. 🙂

In configuration phase it is not possible to send a dialog by id as registries are not yet initialised, they must all be sent inline.

Hello! Could you please attach the Resource Pack and command/text component you are using to trigger this issue? Thanks!

Hi! We have just published 25w21a, which contains some changes that might affect the crash that you are seeing. Can you please try running this snapshot version, and check if the issue still occurs?
Thanks!

The written_book_content component predicate can be used to match the resolved field without comparing item NBT 🙂

The changelog is incorrect, but will be fixed for the full release - thanks for the report!

This issue and MC-276585 will alternate in presence between snapshots and full releases - we try to be more strict with catching crashes in full releases. As they’re the same underlying issue, can they be merged back into the original issue? Thanks!

Are you able to reproduce this still on pre5? The crash report should contain more details about what went wrong. 🙂

Do any of the data packs you have installed affect world generation? Are you able to reproduce this issue without any data packs?

Thanks!🙂