When a player spawned warden either through commands or eggs (not sure if there is a difference between natural and artificial) is damaged by an exploding creeper it continues to roar constantly until it takes notice of another entity.
Linked issues
Attachments
Comments 7
This is a case of MC-250198.
Can confirm. This also relates to MC-250207.
Also, the warden doesn't indefinitely roar at the exploded creeper. It will roar until it's anger value towards the exploded creeper goes below 80. You can see this anger value easily by doing these steps
/scoreboard objectives add WardenAnger dummy
/scoreboard objectives setdisplay sidebar WardenAngerInside of a repeating command block that is always active, enter this command.
execute as @e[type=minecraft:warden,limit=1] at @s store result score AngerLevel WardenAnger run data get entity @s anger.suspects[0].angerIt seems the main issue regarding all these related reports is that the warden is trying to kill something that is no longer there. I'm thinking that the warden should retain its anger value towards the target but still roam around if that target is no longer there. Then when that target loads back in, the warden will try to kill the target again.
Confirmed in 22w17a.
Steps to replicate:
1. Get a creeper to pursue you near the warden, close enough that the warden will track the vibrations of the creeper walking.
2. Continue to lure the creeper toward you until the warden finally knows where the creeper is and begins its angry/roar animation sequence.
3. Immediately get the creeper to explode as the warden is still in or finishing up its roar sequence.
The warden will be stuck in a loop playing out its roar animation.
I was able to walk and jump around the warden within 10 blocks of it, causing lots of vibrations that it could sense, but it continued its loop several more times before it finally had enough and took me out.
Erik Broes
Can confirm.