Ender dragon consists of 9 entities in total
The bug
This happen since 19w08a.
When summoning an ender dragon with /summon command or spawned in end it will spawn 9 times all fixed to one.
How to reproduce
Spawn an ender dragon
/summon minecraft:ender_dragon
Kill the ender dragon
/kill @e[type=ender_dragon]
And the message appear "Killed 9 entities".
Linked Issues
is duplicated by8
Created Issue:
Ender dragon spawn 9 times instand 1 times
The bug
This happen since 19w08a.
When summoning a ender dragon with /summon command or spawned in end it will spawn 9 times all fixed to one.
How to reproduce
Spawn an ender dragon
/summon minecraft:ender_dragonKill the ender dragon
/kill @e[type=ender_dragon]And the message appear "Killed 9 entities".
The bug
This happen since 19w08a.
When summoning a ender dragon with /summon command or spawned in end it will spawn 9 times all fixed to one.
How to reproduce
Spawn an ender dragon
/summon minecraft:ender_dragonKill the ender dragon
/kill @e[type=ender_dragon]And the message appear "Killed 9 entities".
The bug
This happen since 19w08a.
When summoning a ender dragon with /summon command or spawned in end it will spawn 9 times all fixed to one.
How to reproduce
Spawn an ender dragon
/summon minecraft:ender_dragonKill the ender dragon
/kill @e[type=ender_dragon]And the message appear "Killed 9 entities".
duplicates
relates to
duplicates
Ender dragon spawn 9 times instand 1 times
The bug
This happen since 19w08a.
When summoning a ender dragon with /summon command or spawned in end it will spawn
9 times all fixed to one.How to reproduce
Spawn an ender dragon
/summon minecraft:ender_dragonKill the ender dragon
/kill @e[type=ender_dragon]And the message appear "Killed 9 entities".
The bug
This happen since 19w08a.
When summoning an ender dragon with /summon command or spawned in end it will spawn 9 times all fixed to one.
How to reproduce
Spawn an ender dragon
/summon minecraft:ender_dragonKill the ender dragon
/kill @e[type=ender_dragon]And the message appear "Killed 9 entities".
Moderator note is for that ?
is duplicated by
Ender dragon spawn 9 times instand 1 timeEnder dragon spawn 9 times instead of 1
Ender dragon spawn9times instead of1Ender dragon spawns nine times instead of only once
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Ender dragonspawns ninetimes instead of only onceEnder dragon consists of 9 entities in total
is duplicated by
is duplicated by
relates to
relates to
In short:
At least ender dragons summoned without a DragonPhase seem to be able to "bug out" and be positioned at x=NaN, y=NaN, z=NaN.
If a player teleports to that dragon, the worldsave crashes and you get the info:
"[Server thread/INFO]: <Playername> lost connection: Invalid move player packet received"

Upon trying to reenter, you enter the world very briefly, then get kicked with the same message, and your worldsave will be unplayable.
No crash report gets produced.
Video proof
Detailed:
To check on my bugposts related to ender dragons, I entered one of my according bugtest worldsaves.
In this worldsave is a (non-moving) dragon already waiting, summoned with /summon ender_dragon ~ ~10 ~
This time I did not see it and at first thought it was a visual problem (see https://www.youtube.com/watch?v=-7UESPgjZME)
I teleported to the dragon with /tp @s @e[type=minecraft:ender_dragon,limit=1], not knowing that it was at position NaN.
Then the crash occured:
[Server thread/INFO]: Meri lost connection: Invalid move player packet received
Worldsave is unplayable now, but I always make backups upon entering with a new MC version.
Last time I had entered this worldsave was in 19w07a.
I don't know what changed since then that the Dragon will be now located at NaN/NaN/NaN if it was not summoned with a DragonPhase.
This also evidently happens to not only newly summoned dragons, but also those which have been already summoned in an older worldsave.
Log
[15:35:13] [Server thread/INFO]: Scanning for legacy world dragon fight... [15:35:13] [Server thread/INFO]: Found that the dragon has been killed in this world already. [15:35:13] [Server thread/INFO]: Found that there's a dragon still alive (arw['Ender Dragon'/1515, l='Dragon Test', x=NaN, y=NaN, z=NaN])
This crash/bug is reproducible with the attached worldsave Dragon Test_Crash-Reproduction.zip
.
How to reproduce
- Enter worldsave
- Note that there is a dragon boss bar, but you can't see a dragon.
- Teleport to dragon:
/tp @s @e[type=minecraft:ender_dragon,limit=1]
You'll lose the connection/get kicked with "Invalid move player packet received"
- Try to reenter the world, you'll be able to, but only for a very short time.
Note that in the log it'll look similar to this:<Playername> logged in with entity id 165 at (NaN, NaN, NaN)
and you'll get kicked immediately again.
Screenshot of player position NaN
Side note:
I don't know why, but when I summon an ender dragon and then kill it, it removes 9 entities. No matter if the dragon got summoned with or without a DragonPhase. (MC-146503)
Haven't searched yet if this was already reported; display of 9 killed entities confirmed by [Mojang] Panda.
/say @e[type=ender_dragon] also has 9 outputs, and all of them also have a different UUID, even though you only summoned 1 dragon before.
This happens also in freshly created worlds, be it the Legacy dragon or a freshly summoned one, when you execute the kill-command, it will find several dragons
with different UUIDs and you'll be able to execute the kill-command several times. The amount seems to vary, so far it was either 6 or 7 or 9 times for me.
This happens regardless of the "Rotation" NBT tag. Also, there being 9 total dragon entities is another issue that won't be fixed, MC-146503. I removed both points from the ticket and made it focus on the ender dragon spinning when summoned.
Thank you for your report!
We're already tracking this issue at MC-146503, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved. That means that this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-146503, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved. That means that this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're tracking this issue as MC-146503, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as won't fix, which means this is not considered a bug and won't be fixed.
If you haven't already, you might like to make use of the search feature to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-146503, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automagically! Please report any issues in Discord or Reddit
Thank you for your report!
We're tracking this issue as MC-146503, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as working as intended, which means this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-146503, which has been marked as Won't Fix - while this behaviour is not desirable, the developers have said that they will not or cannot fix it.
Please use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
Relates to MC-146503.
The "/damage" command does not inflict damage on ender dragons. However, it functions properly against all other entities, including non-living ones like items.
Steps to replicate
- Enter the End dimension
- Regenerate the ender dragon if it has been previously slain
- If
MC-146503was not fixed, you would execute the command:/execute as @e[type=minecraft:ender_dragon] run damage @s 200 minecraft:arrow
Alternatively, you can run:
/damage @e[type=minecraft:ender_dragon,limit=1] 1 minecraft:arrow
Observed behavior: The ender dragon showed no signs of damage, as evidenced by the absence of sound, its failure to turn red, and the boss bar remaining unchanged.
Expected behavior: The ender dragon should have taken damage, resulting in it turning red, emitting the damage sound, and updating the boss bar.
Although MC-146503 has been resolved, I am still able to replicate this issue in 24w12a.




Please don't fake moderator notes.
Confirmed. This likely happens because (or is a side effect) of the dragon having 9 hitboxes. If you enable F3+B, you can see that the dragon consists of 8 hitboxes contained inside of the main, big hitbox.
Why "Wont Fix" it was not the case in 1.13.2 and before.
Why it's resolved as "Won't Fix" any explication ?
works as intended would be better than "won't fix", saying wont fix as if its not important
Well, it doesn't work as intended, so that resolution doesn't make sense.
I cannot replicate this problem in snapshot 24w11a. It appears that it has been resolved at some point, even though it was marked as "won't fix."