before i start, i apologise for necroing this thread. i saw it and thought it'd contribute. once i realised i had the same issue (where output=true), i learned that the command block needs to update, which means it either needs to be replaced with a clone of itself or test false. setblock ~ ~ ~ command_block 0 replace (Command:"tp @p ~ ~2 ~") replace the curved brackets with curled brackets: { } the above command will replace itself with a command block that would teleport the nearest player up 2 blocks. the '0' in the command above is for things like wood and wool where there are different versions of it separated by a single value. for example: white wool is version zero. fun fact: the transparent 'air' block can also be used instead of 'command_block'. i quite like creating button-like pulses by making a command block produce a 'redstone_block' and a few ticks later another one that replaces it with air. hope i helped!
Elizabeth Anne Attaway
before i start, i apologise for necroing this thread. i saw it and thought it'd contribute.
once i realised i had the same issue (where output=true), i learned that the command block needs to update, which means it either needs to be replaced with a clone of itself or test false.
setblock ~ ~ ~ command_block 0 replace (Command:"tp @p ~ ~2 ~")
replace the curved brackets with curled brackets:
{ }
the above command will replace itself with a command block that would teleport the nearest player up 2 blocks.
the '0' in the command above is for things like wood and wool where there are different versions of it separated by a single value. for example: white wool is version zero.
fun fact: the transparent 'air' block can also be used instead of 'command_block'. i quite like creating button-like pulses by making a command block produce a 'redstone_block' and a few ticks later another one that replaces it with air.
hope i helped!