This is to remove a diamond block placed a fraction of a second earlier, in front of a redstone repeater powered at the same time. This command block resets the mechanism. I get "The block couldn't be placed", but when the diamond block is not powered (by disconnecting the repeater next to it), the command works perfectly. I am using snapshot 14w28b. Is this a bug? Am I using setblock incorrectly?
EDIT: I've noticed this does not occur with /fill under the same conditions. Only with /setblock. I think it's probably a bug but still need to make sure.
I found a workaround, so my structure isn't there anymore. But I still would like to figure out what's going on here. What particular information do you need clarified?
I tested it out myself, exactly the same (except for cords ofc) command, tried powering the block just just before replacing, in the same tick and just after it, tried to do it using relative coordinates and exact - I still can't get the bug to happen. Maybe the command block was already powered, maybe you had another command block powering that put the diamond block back? Both of these seem equally unlikely though, especially that the /fill one worked... It would seem that you had a typo in the command, or something else in the world that would somehow make the /setblock command not work properly - I don't think we will be able to figure it out without world save/screenshot
It couldn't have been a typo; the command worked perfectly as long as the block was unpowered. I think what may have happened is that it might have been on a chunk boundary (can't tell for sure now that I tore it down). The block was being powered by a repeater if that helps, sort of as a redstone equivalent of a transistor. In the original device the block was powered for a split second, during which the block would be powered, the command block would be executed, and the block would stop being powered (F3 confirms this). When I was testing, the block was powered continually. In both cases the command failed, until I made sure the block was unpowered continually.
This is to remove a diamond block placed a fraction of a second earlier, in front of a redstone repeater powered at the same time. This command block resets the mechanism. I get "The block couldn't be placed", but when the diamond block is not powered (by disconnecting the repeater next to it), the command works perfectly. I am using snapshot 14w28b. Is this a bug? Am I using setblock incorrectly?
EDIT: I've noticed this does not occur with /fill under the same conditions. Only with /setblock. I think it's probably a bug but still need to make sure.
It couldn't have been a typo; the command worked perfectly as long as the block was unpowered. I think what may have happened is that it might have been on a chunk boundary (can't tell for sure now that I tore it down). The block was being powered by a repeater if that helps, sort of as a redstone equivalent of a transistor. In the original device the block was powered for a split second, during which the block would be powered, the command block would be executed, and the block would stop being powered (F3 confirms this). When I was testing, the block was powered continually. In both cases the command failed, until I made sure the block was unpowered continually.