When a Shrieker begins shrieking, there is a delay of about 4 seconds before the darkness effect takes place and then the Warden starts crawling out of the ground several seconds later. However, if a Shrieker that is in the process of summoning is broken during the shriek, darkness falls immediately, and the Warden begins to appear without any delay at all.
Is this intentional? Shouldn't it take exactly the same time to appear, regardless of the fate that befalls the Shrieker that summoned it?
Here's a video illustrating the phenomenon. He corrected himself about the "aggro" part, but I sadly didn't get that part of the clip. The Warden isn't "aggro" at that point, it just appears way earlier than it would have had he not broken the Shrieker. The user in the video is playing on version 1.20.1, but I was able to reproduce this in a 1.20.2 world.
Comments 2
"The behavior of the warden appearing when the shrieker is broken is expected." - Jiingy
I am NOT reporting that it shouldn't spawn at all (as you appear to believe.) My report is about timing. I am saying that it shouldn't spawn faster than it does when the shrieker is left intact. I'm not sure why that was unclear from what I wrote, but here's another way of putting it:
It makes no sense that the warden should suddenly appear much more quickly when the shrieker that made the sound is broken. The sound has already been made. The warden should take the exact same amount of time to respond to that shriek no matter what happens to the shrieker that made it. It should be based on the time that the sound first happens, not any other factor.
Shriek begins... 4 seconds later, a warden crawls out of the Earth. No other factors should have any affect on that timing. It shouldn't be able to be stopped, and it shouldn't be able to be accelerated. Once the shriek happens, you should always get a warden, and it should always take exactly the same amount of time to occur. I am reporting that acceleration as a bug, not that the warden appears at all.
Now is my report clear?
This issue is invalid based off of MC-262231 which was resolved as a feature request. The behavior of the warden appearing when the shrieker is broken is expected.