More or less what it sounds like, dragons breath does damage to the player like 2-3 times a second, and usually around 3 hearts per hit. So its pretty much instant death, with very little chance of escaping the acid.
When compared to java, this is extremely broken, as the breath over there only does damage once every second, or second and a half. Even with that amount of delay, its still very effective at killing people🙂
Another side effect of this massive amount of damage bug, is a huge amount of knockback. You can easily fly 20 blocks just from touching some of the breath, and its strong enough to launch you about 5-6 blocks into the air.
Linked issues
is duplicated by 11
MCPE-43211
Ender Dragon Breath attack doesn't apply damage immunity and has buggy knockback and duration
Resolved
MCPE-46120
Dragon Fireball is overpowered
Resolved
MCPE-46798
Ender Dragon fireball is very buggy.
Resolved
MCPE-57647
Ender Dragon's Breath is BROKEN!
Resolved
MCPE-58339
Almost instant death in end
Resolved
MCPE-67901
Ender dragon fight
Resolved
MCPE-68607
Dragon breath insanely powerful
Resolved
MCPE-71994
Bug With Ender Dragon - Insta kill dragons breath
Resolved
MCPE-73008
You guys need to fix the over powered ender dragon breath bomb.
Resolved
MCPE-76920
Ender Dragon Kills Me in less than one second even with armour/totem of undying
Resolved
MCPE-82025
Ender Dragon fireballs ignore Hurt Time
Resolved
relates to 2
Comments 35
It tears thru notch apples, and armor.
Still an issue on 1.11
What about update?
This was for me like:
You died! 😐
What? What's with that...? Is that intentional?! It feels really unbalanced...
Why does the cloud even have knockback? That makes no sense.
This is way overpowered and makes dragon fights annoying and not fun
I could never understand Java players when they say the bosses are too weak. In the bedrock versuon, the fight against them always means the dead. I have to die three or four times until the dragon dies, the one against the acid I can not survive. Fluke as skilful as I am, the acidity is unpredictable.
If that is the intention, please reconsider it.
Still not fixed in 1.12 :/
I used two totems at once and I still died instantly xD
Please please PLEASE! fix dragons breath. I hate going to the end because of this. I died 20 times trying to kill the dragon, lost so much gear and nearly rage quit MC all together. There are a lot of bugs in the End but this one is the worst and kills the fun of the game since you can't get any shulkers or elytra until you kill the dragon.
This STILL effects 1.14.20 and has been in the game for longer then just 1.8
I have seen this bug on Android and Nintendo Switch and it NEEDS to be fixed, the dragon is a big part of the game and this bug is ruining the fight.
Can confirm 26th February 2020.
Still exists. Had been treating my world like a hardcore world (one life), full prot IV armour + regeneration effect (from potion) - but still torn to pieces within seconds.
EDIT : This occured on Nintendo Switch.
Toycat has had this issue. It negatively impacts speedruns. https://www.youtube.com/watch?v=o47wJKyD5yY&t=41m30s
I've encountered several dragon related issues in the end today.
First, when the dragon was hovering above the portal it threw a fireball at the ground in front of it, but i took damage at least 30 blocks away, when i came went back the breath particles were where i'd been standing instead of in front of the portal.
Also, sometimes the breath is invisible. You'll be hit by seemingly nothing, and die close to instantly.
Also, may be unrelated, but upon dying once my game crashed, when i came back i was standing in a different spot, and my helmet and bow had been duplicated.
These issues made my speed run a lot harder than it ought have been.
... I also had a lot of problems (Version 1.14.30):
the damage to the breath is far too high. I have had four beacons of healing, resistance, strength and speed in the area and full dia armor. Even a totem of immortality doesn't help. It is triggered but the death is faster ... immediately.
The breath of the dragon is sometimes not seen. Sometimes "nothing" causes damage, sometimes you could see the purple particles but you couldn't collect them and they caused damage only late ... and but immediately fatal.
No matter whether I harmed the dragon, after my death it had healed again. Impossible to win like that. -> I had to cheat.
last I got a (further) dragon egg ... ???
Please fixes it
@unknown: Please try to do your editing before you submit your comment, so you don't spam dozens of watchers with multiple emails. You might find it helpful to switch between the Visual and Text editing modes.
Last Wednesday, this issue was fixed in 1.15.0.55. The fix should arrive for everyone once 1.15 is officially released.
Actually 1.15 will be merged into 1.16 as the version number 1.15 has been skipped. So the fix should arrive in 1.16 release.
Yes,I suffered a lot before this change.I want the dragon's breath and fireball's acid work like that in Java edition which one hit every second and three hearts per hit.
Confirmed! I fight the dragon. The health bar is gone. I have a hard time bed-killing the dragon because there is invisible dragons breath next to the portal(empty)
The issue with invisible dragon breath is actually being tracked in MCPE-51214.
Fixed in 1.16 beta
I badly want to beat the ender dragon but i cant until this bug fix. Were counting on you mojang 🙂
It is broken on PS4 bedrock to, I was on my main survival world that I have been working on for 5 years or so and I re-spawned the Ender Dragon to fight it again to get another portal to the end Islands so I could get another elytra and I was prepared beyond belief. I had maxed out protection on all my Diamond gear, maximum sharpness on my sword to and, I had a few golden apples. And then the Ender Dragon shot ONE Fireball and KILLED me INSTANTLY. After that I re-spawned and found that none of my loot was there I'm not sure if this is part of the same bug but it's still very bad. By the way I got back to the end in 2 minutes, NOT five minutes which is the normal time it takes for items to despawn. Luckily I had online backups. But please fix.
(I'm not sure if the previous message worked so here's another)
@The Lonesome chicken it is already fixed in the beta. You have to wait until 1.16 releases then you'll no longer have this issue.
@unknown: People often think the 5-minute despawn timer starts counting down when you hit the Respawn button on the death screen, but this is incorrect. It starts the moment you die, so if you leave the death screen up for a while (e.g. it seems like a good time for a short break), the remaining lifetime of your items is getting shorter during that time. In fact, if you leave the death screen up for the full 5 minutes, you can often see your items disappear in front of you.
If you hit Respawn right away, and assuming your respawn point is in the Overworld or at least some distance away from where you died,, the chunk(s) containing your items are unloaded so their despawn timer stops counting. This is the best way to ensure you get the full 5 minutes.
Affects 1.16.100.54 Beta
her normal in the easy way is to take 1 heart out of life? if not, this is happening in the latest official version (1.16.40).
another thing that happened to me is that sometimes the dragon’s breath didn’t hurt me.
The damage done by dragon's breath depends on how much contact you have with it and for how long. You can reduce the damage from dragon's breath spreading toward you by placing a block and stepping on it, putting you above the vapor. So there's no simple number that can be called a "normal" amount of damage, and in many cases it's easy to imagine you avoiding damage at all. But the developers have assured us that it has been fixed so we'll continue assuming it has been fixed unless we get conflicting results from a reproducible experiment.
Can someone help me? When the Dragon's Breath particles are gone, they still do damage. No matter how much time I wait, there is still a damage. What should I do? (I'm on MCEE 1.14.50
@unknown: Note that, while commenting here wasn't a mistake, this is an old problem that was fixed some time ago for the regular Bedrock release. We normally don't keep a close watch on resolved tickets, and it's only by coincidence that I still have this one on my watch list due to an oversight. If you should have a similar problem in the future, raising your question on the Mojira Reddit or the Mojira Discord is likely to get you a quicker response.
You are having this problem because the fix to the Bedrock codebase was issued in 1.16, and Education Edition remains at an earlier release. Because EE is designed for classroom use, where instructors and students all have to have coordinated release levels, putting out EE updates follows a different procedure than the retail game, and apparently EE is several months behind. I'm pretty certain the fix will be included in a future release, though I have no confirmation of that fact right now nor information about when such a release might be issued. I have asked Community Management whether we should reopen this ticket, ask you to create a new bug report, or simply ask you to wait for a release. I will update here when I receive an answer.
If it's feasible for you, you could get around this problem by moving the world to the current retail version of Minecraft. I'm not sure exactly how you would do that, since I don't have EE, but it would involve exporting the world to a .mcworld file, then opening that file on a computer that has the retail version. (Note that this would create a new copy of the world and you would not be able to return it to EE later.) If the procedure I'm outlining isn't familiar to you, I'm afraid I probably can't explain it any further, but you might try asking your teacher for assistance or asking for help on the Minecraft Discord.
@unknown - thanks for getting in touch. If you are having this issue on the Education Edition only, then please let your education provider know directly. You might wish to visit the Education Edition site for more information: https://education.minecraft.net/
This isn't fixed it is still instant kill
What if you wear armour? 🙂