2

When I was making a Zombie Horse Trap (Zombie equivalent of Skeleton Trap) using command blocks, one command block was not doing it's job. I tried clicking the "Unconditional" button to make it "conditional", and it had no effect on the system at all.

Does this button even have a point?

If it does, please explain it's purpose.

7

From Gamepedia:

"Conditional": The command block should only execute its command if the command block behind it executed successfully

"Unconditional": The command block should ignore the block behind it

Behind it means the side opposite from the direction the command block is facing.

This differs from chain command blocks because:

"Chain blocks are green. These execute only after the command block pointing to it is processed. This differs from the Conditional option in that it detects what is pointing to it, instead of simply behind it. The command blocks pointing to it also need not be chain blocks themselves to trigger the chain."

-Gamepedia

I hope this helped. Good luck!

| improve this answer | |
  • Also from Gamepedia, "Chain blocks are green. These execute only after the command block pointing to it is processed. This differs from the Conditional option in that it detects what is pointing to it, instead of simply behind it. The command blocks pointing to it also need not be chain blocks themselves to trigger the chain." – Nitrous Oxide Jul 31 '16 at 4:06
  • Yes, but what is the difference between an |impulse|conditional|always active| command block and a |chain|unconditional|always acitve| command block, apart from colour? – Chemical Comrade Aug 7 '16 at 1:54
  • Impluse command blocks are the same as the old ones. Chain will trigger the block it's pointing to. Repeat will execute once per tick (To get rid of clocks). Always active will execute every tick (For making impluse cimmand blocks that are always active). Needs redstone, self explanatory, was the default for the old command blocks. – Nitrous Oxide Aug 7 '16 at 10:44
  • I tried the |impulse|conditional|always active| command block and a chain command block and they had the same effect – Chemical Comrade Aug 9 '16 at 9:08
  • You must be doing something wrong. – Nitrous Oxide Aug 9 '16 at 10:32
-1

Yes, that is correct. The reason for this is so that you can make your redstone/command block builds more compact and it makes it easier to fit the command blocks together.

| improve this answer | |
  • 1
    That's not correct, please delete this answer . – Nitrous Oxide Aug 7 '16 at 10:47
  • His comment makes perfect sense. Making command block arrays more compact is the main idea of chain/conditional impulse command blocks. What has become the discussion here is the difference between |impulse|conditional|always active| and |chain|unconditional|always active| blocks – Chemical Comrade Aug 9 '16 at 9:11
  • 1
    I will admit that it is designed to make builds more compact but the main reason is that they do different things. – Nitrous Oxide Aug 19 '16 at 2:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.