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!π
Thank you for your report!
However, this issue is Invalid.
This is a technical support issue; this site is for bug reports only. We do not have the resources to provide you with technical support.
Please contact Community Support for assistance and refer to this ticket by providing a link.
Quick Links:
π Bug Tracker Guidelines β π¬ Community Support β π§ Mojang Support (Technical Issues) β π§ Microsoft Support (Account Issues)
π Project Summary β βοΈ Feedback and Suggestions β π Game Wiki
This can be worked around by using stringified SNBT format (and specifying type) for the entity_data component πΒ
As with bugs such as MC-272540, data-driven registries are not reloadable. Disabling the Vanilla pack in this case works as expected, as those banner patterns can no longer exist in the world. πΒ
This is an issue with the graphics driver / windowing system. π
To specify specific data types in advancement JSON, the SNBT format (such as in the command) should be used to specify the bucket data:"minecraft:bucket_entity_data": "{Health:3d,BucketVariantTag:67502593}"
Hi! Does MC-300129 describe your issue? π