If a repeating command blocks output connects to a redstone comparator, the command block being "always active", the comparator will light up when the command block has run a command successfully.
Then, if the command block is right clicked and changed to "needs redstone" and "done" is clicked, the comparator will still be lit up.
The expected outcome is that the redstone signal goes low.
If the command block is right clicked yet another time, and only "done" is clicked, the comparator will be unlit.
Technical description: The command block GUI will update the command output when the GUI is updated (as a result of the tile entity update), but not when the button "done" is pressed.
Linked issues
Comments 7
No, this works as intended but I think the duplicates link is wrong.
Repeating command blocks schedule the command they are running for the next tick. Therefor if you set the repeating command block to "Needs Redstone" it sets the success count (= comparator output) to 0, but in the next tick it runs the command the last time and therefor the success count appears to be not reset.
So it is impossible/undesired to deschedule the command for the next tick if the user in fact was setting the command block to "need redstone"?
Yes, found now the correct report: MC-92629
Relates to/duplicate of MC-7681