Hi! Are you still able to reproduce this on 26.3 Pre-release 1 or newer? Thanks!
Is this still reproducible in 26.3 Pre-Release 1 or newer? 🙂
Hi! Is this still reproducible with 26.3 Pre-Release 1 or newer?
Hi! Are you still able to reproduce this with 26.3 Pre-Release 1 or newer? Thanks!
Hi! It is unfortunately not intended behaviour that the Offers field can be used in predicates for trade generation. We’d love to learn more about your intended use-case for this, such that we can consider how to support in by other means? 🙂
Thank you for your report!
However, this issue is Invalid.
Your device unfortunately does not meet our minimum system requirements, and we are as such unable to provide support for it.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Hi! It looks like your trim pattern textures are missing .mcmeta files to set the base palette, which causes them to not be remapped. It's worth noting that mcmeta files are not inherited between packs - so adding these like Vanilla has should work!
Hi! Are you able to reproduce this in 26.3-snapshot-4 or newer?
Hi! Are you still able to reproduce this issue in 26.3-snapshot-4 or newer?
Closing as Cannot Reproduce given world generation formats and implementation have changed substantially since this report. Please feel free to submit a new report if this is still an issue you are encountering - thanks!
Closing as Cannot Reproduce given world generation formats and implementation have changed substantially since this report. Please feel free to submit a new report if this is still an issue you are encountering - thanks!
Hi! Are you still able to reproduce this in the latest version?
This seems to be a duplicate of MC-302549 which has been resolved, though I see you were able to reproduce this on 1.21.11-pre-1 which would have already included that fix.
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! 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!
Hi! Are you still able to reproduce this in 26.3 Pre-release 1 or newer? 🙂