MC-45409Command block texts not being read correctly
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.
Update: (In response to Anon Ymus)
I was using the /summon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}
NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~ {CustomName:"George",CustomNameVisible:1,Equipment:[{id:minecraft:iron_sword},{id:minecraft:iron_boots}]}
command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}
. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:minecraft:iron_sword}]}
to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
Environment
OSX 10.9.1
Java 7 update 45
Created Issue:
Equipment NBT tag does not work for /testfor on mobs
Put the summary of the bug you're having here
What I expected to happen was...:
Describe what you thought should happen hereWhat actually happened was...:
Describe what happened hereSteps to Reproduce:
1. Put a step by step guide on how to trigger the bug here
2. ...
3. ...Environment
OSX 10.9.1
Put the summary of the bug you're having here
What I expected to happen was...:
Describe what you thought should happen hereWhat actually happened was...:
Describe what happened hereSteps to Reproduce:
1. Put a step by step guide on how to trigger the bug here
2. ...
3. ...UNFINISHED
accidentally hit return too early, currently finishing through editing...
This ticket is incomplete. Please review the guidelines before reporting issues.
For technical support please use the Mojang Support Center.
UNFINISHED
accidentally hit return too early, currently finishing through editing...I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'. The errors always seemed to have something to do with the characters on the ends of the strings not being loaded.
OSX 10.9.1
OSX 10.9.1
Java 7 update 45
Equipment NBT tag does not work for /testfor on mobsCommand block texts not being read correctly
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'. The errors always seemed to have something to do with the characters on the ends of the strings not being loaded.
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the {Equipment:[
{id:<Item>}]} NBT Tag on Zombies. I managed to get the /summon Zombie ~2 ~ ~{CustomName:"George",CustomNameVisible:1,Equipment:[
{id:Iron_sword},
{Iron_boots}]} command to work as well as /testfor @e[type=Zombie]
{CustomName:"George"}. However, later in my testing when I was working on trying to get /testfor @e[type=Zombie] {Equipment:[
{id:Iron_sword}]} to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{id:<Item>}{Equipment:[{id:Iron_sword}
]}NBT Tag on Zombies. I managed to get the/summon Zombie ~2 ~ ~{CustomName:"George",CustomNameVisible:1,Equipment:[,
{Iron_boots}]} command to work as well as /testfor @e[type=Zombie]
{CustomName:"George"}. However, later in my testing when I was working on trying to get /testfor @e[type=Zombie] {Equipment:[
{id:Iron_sword}
]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~{CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:Iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~{CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:Iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~{CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[
{id:Iron_sword}]}
to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~{CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[
{id:Iron_sword}]}
to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~{CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"} {code}. However, later in my testing when I was working on trying to get {code} /testfor @e[type=Zombie] {Equipment:[{id:Iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~{CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"} {code}. However, later in my testing when I was working on trying to get {code} /testfor @e[type=Zombie] {Equipment:[{id:Iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~{CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:Iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~~{CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:Iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ {CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:Iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the
s/ummon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ {CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:Iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the /summon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ {CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:Iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the /summon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ {CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{Iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:Iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the /summon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~ {CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the /summon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~ {CustomName:"George",CustomNameVisible:1,Equipment:[{id:Iron_sword},{iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the /summon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~ {CustomName:"George",CustomNameVisible:1,Equipment:[{id:minecraft:iron_sword},{id:id:minecraft:iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the /summon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~ {CustomName:"George",CustomNameVisible:1,Equipment:[{id:minecraft:iron_sword},{id:id:minecraft:iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:minecraft:iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
I expected the command blocks to follow their commands, however, after quitting and saving and then replaying a certain command block world I had, I realized that the command blocks were not following what they said was written in them. Originally I thought it was a certain NBT tag that wasn't compatible with /testfor, but then other things that were working stopped working, and then once I rewrote them again, they worked again.
In some cases I got 'this command does not exist' or 'missing bracket'.
The errors always seemed to have something to do with the characters on the ends of the strings not being loaded. <-INCORRECT: I just got an error in which an NBT tag in the middle of other brackets that are working is not working.Update: (In response to Anon Ymus)
I was using the /summon and /testfor commands. I was in the process of trying to figure out how to test for an object being in someone's inventory, starting out by listing the
{Equipment:[{id:<Item>}]}NBT Tag on Zombies. I managed to get the
/summon Zombie ~2 ~ ~ {CustomName:"George",CustomNameVisible:1,Equipment:[{id:minecraft:iron_sword},{id:id:minecraft:iron_boots}]}command to work as well as
/testfor @e[type=Zombie] {CustomName:"George"}. However, later in my testing when I was working on trying to get
/testfor @e[type=Zombie] {Equipment:[{id:minecraft:iron_sword}]}to work, Suddenly my Summon command block was not spawning the zombie. This was the first time I had pressed the button to activate the command block since I had reloaded the game, which I had already done several times, and now it wasn't working. All the text looked fine. I remember it first complaining about brackets on the NBT tags, so I retyped the }]} at the end and than that worked for the equipment, but then the name wasn't working (it said Zombie above it's head, not George), so I retyped the name just as it was already, and then that worked.
Now I'm not sure if Equipment tag works the way I wanted it to or if it's just this same bug that must have loaded the command for the block from the text incorrectly or what. I've been unloading and reloading the world for a little bit and haven't been able to replicate it yet, so it might just be a one time thing.
I will try to see if I can provide any steps to replication or screenshots of the issue, I don't have any evidence yet because so far it seems random. All I know is that I can fix text that would normally work by rewriting the whole string of text again.
Please list what command was causing this.
How in the world am I supposed to fix that formatting up there? Whenever I edit those new line/returns are gone, just spaces like before.
If you click the help icon below where you type in your comments...
https://bugs.mojang.com/secure/WikiRendererHelpAction.jspa?section=advanced
See the code tags at the bottom.
ah, thank you.
I fixed your summon command. The ~ and { need a space between them. Also I changed the id's to be the proper format
I can reopen this ticket if it still doesn't work with Ezekiel's edits.