Observer 0 ticks non-operational or resulting in locational behavior when not directly updated
When using an observer to generate a 0 tick pulse, by indirectly powering the intended receiver of the signal via a block or redstone line, the behavior is locational with dust and does not work at all unless the transmitter or receiver receives a direct block update from the observer.
Edit: The locational issue is not relevant as this has always been present, the more concerning is that it no longer works powering via blocks or qc.
2025-01-09, 08:07 PM
2025-01-09, 08:15 PM
2025-01-09, 08:15 PM
0
0
-