What I expected to happen was...:
If you put "item_name" in the item component and hit the give command, you would have gotten a custom potion with the original name.
What actually happened was...:
But what we actually got were "Uncraftable Potions".
Steps to Reproduce:
1. Type the command "/give @p minecraft:potion[minecraft:item_name="aaaaa"]".
2. I have "Uncraftable Potions" on hand.
PS: "/give @p minecraft:potion[minecraft:custom_name='{"text": 'aaaaa', 'italic':false}'" This will solve the problem, but it is only a stopgap method.
There may be something about my English that is not very good, but that is because I am not an English speaker. Of course, I am using a translator for this English text.
Linked issues
is duplicated by 3
Attachments
Comments 3
Thank you for your report!
However, this issue is Working as Intended.
The report you have submitted is working as intended: see the 24w37a changelog:
minecraft:item_name
Name provided by this component always has the lowest priority
That means it will be overriden by components like
minecraft:potion_contents
Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.
Full Version History – Snapshot Version History – Feature Requests and Suggestions
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
WAI per changelogs, item_name has lower priority than potion_contents' name setting