If you utilize a custom spawn egg that typically summons a different entity type, it ceases to function properly following a world upgrade to a 1.20.5 snapshot, likely due to changes in the item storage system. For instance, if you acquire a spawn egg using the command:
give @p husk_spawn_egg{EntityTag:{id:"minecraft:llama",Glowing:1b}} 1The husk spawn egg initially spawns a llama with the "Glowing" NBT tag set to 1. However, after the world upgrade, it will instead spawn husks rather than llamas. Nevertheless, other custom data from the spawn egg, such as the "Glowing" NBT tag in this scenario, remains intact.
Steps to Reproduce
Execute
/give @p husk_spawn_egg{EntityTag:{id:"minecraft:llama",Glowing:1b}} 1in version 1.20.4.
Utilize the spawn egg to spawn glowing llamas as anticipated.
Upgrade to the latest snapshot.
Use the spawn egg again
Observed Results: The spawn egg no longer summons glowing llamas but rather glowing husks.
Expected Results: The item's data should convert to the new system, allowing the husk spawn egg to continue spawning llamas as intended.
Linked issues
relates to 1
Attachments
Comments 3
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 behavior, 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.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Can confirm,
this is the case for a lot of items, not just custom spawn eggs, taking use of custom nbt data, as they aren't compatible with the new component system.