No, I thought about that, but the cooldown is supposed to be per sensor, not global, right? If so, there's way more than 0.5 seconds between the time when an individual skulk sensor activates and the next time I walk past it in that gif, meaning that the sensor should already be cooled down and ready to trigger again. In any case, you can trigger sensors sequentially like this using a different trigger such as pistons firing, so this is proof of inconsistent behavior. Why does one trigger work and not others?
No, I thought about that, but the cooldown is supposed to be per sensor, not global, right? If so, there's way more than 0.5 seconds between the time when an individual skulk sensor activates and the next time I walk past it in that gif, meaning that the sensor should already be cooled down and ready to trigger again. In any case, you can trigger sensors sequentially like this using a different trigger such as pistons firing, so this is proof of inconsistent behavior. Why does one trigger work and not others?
Gif of pistons firing: https://drive.google.com/file/d/1uryiARoPFGK0fi-u9Z024Ej1AEwONdmK/view?usp=sharing
I thought maybe block actions were more reliable than player movement, so I also tried testing this out with rails. A player in a minecart still doesn't reliable trigger every sensor, however: https://drive.google.com/file/d/18eAKZZ2PHsmMFpNtrw68hVIkp1gyDjd_/view?usp=sharing