I was having this same error problem, but with a different command
/tp @p[x=163.5,y=56,z=465.4,dx=-161.4,dy=57,dz=467.4] ~ ~3 ~ it always says the same thing "the entity UUID provided is in an invalid format." anybody know a fix to this? plz help been trying to do this forever
There's a bug where you can't use negative value for dx, dy, dz.
I've submitted a bug report but it's concluded as working as intended
I was having this same error problem, but with a different command
/tp @p[x=163.5,y=56,z=465.4,dx=-161.4,dy=57,dz=467.4] ~ ~3 ~ it always says the same thing "the entity UUID provided is in an invalid format." anybody know a fix to this? plz help been trying to do this forever
EDIT: Nevermind. Forgot to provide search coordinates. However, now I'm having another problem, irrelevent to this thread, so I'm gonna go create a new one.
I also got an invalid uuid with this command:
Testfor @p[x=50,y=70,z=-400,r=3,name=falconflurry]
It worked on 1.7.4. Didn't work on 14w03b
This works perfectly fine for me. Invalid UUID will appear when it fails to check for an entity. That means, even if the command is correct, if there isn't any entity that matches, it will show invalid UUID. In your case, try and capitalize your IGN. As it's case sensitive.
I'm also getting this error a lot. I think it's a bug because sometimes the command works when I don't even change one single thing in the command.
I hope it's a bug and that it'll be fixed on the release of 1.8.2.
I'm also having trouble as well. I'm using what seems to be what all the youtubers had used in 1.6-1.7 : /testfor @p[x=50,y=64,z=46,r=1] and it's telling me the same thing.
I seem to have a problem as well. I want to test for a zombie in a specific location. I put:
/testfor @e[type=Zombie][x=689, y=6, z=1282]
but all I got was:
[15:05:11] The entity UUID provided is in an invalid format
But when I put:
/testfor @e[type=Zombie]
It somehow works.
Is this mine or Minecraft's fault?
I seem to have a problem as well. I want to test for a zombie in a specific location. I put:
/testfor @e[type=Zombie][x=689, y=6, z=1282]
but all I got was:
[15:05:11] The entity UUID provided is in an invalid format
But when I put:
/testfor @e[type=Zombie]
It somehow works.
Is this mine or Minecraft's fault?
The coordinate needs to be placed on the player selector, combined with the type of the entity
And you also want to specify the radius. If you want to check for only a single block, use 0
I am also getting the response for an error and do not know why.
I named a Cow Edgar then tried this command /kill @e[name=Edgar] what is the problem here?
Note: I did use the /summon command for this cow and did name him Edgar in the same command.
Never mind I found the issue the name was wrong lol i feel stupid
The /tp command does not support dataTags; you're currently putting the dataTags in the 'target' teleport location. Entity selectors also don't support dataTags as of 14w02c, and to be honest I doubt they ever will due to the additional "dataTags" option on the /testfor command.
What you would have to do instead is use the /testfor command, which does support dataTags. Another thing to note is a large number of NBT tags require you to label the tag-type. In this case, the tag-type is "byte", so you label the value with a 'b':
<3 Thank you.
EDIT: Ok how can i make the {inGround:1} work with the arrow thing?
tp @p @e[type=Arrow] {inGround=1} Doesn't seem to work :L
guys, inGround?1b CAN be a @?[UUID format] AND a {DataTag} you replace ? With = for UUID and : for DataTag.
Now can anyone please tell me how to correctly UUID format @a[slot0=(item)] (for non-testing command purposes excluding /testfor and the like)
guys, inGround?1b CAN be a @?[UUID format] AND a {DataTag} you replace ? With = for UUID and : for DataTag.
Now can anyone please tell me how to correctly UUID format @a[slot0=(item)] (for non-testing command purposes excluding /testfor and the like)
guys, inGround?1b CAN be a @?[UUID format] AND a {DataTag} you replace ? With = for UUID and : for DataTag.
Now can anyone please tell me how to correctly UUID format @a[slot0=(item)] (for non-testing command purposes excluding /testfor and the like)
NOT using {DataTags}
No, it cannot. "inGround" is NBT data, as well as "Slot". NBT data must be placed within 'dataTags' unless there is a parameter that creates a bridge, such as the 'name' parameter for the 'CustomName' tag. There is no 'slot0' or 'inGround' parameter. You have to use commands that support dataTags, which includes /testfor and /scoreboard.
If you want to target entities using commands that don't support NBT data, you will have to assign the entity a score using the /scoreboard command, which didn't support NBT data back in January. It was specifically updated for the purpose of allowing other commands access to NBT data selection through the /scoreboard command. For example:
No, it cannot. "inGround" is NBT data, as well as "Slot". NBT data must be placed within 'dataTags' unless there is a parameter that creates a bridge, such as the 'name' parameter for the 'CustomName' tag. There is no 'slot0' or 'inGround' parameter. You have to use commands that support dataTags, which includes /testfor and /scoreboard.List of valid parameters: http://minecraft.gam...mands#ArgumentsList of valid NBT data for entities: http://minecraft.gam...t#Entity_FormatList of valid NBT data for items: http://minecraft.gam...#Item_structureIf you want to target entities using commands that don't support NBT data, you will have to assign the entity a score using the /scoreboard command, which didn't support NBT data back in January. It was specifically updated for the purpose of allowing other commands access to NBT data selection through the /scoreboard command. For example:
/scoreboard objectives add NAME dummy
/scoreboard players {dataTags}
/scoreboard players set @a NAME 1 {Inventory:[{id:minecraft:stone,Slot:0b}]}
The above will set players 'NAME' objective to 1 that have stone in their first inventory slot. You can then target those players based on the score:
/say @a[score_NAME_min=1]
first of all "slot0" was a placeholder second good idea third apparently you aren't using 14w11b in which case of course inGround=1/inGround=1b (not sure which) for arrows only which is implemented THEN is not a [UUID]. If you are using 14w11b I HAVE used it to tp myself to an arrow in the ground with this command /tp @p @e[type=Arrow,inGround=1,c=1]. IT WORKS. If it doesn't try adding b to one or both of the "1"s.
first of all "slot0" was a placeholder second good idea third apparently you aren't using 14w11b in which case of course inGround=1/inGround=1b (not sure which) for arrows only which is implemented THEN is not a [UUID]. If you are using 14w11b I HAVE used it to tp myself to an arrow in the ground with this command /tp @p @e[type=Arrow,inGround=1,c=1]. IT WORKS. If it doesn't try adding b to one or both of the "1"s.
You had used it when there were no other arrows in flight closest to you. The invalid parameter (inGround) is ignored and you will be teleported to the single, nearest arrow entity, whether or not it's in the ground. Please test it by shooting an arrow straight up into the air and immediately using your /tp command while there are no other arrows in existence (/kill @e[type=Arrow]).
You had used it when there were no other arrows in flight closest to you. The invalid parameter (inGround) is ignored and you will be teleported to the single, nearest arrow entity, whether or not it's in the ground. Please test it by shooting an arrow straight up into the air and immediately using your /tp command while there are no other arrows in existence (/kill @e[type=Arrow]).
oops, I was wrong sorry, but still "slot0" was a placeholderit was a good idea you gave me ,thanks, the MAIN reason why i thought it was a UUID was because i made a tp arrow concept that relied on it being in the ground but then i forgot that i used a testfor block as well.
There's a bug where you can't use negative value for dx, dy, dz.
I've submitted a bug report but it's concluded as working as intended
Here's the link to the report
https://mojang.atlassian.net/browse/MC-45134
-
View User Profile
-
View Posts
-
Send Message
Retired StaffYou also cannot use decimals in your coordinates at all.
returns
EDIT: Nevermind. Forgot to provide search coordinates. However, now I'm having another problem, irrelevent to this thread, so I'm gonna go create a new one.
Killed by a pack of wolves.
Testfor @p[x=50,y=70,z=-400,r=3,name=falconflurry]
It worked on 1.7.4. Didn't work on 14w03b
This works perfectly fine for me. Invalid UUID will appear when it fails to check for an entity. That means, even if the command is correct, if there isn't any entity that matches, it will show invalid UUID. In your case, try and capitalize your IGN. As it's case sensitive.
I hope it's a bug and that it'll be fixed on the release of 1.8.2.
/testfor @p[x=50,y=64,z=46,r=1]
and it's telling me the same thing.
/testfor @e[type=Zombie][x=689, y=6, z=1282]
but all I got was:
[15:05:11] The entity UUID provided is in an invalid format
But when I put:
/testfor @e[type=Zombie]
It somehow works.
Is this mine or Minecraft's fault?
The coordinate needs to be placed on the player selector, combined with the type of the entity
And you also want to specify the radius. If you want to check for only a single block, use 0
So I have rapidly spawning creepers somehwere in the world:
/summon Creeper * * * {Fuse:5,ExplosionRadius:3,ignited:1}
I use this + /gamerule mobGriefing false so I can have non-block damage explosions.
I attempt to make grenades with Sethbling's Explosive Projectiles trick:
/testfor @e[type=XPOrb]
Now it is suppoed to then teleport a creeper to an XPOrb like this
/tp @e[type=Creeper] @e[type=XPOrb]
and then kill the XPOrb. BUT ^that command didn't work!
I solved the problem by adding "c=-1"
/tp @e[type=Creeper,c=-1] @e[type=XPOrb,c=-1]
this teleports the youngest existing creeper to the youngest existing XPOrb. This works now!
Hope this is helpful
I named a Cow Edgar then tried this command /kill @e[name=Edgar] what is the problem here?
Note: I did use the /summon command for this cow and did name him Edgar in the same command.
Never mind I found the issue the name was wrong lol i feel stupid
guys, inGround?1b CAN be a @?[UUID format] AND a {DataTag} you replace ? With = for UUID and : for DataTag.
Now can anyone please tell me how to correctly UUID format @a[slot0=(item)] (for non-testing command purposes excluding /testfor and the like)
NOT using {DataTags}
-
View User Profile
-
View Posts
-
Send Message
Retired StaffNo, it cannot. "inGround" is NBT data, as well as "Slot". NBT data must be placed within 'dataTags' unless there is a parameter that creates a bridge, such as the 'name' parameter for the 'CustomName' tag. There is no 'slot0' or 'inGround' parameter. You have to use commands that support dataTags, which includes /testfor and /scoreboard.
List of valid parameters: http://minecraft.gamepedia.com/Commands#Arguments
List of valid NBT data for entities: http://minecraft.gamepedia.com/Chunk_format#Entity_Format
List of valid NBT data for items: http://minecraft.gamepedia.com/Player.dat_format#Item_structure
If you want to target entities using commands that don't support NBT data, you will have to assign the entity a score using the /scoreboard command, which didn't support NBT data back in January. It was specifically updated for the purpose of allowing other commands access to NBT data selection through the /scoreboard command. For example:
/scoreboard players <set|add|remove> <objective> <value> {dataTags}/scoreboard players set @a NAME 1 {Inventory:[{id:minecraft:stone,Slot:0b}]}The above will set players 'NAME' objective to 1 that have stone in their first inventory slot. You can then target those players based on the score:
-
View User Profile
-
View Posts
-
Send Message
Retired StaffYou had used it when there were no other arrows in flight closest to you. The invalid parameter (inGround) is ignored and you will be teleported to the single, nearest arrow entity, whether or not it's in the ground. Please test it by shooting an arrow straight up into the air and immediately using your /tp command while there are no other arrows in existence (/kill @e[type=Arrow]).
oops, I was wrong sorry, but still "slot0" was a placeholderit was a good idea you gave me ,thanks, the MAIN reason why i thought it was a UUID was because i made a tp arrow concept that relied on it being in the ground but then i forgot that i used a testfor block as well.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium/testfor @p[x=-195, y=71, z=-50, r=1]Bit late to the party here but this command doesn't work!
/testfor @p[x=-195, y=71, z=-50, r=1]