The error occurs when no target is found, make sure you have a zombie in those coordinates (that is x=0,y=64,z=0, in range of 20 blocks, your clock is running and the system is in loaded chunks (as well as position where zombie should be).
To testfor an entity with specific name use name=
There are three possible outputs for it.
The UUID is not in a correct format. (My problem)
Makes no output text. (What you're saying)
Object is successfully summoned or target is found.
And I'll try the name= thing later once I get back to it. I can work around the problem but holy crap it's time consuming.
class="quote-body">I'm having a couple of problems trying to use this command.
Testing for more than one entity in the same block.
Testing for an entity in cords, tried [x,y,z,type=entity] and [x,y,z,r,type=entity] (like the wiki said) and tried [type=entity] x,y,z
Testing for an entity with a name. I have no clue where to begin the search for "{CustomName:"Whatever"}" I tried before, in, and after the @e.
I really need help with this because it's really bugging me.
(The picture is how the wiki says it needs to be.)
1. Not sure, but the c identifier might help?
2.Try putting the label of [x=0,y=64,z=0]
3.I think it is [name="Name"]
Other troubleshooting:
Make sure there is a zombie there.
Make sure the chunk is loaded
Rollback Post to RevisionRollBack
Also take a look at this guide if you are requesting builders for a server/project.
Please note, if I deny a suggestion because it is already possible, then I mean it is already possible withing 10 command blocks (That do not spawn other command blocks) or up to 5 creations (Command blocks that spawn other command blocks) to make your suggestion.
If I critique your suggestion I am not hating on you. Learn the difference.
Okay. I made a scoreboard objective for it and it goes... /scoreboard objectives add Boss1 dummy. But I don't know how to add Dr. Ned to it. I tried this...
The format is actually invalid. The x/y/z/r parameters must have labels if they are not placed at the very beginning of the list of parameters (there are no other requirements for order). The reason it's working now is because it's no longer looking for a specific location, thus the entire world is searched for any zombies. This leads me to believe that your coordinates themselves are incorrect, and the command he provided is no different than:
/testfor @e[type=Zombie]
However, looking at your /summon command leads me to ask: how many zombies have you summoned at the same time with that command? If you have more than one entity with the same UUIDLeast/UUIDMost pair, you will run into conflicts and commands will no longer be able to target those entities. UUIDs are meant to be unique, and no entity should have the same UUID as another (hence "Universally Unique"). You'll likely need to use a third-party editor in order to remove all of the conflicting targets.
As more general information: you cannot have quotation marks (nor spaces) in player selectors. Having only x/y/z parameters with no limiter (radius) will only change the origin of the start of the search, and will not help at all when looking for entities within a specific location. Your original command was perfectly correct, meaning the error does indicate that no zombie could be found within 20 blocks of (0,64,0). If you're positive that the coordinates and radius are correct, and that the area is loaded, then it's likely you've got a UUID conflict by summoning multiple of those zombies. But the error of "UUID format is invalid" does also mean that no target was found, which is your problem since the command is structured correctly.
I'm having a couple of problems trying to use this command.
Testing for more than one entity in the same block.
Testing for an entity in cords, tried [x,y,z,type=entity] and [x,y,z,r,type=entity] (like the wiki said) and tried [type=entity] x,y,z
Testing for an entity with a name. I have no clue where to begin the search for "{CustomName:"Whatever"}" I tried before, in, and after the @e.
I really need help with this because it's really bugging me.
(The picture is how the wiki says it needs to be.)
Ok let's see, For #1 you mean testing for more than 1 of the same entity within the coordinates?
/testfor @e[0,64,0,20]
Ths will try to find all the entities within 20 blocks of the block at 0,64,0. If you wish to count how many, you can only count up to 15 using a comparator. To testfor an entity with a name, you have to make sure the name does NOT have any spaces in it. Do not use quotations either I'm afraid.
The format is actually invalid. The x/y/z/r parameters must have labels if they are not placed at the very beginning of the list of parameters (there are no other requirements for order). The reason it's working now is because it's no longer looking for a specific location, thus the entire world is searched for any zombies. This leads me to believe that your coordinates themselves are incorrect, and the command he provided is no different than:
/testfor @e[type=Zombie]
However, looking at your /summon command leads me to ask: how many zombies have you summoned at the same time with that command? If you have more than one entity with the same UUIDLeast/UUIDMost pair, you will run into conflicts and commands will no longer be able to target those entities. UUIDs are meant to be unique, and no entity should have the same UUID as another (hence "Universally Unique"). You'll likely need to use a third-party editor in order to remove all of the conflicting targets.
As more general information: you cannot have quotation marks (nor spaces) in player selectors. Having only x/y/z parameters with no limiter (radius) will only change the origin of the start of the search, and will not help at all when looking for entities within a specific location. Your original command was perfectly correct, meaning the error does indicate that no zombie could be found within 20 blocks of (0,64,0). If you're positive that the coordinates and radius are correct, and that the area is loaded, then it's likely you've got a UUID conflict by summoning multiple of those zombies. But the error of "UUID format is invalid" does also mean that no target was found, which is your problem since the command is structured correctly.
I'm using http://mcstacker.bimbimma.com/ for my /summon commands. So in order for me to look for all (or at least 15) I need to tell it a radius? And is there a way to solve the max of searches (15?) I was also using the cords from the Wiki, it's not where I'm at exactly but the x,y,z of my wanted search is 10000,~1, 10000 with a radius of 130. Are ~ allowed in the testfor?
Ok let's see, For #1 you mean testing for more than 1 of the same entity within the coordinates?
/testfor @e[0,64,0,20]
Ths will try to find all the entities within 20 blocks of the block at 0,64,0. If you wish to count how many, you can only count up to 15 using a comparator. To testfor an entity with a name, you have to make sure the name does NOT have any spaces in it. Do not use quotations either I'm afraid.
Those I'm afraid did not work. Testfor @e[x,y,z,type=Zombie] also didn't. However, it did work when I switched the cords with the type=Zombie.
Also, on a side note. Is there a way to kill entities without killing more than 1? Say, I don't want to die and I don't want my Villager to die, is there a string I can use to achieve this?
I'm using http://mcstacker.bimbimma.com/ for my /summon commands. So in order for me to look for all (or at least 15) I need to tell it a radius? And is there a way to solve the max of searches (15?) I was also using the cords from the Wiki, it's not where I'm at exactly but the x,y,z of my wanted search is 10000,~1, 10000 with a radius of 130. Are ~ allowed in the testfor?
Those I'm afraid did not work. Testfor @e[x,y,z,type=Zombie] also didn't. However, it did work when I switched the cords with the type=Zombie.
Also, on a side note. Is there a way to kill entities without killing more than 1? Say, I don't want to die and I don't want my Villager to die, is there a string I can use to achieve this?
Oh OH!! Wait, you can't do [x,y,z,name=Hello] It has to be [x,y,x,1,name=Hello] It is the same except it needs you to clarify the r value. But turning it around works just as well.
Well you will have to specify the entity type.
/kill @e[type=Zombie]
Because you can do
/kill @e[name=!Player]
which will kill everything but you. But you can't put more than 1 type= value in the specifiers. You will have to go through the list of entities to kill everything but you and the villagers.
But if it is in your interest you can do
/gamerule doMobSpawning false
this will prevent all hostile mobs from spawning naturally in your world.
Testfor cannot use ~ ~ ~ unfortunately. So 10000,~1,10000,130 shouldn't work. If you meant -1 then that is literally in the void so it wouldn't work at all, or does it..? I personally tried to mess with the comparators and I don't have a way to bypass the 15 mob limit but Skyliner might have a way
This is what your command should look like. But make sure you put the right y coordinate in and btw you can also do: [x,y,z,dx,dy,dz,type=Zombie] :the d's are how far away in that direction from the coordinates. Just make sure you put dx= and etc.
Oh OH!! Wait, you can't do [x,y,z,name=Hello] It has to be [x,y,x,1,name=Hello] It is the same except it needs you to clarify the r value. But turning it around works just as well.
Well you will have to specify the entity type.
/kill @e[type=Zombie]
Because you can do
/kill @e[name=!Player]
which will kill everything but you. But you can't put more than 1 type= value in the specifiers. You will have to go through the list of entities to kill everything but you and the villagers.
But if it is in your interest you can do
/gamerule doMobSpawning false
this will prevent all hostile mobs from spawning naturally in your world.
Testfor cannot use ~ ~ ~ unfortunately. So 10000,~1,10000,130 shouldn't work. If you meant -1 then that is literally in the void so it wouldn't work at all, or does it..? I personally tried to mess with the comparators and I don't have a way to bypass the 15 mob limit but Skyliner might have a way
Turning the r to 130 worked with "Zed". Now to change the name of things. If I have 2 Command Blocks setup with different "!" then it won't work either, both will die. So there's only one option? That sucks.
This is what your command should look like. But make sure you put the right y coordinate in and btw you can also do: [x,y,z,dx,dy,dz,type=Zombie] :the d's are how far away in that direction from the coordinates. Just make sure you put dx= and etc. If you still wanted the spaces in the names you can try this:
Oh OH!! Wait, you can't do [x,y,z,name=Hello] It has to be [x,y,x,1,name=Hello] It is the same except it needs you to clarify the r value. But turning it around works just as well.
Well you will have to specify the entity type.
/kill @e[type=Zombie]
Because you can do
/kill @e[name=!Player]
which will kill everything but you. But you can't put more than 1 type= value in the specifiers. You will have to go through the list of entities to kill everything but you and the villagers.
But if it is in your interest you can do
/gamerule doMobSpawning false
this will prevent all hostile mobs from spawning naturally in your world.
Testfor cannot use ~ ~ ~ unfortunately. So 10000,~1,10000,130 shouldn't work. If you meant -1 then that is literally in the void so it wouldn't work at all, or does it..? I personally tried to mess with the comparators and I don't have a way to bypass the 15 mob limit but Skyliner might have a way
Turning it around does not work if there are no labels. The "name" parameter will not work in this case, since the player's name will be their actual name ("Skylinerw"), not "Player".
EDIT: Unless you mean to replace "Player" with the player name, of course.
Your coordinates were incorrect then, hence why the original command isn't working. You're trying to search where there are no mobs; logically it won't find any. You have to enter the coordinates that you are expecting the mob to be at. You can't just copy/paste any command and not change it to fit your system or world.
Again, putting the x/y/z/r parameters (without labels) at a point besides the beginning of the list will not work as you want it to. Insert the correct coordinates.
Turning it around does not work if there are no labels. The "name" parameter will not work in this case, since the player's name will be their actual name ("Skylinerw"), not "Player".
EDIT: Unless you mean to replace "Player" with the player name, of course.
Your coordinates were incorrect then, hence why the original command isn't working. You're trying to search where there are no mobs; logically it won't find any. You have to enter the coordinates that you are expecting the mob to be at. You can't just copy/paste any command and not change it to fit your system or world.
Again, putting the x/y/z/r parameters (without labels) at a point besides the beginning of the list will not work as you want it to. Insert the correct coordinates.
Both yours and his worked.Unless I did it wrong again, I don't really know. I didn't test named Zombies though. And I'll have to check that link. Nor radius, just the x,y,z exact.
I'll explain why the following commands don't actually work:
/testfor @e[type=Zombie,1001,5,9983]
/testfor @e[type=Zombie,x=1001,y=5,z=9983]
The first command does not have labels for the x/y/z parameters. The parameters are then invalidated, meaning they're thrown out and completely ignored. In order to use the x/y/z/r parameters without labels, you must place them at the beginning of the list of parameters, as I have shown in my commands.
Because the parameters are essentially thrown out, you are now only looking for "type=Zombie". If there are zombies anywhere in your world, it will find them. Since you want to find zombies in a specific location, this is not going to work for you.
The second command has the same problem. You are only changing the origin; the starting location of where to find closest matches. You are not limiting how far out to look for targets. That means the entire world is searched, same as the first command, and you are not actually finding targets in the area you intended to only find them. You must include some sort of limiter, such as a radius, in order to reduce the selection area.
The same is true for your other images using my commands. You've neglected to include the selection limiter, which I had originally provided in my commands.
The first command is fixed by moving the parameters in the correct slot, while also including a radius:
/testfor @e[1001,5,9983,130,type=Zombie]
The second command is fixed by adding a radius:
/testfor @e[type=Zombie,x=1001,y=5,z=9983,r=130]
And you'll see that the fixed commands are essentially identical to the ones I provided. A radius of 130 from X of 1001, Y of 5, and Z of 9983.
I'll explain why the following commands don't actually work:
/testfor @e[type=Zombie,1001,5,9983]
/testfor @e[type=Zombie,x=1001,y=5,z=9983]
The first command does not have labels for the x/y/z parameters. The parameters are then invalidated, meaning they're thrown out and completely ignored. In order to use the x/y/z/r parameters without labels, you must place them at the beginning of the list of parameters, as I have shown in my commands.
Because the parameters are essentially thrown out, you are now only looking for "type=Zombie". If there are zombies anywhere in your world, it will find them. Since you want to find zombies in a specific location, this is not going to work for you.
The second command has the same problem. You are only changing the origin; the starting location of where to find closest matches. You are not limiting how far out to look for targets. That means the entire world is searched, same as the first command, and you are not actually finding targets in the area you intended to only find them. You must include some sort of limiter, such as a radius, in order to reduce the selection area.
The same is true for your other images using my commands. You've neglected to include the selection limiter, which I had originally provided in my commands.
The first command is fixed by moving the parameters in the correct slot, while also including a radius:
/testfor @e[1001,5,9983,130,type=Zombie]
The second command is fixed by adding a radius:
/testfor @e[type=Zombie,x=1001,y=5,z=9983,r=130]
And you'll see that the fixed commands are essentially identical to the ones I provided.
When r is provided is it a sphere, cube, or just flat with the y?
(The picture is how the wiki says it needs to be.)
Embed Removed
There are three possible outputs for it.
Embed Removed
1. Not sure, but the c identifier might help?
2.Try putting the label of [x=0,y=64,z=0]
3.I think it is [name="Name"]
Other troubleshooting:
Make sure there is a zombie there.
Make sure the chunk is loaded
Also take a look at this guide if you are requesting builders for a server/project.
Please note, if I deny a suggestion because it is already possible, then I mean it is already possible withing 10 command blocks (That do not spawn other command blocks) or up to 5 creations (Command blocks that spawn other command blocks) to make your suggestion.
If I critique your suggestion I am not hating on you. Learn the difference.
Embed Removed
/summon Zombie 10000 7 10000 {CustomName:"Dr. Ned",CustomNameVisible:1,UUIDLeast:1L,UUIDMost:1L,Equipment:[{id:shears,Count:1,tag:{Unbreakable:1,ench:[{id:16,lvl:3},{id:19,lvl:6}]}},{id:leather_boots,Count:1,tag:{Unbreakable:1,ench:[{id:0,lvl:2}],display:{color:7359769}}},{id:leather_leggings,Count:1,tag:{Unbreakable:1,ench:[{id:0,lvl:2}],display:{color:16765900}}},{id:leather_chestplate,Count:1,tag:{Unbreakable:1,ench:[{id:0,lvl:2}],display:{color:16765900}}},{id:leather_helmet,Count:1,tag:{Unbreakable:1,ench:[{id:0,lvl:2}],display:{color:3877138}}}],DropChances:[0.0F,0.0F,0.0F,0.0F,0.0F],Attributes:[{Name:generic.maxHealth,Base:236},{Name:generic.movementSpeed,Base:.3},{Name:zombie.spawnReinforcements,Base:1.0F},{Name:generic.attackDamage,Base:8},{Name:generic.followRange,Base:130},{Name:generic.knockbackResistance,Base:1}],HealF:236,Leashed:1,Leash:{UUIDLeast:1L,UUIDMost:1L}}
and
/summon Zombie 10000 7 10000 {CustomName:"Dr. Ned",CustomNameVisible:1,UUIDLeast:1L,UUIDMost:1L,Equipment:[{id:shears,Count:1,tag:{Unbreakable:1,ench:[{id:16,lvl:3},{id:19,lvl:6}]}},{id:leather_boots,Count:1,tag:{Unbreakable:1,ench:[{id:0,lvl:2}],display:{color:7359769}}},{id:leather_leggings,Count:1,tag:{Unbreakable:1,ench:[{id:0,lvl:2}],display:{color:16765900}}},{id:leather_chestplate,Count:1,tag:{Unbreakable:1,ench:[{id:0,lvl:2}],display:{color:16765900}}},{id:leather_helmet,Count:1,tag:{Unbreakable:1,ench:[{id:0,lvl:2}],display:{color:3877138}}}],DropChances:[0.0F,0.0F,0.0F,0.0F,0.0F],Attributes:[{Name:generic.maxHealth,Base:236},{Name:generic.movementSpeed,Base:.3},{Name:zombie.spawnReinforcements,Base:1.0F},{Name:generic.attackDamage,Base:8},{Name:generic.followRange,Base:130},{Name:generic.knockbackResistance,Base:1}],HealF:236}
Embed Removed
/testfor @e[type=Zombie,0,64,0,20]
That solves one problem, thank you.
Embed Removed
The format is actually invalid. The x/y/z/r parameters must have labels if they are not placed at the very beginning of the list of parameters (there are no other requirements for order). The reason it's working now is because it's no longer looking for a specific location, thus the entire world is searched for any zombies. This leads me to believe that your coordinates themselves are incorrect, and the command he provided is no different than:
However, looking at your /summon command leads me to ask: how many zombies have you summoned at the same time with that command? If you have more than one entity with the same UUIDLeast/UUIDMost pair, you will run into conflicts and commands will no longer be able to target those entities. UUIDs are meant to be unique, and no entity should have the same UUID as another (hence "Universally Unique"). You'll likely need to use a third-party editor in order to remove all of the conflicting targets.
As more general information: you cannot have quotation marks (nor spaces) in player selectors. Having only x/y/z parameters with no limiter (radius) will only change the origin of the start of the search, and will not help at all when looking for entities within a specific location. Your original command was perfectly correct, meaning the error does indicate that no zombie could be found within 20 blocks of (0,64,0). If you're positive that the coordinates and radius are correct, and that the area is loaded, then it's likely you've got a UUID conflict by summoning multiple of those zombies. But the error of "UUID format is invalid" does also mean that no target was found, which is your problem since the command is structured correctly.
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/
Ok let's see, For #1 you mean testing for more than 1 of the same entity within the coordinates? Ths will try to find all the entities within 20 blocks of the block at 0,64,0. If you wish to count how many, you can only count up to 15 using a comparator. To testfor an entity with a name, you have to make sure the name does NOT have any spaces in it. Do not use quotations either I'm afraid. However I believe you can try this: Hope this helps!
I like to help and howl and laugh all day XD
What do NOT say to get in trouble HERE!!!
My Blog
I'm using http://mcstacker.bimbimma.com/ for my /summon commands. So in order for me to look for all (or at least 15) I need to tell it a radius? And is there a way to solve the max of searches (15?) I was also using the cords from the Wiki, it's not where I'm at exactly but the x,y,z of my wanted search is 10000,~1, 10000 with a radius of 130. Are ~ allowed in the testfor?
Those I'm afraid did not work. Testfor @e[x,y,z,type=Zombie] also didn't. However, it did work when I switched the cords with the type=Zombie.
Also, on a side note. Is there a way to kill entities without killing more than 1? Say, I don't want to die and I don't want my Villager to die, is there a string I can use to achieve this?
Embed Removed
Oh OH!! Wait, you can't do [x,y,z,name=Hello] It has to be [x,y,x,1,name=Hello] It is the same except it needs you to clarify the r value. But turning it around works just as well.
Well you will have to specify the entity type.
Because you can do
which will kill everything but you. But you can't put more than 1 type= value in the specifiers. You will have to go through the list of entities to kill everything but you and the villagers.
But if it is in your interest you can do
this will prevent all hostile mobs from spawning naturally in your world.
Testfor cannot use ~ ~ ~ unfortunately. So 10000,~1,10000,130 shouldn't work. If you meant -1 then that is literally in the void so it wouldn't work at all, or does it..? I personally tried to mess with the comparators and I don't have a way to bypass the 15 mob limit but Skyliner might have a way
This is what your command should look like. But make sure you put the right y coordinate in and btw you can also do: [x,y,z,dx,dy,dz,type=Zombie] :the d's are how far away in that direction from the coordinates. Just make sure you put dx= and etc.
I like to help and howl and laugh all day XD
What do NOT say to get in trouble HERE!!!
My Blog
Turning the r to 130 worked with "Zed". Now to change the name of things. If I have 2 Command Blocks setup with different "!" then it won't work either, both will die. So there's only one option? That sucks.
Embed Removed
I like to help and howl and laugh all day XD
What do NOT say to get in trouble HERE!!!
My Blog
Turning it around does not work if there are no labels. The "name" parameter will not work in this case, since the player's name will be their actual name ("Skylinerw"), not "Player".
EDIT: Unless you mean to replace "Player" with the player name, of course.
Your coordinates were incorrect then, hence why the original command isn't working. You're trying to search where there are no mobs; logically it won't find any. You have to enter the coordinates that you are expecting the mob to be at. You can't just copy/paste any command and not change it to fit your system or world.
Again, putting the x/y/z/r parameters (without labels) at a point besides the beginning of the list will not work as you want it to. Insert the correct coordinates.
With labels:
EDIT: I have a post here detailing how to circumvent the 15-signal-strength limit of comparators: http://www.minecraftforum.net/forums/minecraft-discussion/redstone-discussion-and/2338514-help-with-multiple-questions?comment=10
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/
Both yours and his worked.Unless I did it wrong again, I don't really know. I didn't test named Zombies though. And I'll have to check that link. Nor radius, just the x,y,z exact.
Embed Removed
The first command does not have labels for the x/y/z parameters. The parameters are then invalidated, meaning they're thrown out and completely ignored. In order to use the x/y/z/r parameters without labels, you must place them at the beginning of the list of parameters, as I have shown in my commands.
Because the parameters are essentially thrown out, you are now only looking for "type=Zombie". If there are zombies anywhere in your world, it will find them. Since you want to find zombies in a specific location, this is not going to work for you.
The second command has the same problem. You are only changing the origin; the starting location of where to find closest matches. You are not limiting how far out to look for targets. That means the entire world is searched, same as the first command, and you are not actually finding targets in the area you intended to only find them. You must include some sort of limiter, such as a radius, in order to reduce the selection area.
The same is true for your other images using my commands. You've neglected to include the selection limiter, which I had originally provided in my commands.
The first command is fixed by moving the parameters in the correct slot, while also including a radius:
The second command is fixed by adding a radius:
And you'll see that the fixed commands are essentially identical to the ones I provided. A radius of 130 from X of 1001, Y of 5, and Z of 9983.
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/
All four with radius.
Embed Removed
When r is provided is it a sphere, cube, or just flat with the y?
Embed Removed
It's sphere. If you need a square, you use the delta selection parameters instead of radius. List of valid parameters on the wiki: http://minecraft.gamepedia.com/Commands#Target_selector_arguments
You can set the radius to 0 to select the exact coordinate.
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/