-
Bug
-
Resolution: Works As Intended
-
None
-
22w19a
-
None
-
Confirmed
-
(Unassigned)
The bug
Sculk shriekers with "can_summon" set to true don't shriek if a warden is nearby, which prevents them from alerting the warden if a sculk sensor triggers it or if the player steps on it. This doesn't happen with player placed shriekers (can_summon: false), as they do in fact send a vibration to the warden after they shriek and thus get angered at the player.
Not sure, but this might be due to shriekers not triggering when a warden is nearby to prevent another spawn, however this shouldn't be an issue if the warden spawn is just cancelled after the player triggers the shrieker, so this way it is able to alert them like their "can_summon: false" counterpart.
Expected result
Triggering a sculk shrieker nearby a warden would shriek and thus alert the warden.
Observed result
The shrieker is blocked as long as there's a warden nearby, preventing it from shrieking even if it receives a sculk sensor signal.
How to reproduce
- Summon a warden, trap it and place a sculk shrieker nearby, with "can_summon: false".
- Place a sculk sensor far from the warden but in a way that only triggers the shrieker.
- Make sure you're on survival and trigger the sculk sensor.
- Notice how the sensor sends a signal to the shrieker, which shrieks and sends a signal to the warden, getting angered.
- Now replace the shrieker with another with "can_summon: true".
- Trigger the sensor again.
- Notice how now the shrieker doesn't do anything even though it got a triggered by the sensor.