Fireballs Get Stuck In Water
Update by [Mojang] Mega_Spud (Jay Wells)
All kinds of Fire Charges freeze when they fly under water.
Steps to Reproduce:
- Use a dispenser to dispense fire charges underwater
- Notice they travel a short distance then stop moving, and stay there
- Ghast, Blaze, and Ender Dragon fireball/charge attacks also behave the same way
Original Description:
When trying to fight with ghasts, and when the throw fireball it's gets stuck in water and doesn't disappear for a long Time. The device I'm using is Asus Zenfone go T500 LTE
Please look into this issue as there are some problems in beta build 3 ;D
Created Issue:
Ghasts fireball stuck
When trying to fight with ghasts, and when the throw fireball it's gets stuck in water and doesn't disappear for a long Time. The device I'm using is Asus Zenfone go T500 LTE
Please look into this issue as there are some problems in beta build 3 ;D
Ghasts fireball stuckFire Charges Get Stuck In Water
Update by [Mojang] Mega_Spud (Jay Wells)
All kinds of Fire Charges freeze when they fly under water.Steps to Reproduce:
- Use a dispenser to dispense fire charges underwater
- Notice they travel a short distance then stop moving, and stay there
- Ghast and Blaze Attacks also behave the same way
Original Description:
When trying to fight with ghasts, and when the throw fireball it's gets stuck in water and doesn't disappear for a long Time. The device I'm using is Asus Zenfone go T500 LTE
Please look into this issue as there are some problems in beta build 3 ;D
Update by [Mojang] Mega_Spud (Jay Wells)
All kinds of Fire Charges freeze when they fly under water.Steps to Reproduce:
- Use a dispenser to dispense fire charges underwater
- Notice they travel a short distance then stop moving, and stay there
- Ghast
and BlazeAttacks also behave the same way
Original Description:
When trying to fight with ghasts, and when the throw fireball it's gets stuck in water and doesn't disappear for a long Time. The device I'm using is Asus Zenfone go T500 LTE
Please look into this issue as there are some problems in beta build 3 ;DUpdate by [Mojang] Mega_Spud (Jay Wells)
All kinds of Fire Charges freeze when they fly under water.Steps to Reproduce:
- Use a dispenser to dispense fire charges underwater
- Notice they travel a short distance then stop moving, and stay there
- Ghast, Blaze, and Ender Dragon fireball/charge attacks also behave the same way
Original Description:
When trying to fight with ghasts, and when the throw fireball it's gets stuck in water and doesn't disappear for a long Time. The device I'm using is Asus Zenfone go T500 LTE
Please look into this issue as there are some problems in beta build 3 ;D
is duplicated by
It is also an interesting feature.
relates to
is duplicated by
relates to
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-20529
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki




Confirmed. Affects normal fire charges dispensed underwater as well.
Attached test world.
Still affects 1.6.0.5
Still affects 1.6.0.6
Still affects 1.6.0.8
This still affects versions unto this day (1.9.0+) and should be fixed as it creates large amounts of lag if unattended, and can act as a "booster" or "landmine" due to the knockback.
Still happens in 1.10 on Nintendo Switch. I had some blazes escape my XP farm and the fireballs they shot at me when I jumped in the sea to escape them just stopped and hung there. The only way to get rid of them is to detonate them by swimming in to them!
Still affects 1.11.1. it makes a great underwater mine since it will damage mobs and players that touches it!
I don't think it's a bug,the ghast fireball should be slowed by water.
Is this issue still a thing in the latest beta?
No longer occurs in 1.16.40
Resolving as "fixed" based on previous comment corroborated to me by Zeb. We are not sure in which version the behavior actually changed.