Fireball is not correctly positioned when shot by ghast
- You can see when the ghast shoot a fireball, it appears a little above the head instead of being in the mouth
Device: LG K10
Linked Issues
is duplicated by6
- Fixed
Lio- 68
- 12
- Confirmed
- 349985
- Multiple
- Android 6.0
- fireball ghast position
1.19.80.24 Preview - 1.18.12 Hotfix
1.19.80.24 Preview 1.19.80.23 Preview 1.19.80.22 Preview 1.18.30.29 Preview 1.18.30.28 Beta 1.18.30.27 Preview 1.18.30.26 Beta 1.18.30.23 Preview 1.18.30.22 Beta 1.18.20.30 Preview 1.18.20.28 Preview 1.18.20.29 Beta 1.18.20.27 Beta 1.18.20.25 Beta 1.18.20.24 Preview 1.18.20.23 Beta 1.18.20.22 Preview 1.18.20.21 Beta 1.18.10.22 Beta 1.18.10.21 Beta 1.18.10.20 Beta 1.18.0.27 Beta 1.18.0.24 Beta 1.17.40.23 Beta 1.17.11 Hotfix 1.16.210.54 Beta 1.16.200.55 Beta 1.16.100.60 Beta 1.16.100.55 Beta 1.16.100.52 Beta 1.16.100.51 Beta 1.16.100.50 Beta 1.16.20.54 Beta 1.16.20.53 Beta 1.16.20.52 Beta 1.16.20.50 Beta 1.16.0.68 Beta 1.16.0.67 Beta 1.16.0.66 Beta 1.16.0.64 Beta 1.16.0.63 Beta 1.16.0.61 Beta 1.16.0.60 Beta 1.16.0.59 Beta 1.16.0.57 Beta 1.16.0.58 Beta 1.16.0.55 Beta 1.16.0.53 Beta 1.6.0.5 1.6.0.6 1.6.0.8 Beta 1.6.0.30 Beta 1.7.0.2 Beta 1.7.0.9 Beta 1.14.60 Hotfix 1.16.0 1.16.20 1.16.40 Hotfix 1.16.221 Hotfix 1.18.0.25 Beta 1.17.41 Hotfix 1.18.0 1.18.1 Hotfix 1.18.2 Hotfix 1.18.10 1.18.30.21 Preview 1.18.30.20 Beta 1.18.12 Hotfix- 1.20.0.20 Preview 1.20.0
Created Issue:
Fireball is not correctly positioned when shot by ghast
- You can see when the ghast shoot a fireball, it appears a little above the head instead of being in the mouth
Device: LG K10
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
relates to
Thank you for your report!
We're actually already tracking this issue under MCPE-35202.
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 – 📖 BDS Wiki – 📖 FAQs
Thank you for your report!
We're actually already tracking this issue at MCPE-35202, so I will resolve and link this ticket 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
Thank you for your report!
We're actually already tracking this issue at MCPE-35202, so I will resolve and link this ticket 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
Thank you for your report!
We're actually already tracking this issue at MCPE-35202, so I will resolve and link this ticket 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
Thank you for your report!
We're actually already tracking this issue at MCPE-35202, so I will resolve and link this ticket 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
Thank you for your report!
We're tracking this issue in MCPE-35202, 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:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
This likely happens due to a collision between the fireball and the blaze. Fireballs are indeed entities like mobs. They are affected by collision with mobs (unlike items) because entities\small_fireball.json contains the line
"minecraft:pushable": { "is_pushable": true,
It seems debatable whether blaze fireballs should have this property at all, since fire is immaterial. It may just be a default that was put in the small_fireball.json without consideration. XP orbs and player-thrown tridents have the same issue (MCPE-87711 and MCPE-60895). Ghast fireballs have collision as well, but that makes sense because ghast fireballs explode desctructively, which would seem to imply lore-wise that they contain a core of explosive material. If blaze fireballs are supposed to more like pure fire (as I imagine them to be), then I can't see why they'd be pushable. Moreover, ghast fireball collision is important for some technical contraptions like cobblestone farms and tree farms, but I am not aware of any tech based on blaze fireball collision.
Aside from the issue of fireballs having collision, this bug might alternatively be attributable to the offset used for spawning blaze fireballs. That is, given that fireballs have collision, a blaze's fireball probably bounces backward when the blaze is against a wall because the fireball originates from inside the blaze's head. My guess is that when the blaze is against a wall the fireball "hits" the wall immediately after being spawned and loses its forward momentum, and then before it can be despawned on the next tick it gains momentum in the opposite direction from the wall due to overlapping the blaze collision box.
It is possible to set blaze fireballs to originate from the edge of the blaze's body (where I'd imagine they come from) by using something like this for the offset (compare my solution for MCPE-35202):
"offset": [ ".25 * math.sin(query.body_y_rotation)" , .5, ".25 * math.sin(query.body_y_rotation - 90)" ]
I could confirm, Relates to MCPE-35202
Cleaning up old tickets: This ticket has not been updated recently (~7 months+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue and is affecting the most recent versions, then please comment, or create a new ticket following the Issue Guidelines.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
This issue is certainly still around, and can be pretty easily tested even in the recent 1.16.0.58 nether update beta. Since its the nether update, seems like a perfect time to fix up ghasts
I think this bug also makes it so the ghast often misses where its firing, so that the player can stand perfectly still, and the ghast will never be able to shoot you.
Here is some footage of this bug in action: https://youtu.be/aKaxK2xAWJI?t=396
I will confirm this later today, but it should look much better in the betas than in 1.14.60 since
MCPE-44326was fixed. It just so happens that the fireball is offset even more than the ghast hitbox box used to be.I don't know why people say that ghasts have inaccurate range.every time a ghast shoots at me,its always at me.so I don't know whether this is fixed or this just me because even in 1.14.60,ghasts were fine in this description
This is still an issue in 1.16.0.64, to reproduce just summon a ghast and have it fire at you, once it gets high enough the shots will start going over your head, they only hit if the ghast is roughly the same elevation as the target.
1.16.0.64 is already in the Affects Version/s list.
Affects 1.16.200.55 Beta.
Affects 1.16.40 Hotfix.
The position of a fireball when shot by a ghast is determined by the "offset" parameter in the "minecraft:projectile" component in \entities\fireball.json. To make the fireball come from the ghast's mouth the offset should be
"offset": [ "2 * math.sin(query.body_y_rotation)" , -3.25, "2 * math.sin(query.body_y_rotation - 90)" ],I have attached a behavior pack (Ghast fireball alignment.mcpack
) that fixes the bug by adding a component group that contains a version of "minecraft:projectile" with the above offset, and a filter in the "entity_spawned" event that adds that group if the fireball is spawned by a ghast. This allows "ghast" fireballs shot by other entities to still use the default offset.
Affects 1.17.40.20