Steps to Reproduce:
(the attachment has the world)
find a place without mob
activate a repeating_command_block with execute as @e[type=!player,type=!snowball] at @s run tp ~~~
/summon wither ~~~
/summon snow_golem ~ ~2 ~2
Observed Results:
Most of the time,the wither faces to the snow golem.It will keep under 1.20.1,but in this edition the wither spins sometimes.
It doesn't a rendering error and the sight spinning has make a lot of wither cages unsafe
Expected Results:
When a wither has a only target,it will face to the target forever.
Guess:
Interrupt of wither's target
Addition:All preview edition have solved this issue but other editions not(2023.12.18)
Linked issues
is duplicated by 1
Attachments
Comments 9
Might relate to MCPE-44178
I can't reproduce the issue in 1.21.1 (it seems like it got fixed). Is it still an issue for you in the latest beta or stable release?
it still a issue in my test of 1.21.1,maybe your test time too short to reproduce.(about a few minutes)
I could confirm in latest preview, This probably spins with out /tp command when near covered the bedrock box setup.
Does MCPE-157761 describe your issue? Seems like a generic AI freeze problem.
This ticket will reopen when you reply.
Maybe MCPE-157761 has little relationship to this.That relates to move AI but this about spin AI.Besides,a freeze should make a stable eyes line instead of spinning.
In my opinion,this issue takes place because of wither location movement AI,movement is OK but view also following is unomal,so a binding of movement and view is a error
Maybe MCPE-44178 has little relationship to this.That just like a render error.
Why do you think the Wither should not target other mobs?
What do you expect it to do instead?
Please edit the Description to include a list of steps along with the Observed and Expected results, as shown here:
Use screenshots or video to help explain (but not replace) the above information
This report has been temporarily resolved as Awaiting Response. It will automatically reopen when you add information. Please follow the format shown and include all sections (steps, observed, expected). Reports that do not contain all of the requested information and complete steps to reproduce the issue may be closed as Incomplete. For more information please read the Bug Tracker Guidelines.
You may find this Report Creation Form helpful for any future reports you create.