Background:

When using creative mode to 'pick block' to grab a copy of either type of sculk (calibrated or regular) sensor with its NBT data, it records the position of the sculk sensor within that data.

An example of such might look like this, referring to "source:{pos:[I;x,y,z]...}"

minecraft:sculk_sensor[ . . . ]{ . . . ,listener:{ . . . source:

{pos:[I;10638,64,10840],type:"minecraft:block"}

}}

This appears to have been introduced in 22w12a (2022 March 24 - 1.19 snapshot) with the introduction of sculk shrieker functionality, and this location data is not present in 22w11a.  Coinciding with this, the following bug cannot be reproduced in 22w11a, but can be reproduced in 22w12a and later up to the current versions/snapshots.

The Bug:

Once the copied sensor with its attached NBT location data is placed down anywhere within a 3x3 chunk region centered on the original sensor, it will be in a glitched state where it will never activate from any vibrations.  The sensor will only respond to a player standing on top of the sensor.  Upon an area unload and reload, the glitched sensor will go into a further glitched state where activating the original sensor that was copied, will activate the glitched sensor.  Removing the original sensor and creating vibrations around the empty space that had the original sensor, will continue to activate the glitched sensor, as it still contains the original position data.

Steps to Reproduce:

1. Go into creative mode and place down any type of sculk sensor.
2. Pick block by using ctrl + middle click to copy the sensor and its NBT data.
3. Move to a different location, anywhere within a 3x3 chunk space centered on the original sensor (use F3+g for chunk borders), and away from the original sensor (to avoid any confusions).  Place the copied sensor down.
4. Create vibrations near the copied sensor and observe that it does not respond.  Go to the original sensor, create vibrations, and note that the copied sensor still does not respond to any vibrations (for comparison in step 6).  Step directly on the copied sensor to observe that it does activate, and additionally sends a signal out to the location of the original sensor with two consecutive 'vibration.png' particle effects.
5. Unload+reload the chunks by any means, such as logging out and back in, or teleporting far away and back.
6. Repeat step 4, but note differences.  Vibrations near the copied sensor still make no difference, however vibrations near the original sensor will activate both the original and the copied sensor simultaneously.
7. Remove the original sensor, and repeat step 4 again.  Notice that vibrations around the location of the now-gone original sensor will still cause the copied sensor to activate.

See the attached video for a visual walkthrough of these steps.

Additional Notes:

• This bug very likely relates to MC-249450, which also first affected version 22w12a.
• May also relate to MC-207251, which also deals with sensor position NBT data

2023-03-26-01-01-08.mp4