Open up a command block. Click X. Then Done. Re-Open command block and the previous output is still there and button is O
Also is there a /blockdata command to update the "Previous Output" flag? Save clicking in a few hundred blocks to turn it off.
Tested this with (client) 1.8.3/1.8.7 (server 1.8.7)
Attachments
Comments 10
Cannot really confirm
But you can use /gamerule sendCommandFeedback false and turn it when you finished placing the command blocks back on. This way every command block automatically doesn't track its output
I understand you cannot confirm, it's really rare, like I said, it only happens to a few command block out of the 100s in my server
side note:
this seems to only happen with fill/setblock clocks, or at least ones that get activated repeatedly in small amounts of time
might be the server having preformance issues and failing to save it
Was trying to find a pattern to when the it doesn't work. Command blocks I placed quite some time ago the X/O button functions as expected.
Any new command blocks the X/O button doesn't save when you close the GUI. Thought it might be it does save the X/O when the command block was activated and the GUI was up but that wasn't always the case.
This works though! /blockdata -31 42 -2088 {TrackOutput:0b} That's something I can script to get all the command blocks off.
I'll play around with the /gamerule sendCommandFeedback false too.
"this seems to only happen with fill/setblock clocks, or at least ones that get activated repeatedly in small amounts of time
might be the server having performance issues and failing to save it" - actually for me it's happening for all new command blocks created with 1.8.3+ near the /seblock clock.
I also had some random command blocks that didn't want to save it, near, but not attached to, a fill clock
I got one that doesn't want to turn it on nor off
Does replacing the command block/changing commands fix the issue? Do the same spots in different worlds behave the same?
only disableing the redstone clock behind me makes me able to change it
so it has to do with the preformance
the weirdest thing is that it does save any changes in the command, but not if it should track the output
can confirm, but only with a few command blocks out of the 100s I have
you can use
to be able to turn it off