Place your other commands along this line. The length is determined by the second set of coordinates. This creates a 1 block wide, 5 block long line of redstone blocks along the z-axis. Instead of the commands above, use (again, command blocks along the X-axis) /fill ~1 ~ ~ ~1 ~ ~4 stone Fill clockĪ fill clock uses the same basic principles as the setblock clock, but allows for more commands to be run by creating a line of redstone blocks rather than a single block. If more than two of your commands require to be run in a specific order, I suggest using a fill clock instead. The execution order can be more difficult when working on different axes at the same time though. Command blocks on the same axis activate from lower to higher coordinate. You can now place up to 4 other command blocks next to the redstone block. If everything is done correctly, this block is immediately recreated when you break it. Place a redstone block in the center to jump-start the clock. I used smoothstone as my alternate block, but you can use any other solid, non-transparent block (transparent blocks, including air blocks, would cause lighting updates!). This example is for the X-axis, for another axis, move the ~1 and ~-1 to the corresponding position in the setblock command, e.g. In the other one, put /setblock ~-1 ~ ~ redstone_block No matter how you oriented your command blocks, locate the one at the lower coordinate and set it to /setblock ~1 ~ ~ stone Red points towards positive X, Green towards positive Y and Blue towards positive Z, that is RGB corresponds to XYZ. This tells you the direction of the three major coordinate axes. If you are playing on 1.8+ and the gamerule reducedDebugInfo is false (the default), your cursor turns into a red green and blue thingy. Remember what I said about the well-ordered execution earlier? This is based on the (relative) coordinates the command blocks are placed in, so let's find out! Place two command blocks in a line, with a single free space in between. It creates and destroys a single redstone block between the two command blocks. Setblock clockĪ setblock clock is slightly simpler than it's larger cousin. One to set the redstone blocks, the other to set the regular block. By a similar logic, you should limit your use of comparators and repeaters, even though they're not quite as bad as redstone dust.īoth clocks require two command blocks as a base. A setblock/fill clock has no lighting updates, and few block updates. Virtually lag-free: Redstone dust is laggy, mostly due to block updates and lighting updates around it.This allows you to, for example, set a scoreboard objective to 0 for everyone, and to 1 for certain players directly afterwards, without their score "flickering". Well-defined execution order: This may seem odd, but while every command is executed at the same time, the placement of the command blocks still determines the order this happens in.They are extremely useful for making command block contraptions for multiple reasons: They are therefore also referred to as "20Hz" clocks. What are those?Ī setblock or fill clock is a command block contraption based on using the /setblock or /fill commands to alternately set redstone blocks and regular blocks in the same spot, therefore activating adjacent command blocks 20 times a second. Repeating and chain command blocks have the same functionality (see below) and more, and are much easier to use. First off, if you are playing in Minecraft 1.9 or later, you don't need to use these clocks.
0 Comments
Leave a Reply. |