Looked at the data information in F3 menu and see that the distance attribute does not instantly change to the new value when specifically removing a log, but increases by 1 until it settles at 7. It seems to be looking outward for the existence of a log 1 block at a time, increasing the distance attribute as it is searching and stopping at 7 if it cannot find anything.
My guess would be that only when the distance value is 1 or 2, for the first 2 leaves, the ticking up process is long enough for the observer to observe the first update, reset, and receive a second update from the leaf block.
Tom Groskamp
Looked at the data information in F3 menu and see that the distance attribute does not instantly change to the new value when specifically removing a log, but increases by 1 until it settles at 7. It seems to be looking outward for the existence of a log 1 block at a time, increasing the distance attribute as it is searching and stopping at 7 if it cannot find anything.
My guess would be that only when the distance value is 1 or 2, for the first 2 leaves, the ticking up process is long enough for the observer to observe the first update, reset, and receive a second update from the leaf block.
Edit: 1.17.1