cmdblock 1 can not be read by c1 therefore 2&3&4 can not operate
5 is part of the clock
i guess the comparator cant read the cmdblock fast enough or cant output fast enough as this works with a slower clock than a fill/setblock clock i used in the pic
i need to use the fast clock to achieve what i want to, as the thing i want to detect happens really fast and the game i intend to build may be cheated on or broken if this does not happen fast enough
Attachments
Comments 9
1: /clear @a minecraft:diamond 0 1
2: /give @a minecraft:stone
3: /setblock ~1 ~-1 ~ minecraft:unpowered_comparator 3
4: /setblock ~2 ~1 ~ minecraft:command_block 0 0 {Command:/clear @a minecraft:diamond 0 1}
on the pic im facing south
if i put a stack of diamonds in my inventory, i get about 21 stone back, i should get a stack though.
if you dont use 3 and 4 youll only get one stone for any amount od diamonds, as the comparator gets stuck on the on state as long as i have diamonds to be cleared of.
i first discovered this with a bunch of parameters on each item and doing other things behind c1, but this gives the same result.
(btw 64/21 is about as long as a redstone tick, so i guess the comparator only works every redstopne tick, whereas the clock on every gametick i might be wrong on this though)
"4: /setblock ~2 ~-1 ~ minecraft:command_block 0 0 "
should it not be 4: /setblock ~2 ~1 ~ minecraft:command_block 0 0
however further I don't see the problem, I do know the comparator has a delay of 1, that could be your problem, it could be the clock going to fast for the comerator
yeah i derpd on 4 yours is the right one, i copied from another one of my tests.
and as it seems i get 21 items every time i have 64 diamonds in my inventory
I really think it's just the delay on the comperator that bothers your device, the clock goes faster then the comperator because of the delay
also the corect command should be /setblock ~2 ~1 ~ minecraft:command_block 0 {Command:/clear @a minecraft:diamond 0 1}
you added an extra 0: command_block 0 0
well then, i guess i call that delay a 'bug'. ive seen it beeing called intended behaviour, but in this case it is not... i guess one can say if you have commandblocks you are creative and are cheating one in survival would not. so thereby the delay after a commandblock is unnessessary as it wont lag servers or worlds of one player in survival. and commandblocks can do way worse than a comparator with a 0 tick delay anyways, so why not add it to check if it reads a commandblock and then give it a 0 tick delay? that would not change its way of operating in other redstone mechanics, only screw with timings of other commandblock builds built before.
it isn't a bug previously in 1.5 snapshots it got 0.5 delay, what got higher to 1 intentionaly, just don't make the device run on a setblock clock, and that is axactly why they don't set it to 0 delay, it WILL cause lag and everything else
paste the exact command of the effected command block