I'm not sure if it's a bug yet, but I swear it wasn't like that before. Basically, shouldn't the comparator just deactivate once the impulse command block is finished with it's work.
If it's because there is data on the command block, why not repeat command blocks. Repeat command blocks will only activate comparators once it's find the particular thing.
I'm not sure if it's a bug yet, but I swear it wasn't like that before. Basically, shouldn't the comparator just deactivate once the impulse command block is finished with it's work.
If it's because there is data on the command block, why not repeat command blocks. Repeat command blocks will only activate comparators once it's find the particular thing.
If it's always been like this...then I'm dumb.
It's always been like that.
yeah
You should put a chain command block set to always active and coditional on top of your impulse block
In the chain command block have a /setblock ~~~ that activates your repeating command block