Comparator pulse extenders that use command blocks in the circuitry do not extend a redstone signal. As soon as the power souce is turned off, so does the circuit. If the exact same circuit is built, and the command block is repaced with a different solid block, the pulse extender works as intended. Since command blocks are also solid blocks, it makes no sense as to why they're an exception. If this is working as intended, please change this.
Attachments
Comments 11
migrated
I could not reproduce this problem in Windows 10 release 1.2.13.60. For me, the circuit remained active for 2 ticks after I stepped off the pressure plate.
I can think of two possible explanations:
The circuit is working properly, but the delay isn't as long as you expected. In this case, you would need to add additional pairs of comparators.
The circuit is working properly but the command block isn't behaving as you expected. In this case, we would need to know more about what you expect the circuit to do and what command you're using.
I could not reproduce this problem in Windows 10 release 1.2.13.60. For me, the circuit remained active for 2 ticks after I stepped off the pressure plate.
I can think of two possible explanations:
The circuit is working properly, but the delay isn't as long as you expected. In this case, you would need to add additional pairs of comparators.
The circuit is working properly but the command block isn't behaving as you expected. In this case, we would need to know more about what you expect the circuit to do and what command you're using.
If it only stayed active for only two ticks for you, then you pretty much did replicate it. And it didn't matter what command I was using. Rebuild the circuit and replace the command block with a different solid block. You should see what the comparators are supposed to do. Also, it doesn't have to be a pressure plate. Any redstone power source will work.
You're right of course. I was thinking you meant that the command block was acting like a transparent block, so I stopped as soon as I saw that it wasn't.
Confirmed in Windows 10 release 1.2.13.60. Note that the powered command block powers the redstone dust beside it, but the dust does not appear to power the comparator whose input it's attached to (it doesn't light up).
You're right of course. I was thinking you meant that the command block was acting like a transparent block, so I stopped as soon as I saw that it wasn't.
Confirmed in Windows 10 release 1.2.13.60. Note that the powered command block powers the redstone dust beside it, but the dust does not appear to power the comparator whose input it's attached to (it doesn't light up).
It looks as though this affects other blocks/ block entities also, including Note Block, Dropper, Dispenser, Redstone Lamp and Command Block :