mojira.dev
MC-311956

Editing sculk shriekers' `shrieking` block state property using debug sticks causes it to be set to the value opposite to the selected one

Changing the sculk shrieker's shrieking block state with the debug stick consistently applies the opposite value. Selecting true changes the block state to false, while selecting false changes it to true. During my testing, the can_summon and waterlogged block states behaved normally and were not reversed.

Steps

  1. Obtain a debug stick with commands

  2. Place a sculk shrieker

  3. Use the debug stick on the sculk shrieker with left-click until the selected property is shrieking

  4. Toggle the value with right-click

  5. Activate the sculk shrieker

  6. Observe the displayed block state

Observed Results

Selecting true changes the block state to false, and selecting false changes it to true.

Expected Results

The selected value and the applied block state should match.

See the attached video demonstration: https://youtu.be/CzGnFvgtnd8

Environment

Windows 11

Comments 3

During further testing, I also found that when can_summon is set to true, selecting shrieking = true (which behaves as false according to this report) prevents the shrieker from summoning a Warden. Other value combinations with can_summon = true summon the Warden normally, including both waterlogged values.

I think this report will be probably resolved as invalid, since issues relating with the debug stick are not supported

I was unaware of that, thanks for letting me know. It’s not a big deal if it is, it was just something I discovered while messing around with sculk shriekers and thought it was interesting lol

S_Mania

(Unassigned)

Confirmed

Platform

Low

Debug

26.3

Retrieved