I'm making a minigame, and I am trying to use the /testforblock command to test if there is a crafting table at a location, and if there is it will output a signal.
The command I am using:
/testforblock ~ ~2 ~ minecraft:crafting_table
However, when I run it with a clock, it doesn't output a signal. Anyone have any suggestions?
I'm making a minigame, and I am trying to use the /testforblock command to test if there is a crafting table at a location, and if there is it will output a signal.
The command I am using:
/testforblock ~ ~2 ~ minecraft:crafting_table
However, when I run it with a clock, it doesn't output a signal. Anyone have any suggestions?
If you're using the speedy comparator clock, you'll need to extend the length of the wire before it reaches the command block. Otherwise you'll have to use a slower clock. If that's not the issue, then I'm unsure. The command itself works, but a comparator clock prevents the command block from firing as intended.
If you're using the speedy comparator clock, you'll need to extend the length of the wire before it reaches the command block. Otherwise you'll have to use a slower clock. If that's not the issue, then I'm unsure. The command itself works, but a comparator clock prevents the command block from firing as intended.
Skylinerw is right; the command works as intended. However, if the clock is not your problem, maybe you could check your coordinates. Currently, you are checking 2 blocks above the location of the command block, rather than any horizontal direction. Also, you are checking with respect to the command block itself, not the player. Finally, make sure that the block you are testing for and the block you place match exactly; if you give yourself a minecraft:crafting_table with data value 1 and test for a minecraft:crafting_table with data value 0, the test for block command would not output a true signal (although it's pretty unlikely that this is the problem ).
Looks like the comparator clock was too fast, thanks for the help guys!
Actually, comparator clocks aren't too fast for the command block- if the command block is too close, the signal strength will switch between strengths of about 12-15 or something like that and somewhere around 1-3 (can't remember the exact numbers), so you just need to extend the wire. Unless this is some new comparator clock I haven't heard about. Which I'm pretty sure it isn't.
Rollback Post to RevisionRollBack
I am so mad at the Sky fanboys who are like "ADD BUUUDDDER TWO MINCRFT CUZ BURDR Z SP ASWUM ND STUFZ BUDDERBUDDERBUDDER :D:D:D:D" that I am dedicating my signature to stopping them. I had gone into more depth, but the stupid signature limit stopped me. Oh well.
I'm making a minigame, and I am trying to use the /testforblock command to test if there is a crafting table at a location, and if there is it will output a signal.
The command I am using:
/testforblock ~ ~2 ~ minecraft:crafting_table
However, when I run it with a clock, it doesn't output a signal. Anyone have any suggestions?
If you're using the speedy comparator clock, you'll need to extend the length of the wire before it reaches the command block. Otherwise you'll have to use a slower clock. If that's not the issue, then I'm unsure. The command itself works, but a comparator clock prevents the command block from firing as intended.
Minecraft-things: http://skylinerw.com
More Minecraft-things: https://sourceblock.net
Guides for command-related features (eventually moving to Source Block): https://github.com/skylinerw/guides
I primarily hang out in the /r/MinecraftCommands discord, where there's a lot of people that help with commands: https://discord.gg/QAFXFtZ
Their corresponding subreddit: https://www.reddit.com/r/MinecraftCommands/
Skylinerw is right; the command works as intended. However, if the clock is not your problem, maybe you could check your coordinates. Currently, you are checking 2 blocks above the location of the command block, rather than any horizontal direction. Also, you are checking with respect to the command block itself, not the player. Finally, make sure that the block you are testing for and the block you place match exactly; if you give yourself a minecraft:crafting_table with data value 1 and test for a minecraft:crafting_table with data value 0, the test for block command would not output a true signal (although it's pretty unlikely that this is the problem ).
Good luck!
Actually, comparator clocks aren't too fast for the command block- if the command block is too close, the signal strength will switch between strengths of about 12-15 or something like that and somewhere around 1-3 (can't remember the exact numbers), so you just need to extend the wire. Unless this is some new comparator clock I haven't heard about. Which I'm pretty sure it isn't.