Timeline for How to test if 2 items are near each other in Minecraft 1.10.2?
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 14, 2019 at 13:42 | comment | added | I Like Fish | @Quijibo oh i've checked everything again and i found a mistake that i don't choose the correct command block for your command. Thanks for helping me :)) | |
| Jun 14, 2019 at 11:55 | comment | added | Quijibo | @ILikeFish I think the problem is that you are using two command blocks that lead to an AND gate, when you don't actually need them. You can have just the command that I showed, because you don't need to test if there are these two items somewhere in the world if you are also testing if the items are right next to each other. So, you can remove the two command blocks that are just testing if the dropper and crafting table are thrown on the ground. | |
| Jun 14, 2019 at 11:18 | comment | added | I Like Fish | @Quijibo but there're a few problem:I have a system testing if dropper and crafting table are throwed on the ground. Then 2 comparators and an AND gate get the redstone to the command you have gave me then a comparator will move the signal to some command block to summon the custom crafting table.When i throw dropper and craftng table near each other, it works but the redstones still got signal from the command block have your command to some summon command blocks and it only works once. I tried to put /scoreboards players reset <player> <objective> after all but it didn't work. What wrong? | |
| Jun 13, 2019 at 19:22 | history | edited | Quijibo | CC BY-SA 4.0 |
fixed grammar
|
| Jun 13, 2019 at 19:20 | comment | added | Quijibo | @ILikeFish Glad I could help :) Also, I should start putting lamps behind comparators. I like having my cookies not eaten. | |
| Jun 13, 2019 at 19:02 | comment | added | Fabian Röling |
Oh, right. But the concept is the same (and I forgot the distance before): /execute @e[type,bla] ~ ~ ~ execute @e[type,r,bla] ~ ~ ~ say hi
|
|
| Jun 13, 2019 at 14:54 | comment | added | I Like Fish | @FabianRöling /execute at @e[type=item,bla=bla] at @e[type=item,limit=1,bla=bla] only works in 1.13+ | |
| Jun 13, 2019 at 10:28 | comment | added | Fabian Röling | If you ever put a comparator on a command block with something other than a lamp behind it, I will haunt your house and eat all your cookies. ;) | |
| Jun 13, 2019 at 10:27 | comment | added | Fabian Röling |
/execute at @e[type=item,bla=bla] at @e[type=item,limit=1,bla=bla] run say hi
|
|
| Jun 13, 2019 at 9:03 | comment | added | I Like Fish | @Quijibo it's work thanks you so much | |
| Jun 13, 2019 at 9:02 | vote | accept | I Like Fish | ||
| Jun 13, 2019 at 8:45 | comment | added | Quijibo | @FabianRöling How would that work? | |
| Jun 13, 2019 at 8:26 | comment | added | Fabian Röling |
I suggest not using testfor at all, you don't ever need it. Just use execute.
|
|
| Jun 13, 2019 at 8:26 | comment | added | I Like Fish | thanks you very much for fixing my bad english and helping my problem | |
| Jun 13, 2019 at 5:01 | history | answered | Quijibo | CC BY-SA 4.0 |