Block Update Detectors are complicated and now most don't even work. However, the only reason Mojang removes BUD behavior is because all are bugs. But, now that Jeb has created a way to output a signal when a certain block is placed in a certain spot. But, a simple new command I suggest can make it so it works when ANY block is placed in that location or near the location.
If the adjacent in [adjacent|notadjacent] means that if a block is placed above, below, or to any side of the specific coordinate then it will also trigger the redstone signal. If notadjacent is chosen then it will only work if a block is placed in that specific location.
Note: Remember that destroying a block is still technically placing block 0 so this /testforblockupdate command works for breaking blocks, too.
Note: Activating a redstone signal going into this block (lever, button, tripwire, etc.) will not activate the redstone output from the command block UNLESS it changes the block such as activating/deactivating a redstone lamp or torch.
Thanks for reading my suggestion!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Setup:
/testforblockupdate <x> <y> <z> [adjacent|notadjacent]
If the adjacent in [adjacent|notadjacent] means that if a block is placed above, below, or to any side of the specific coordinate then it will also trigger the redstone signal. If notadjacent is chosen then it will only work if a block is placed in that specific location.
Note: Remember that destroying a block is still technically placing block 0 so this /testforblockupdate command works for breaking blocks, too.
Note: Activating a redstone signal going into this block (lever, button, tripwire, etc.) will not activate the redstone output from the command block UNLESS it changes the block such as activating/deactivating a redstone lamp or torch.
Thanks for reading my suggestion!