MCPE-75157Ghast face stucks on shooting face after loosing track of the player
When fighting a ghast you will observe his shooting face can remain after it looses contact wil you. If you leave and come back the ghast will still have this face and can shoot imediatly bakc at you without charging a new fireball and making the sound before shooting. That means already charged ghasts are silent wheapons and they are so hard to observe since they dont make the sound of charging up a new fireball to shoot.
Linked Issues
Created Issue:
Ghast face stucks on shooting face after loosing track of the player
When fighting a ghast you will observe his shooting face can remain after it looses contact wil you. If you leave and come back the ghast will still have this face and can shoot imediatly bakc at you without charging a new fireball and making the sound before shooting. That means already charged ghasts are silent wheapons and they are so hard to observe since they dont make the sound of charging up a new fireball to shoot.
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
duplicates
![[Mod] GoldenHelmet](../../../data/avatars/users/18951.svg){kind=small}
I have updated the parent ticket. Our bot, Arisa, also now auto-updates affected versions based on duplicate reports being linked.
Same
Elizabeth, of cousre its the same.. its a bug that happens on all devises and worlds. Vote this report so it gets resolved quicker...
Thank you for your report!
We're tracking this issue as MCPE-45311, 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 reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Golden helmet. the bug you mentioned as tracked is outdated.... Please update the version because it says it happens on 1.11 and 1.12 but it happens on 1.14 and 1.16 betas as well!
I have updated the parent ticket. Our bot, Arisa, also now auto-updates affected versions based on duplicate reports being linked.