MC-10112/clear with command blocks not working with armor that has been worn with custom damage values.
I have a command block that gives me an iron chestplate with damage -32000. I also have another command block saying /clear @p. Without equipping the chestplate /clear works ok. But when I wear the armor and take it off again /clear doesn't work. Also tested with chain helmet and leather pants.
Environment
Java 7 update 10
Windows 7 Home Premium
Normal Minecraft Launcher
Created Issue:
/clear with command blocks not working with armor that has been worn with custom damage values.
I have a command block that gives me an iron chestplate with damage -32000. I also have another command block saying /clear @p. Without equipping the chestplate /clear works ok. But when I wear the armor and take it off again /clear doesn't work. Also tested with chain helmet and leather pants.
Environment
Java 7 update 10
Windows 7 Home Premium
Normal Minecraft Launcher
is duplicated by
![[Mojang] Jeb (Jens Bergensten)](../../../data/assets/gravatar/jeb.jpeg){kind=small}
[Mojang] Jeb (Jens Bergensten)relates to
relates to
relates to
MC-9066
Duplicate of MC-10112, please use the search function to see if your bug has already been submitted. Currently over 52% of tickets are being closed as duplicate.
Confirmed
Also, you can not interact with the armor. It becomes a ghost item, You can't drop it in any way.
If you try to move it around in your inventory in survival it will disappear.
Oh I forgot to say that, thanks.
Uhm... Fixed this, but probably not the way you hoped for =) I've made it impossible to create items with negative damage values, because the behavior is undefined. Will compensate by adding some kind of "indestructible" enchantment for this purpose in the future.
Will you do it for 1.5? If no, mapmakers gonna have a bad time :/
First of all, Jeb actually saw this! That was awesome. But the damage value fix sucks really bad, just because a gold helmet and a chain helmet are the only two armor with the exact same protection values, but gold has way less durability. This is a bit of a problem. But the fact that Jeb, someone from mojang actually saw this almost makes up for it. (I say almost because I hope they will fully support custom data values)
I'm making an adventure map and I'm not too happy with this "fix." I'd rather not have an enchantment, because you get the glowing effect. Also, I have to change the whole entire map. Please, find another way to fix the problem!
I agree with David on this one, this little change just broke all vanilla pvp and some pve maps (TF2 with SethBling and Herobrine's Mansion for example). If an enchant is added, every armors will be glowing or wouldn't be giveable via command blocks =(
Please, I started a PVP vanilla map and this little "fix" is just totally breaking my map, i spent a lot of time into it. Please, make so we can set the durability to negative values...
No offence, jeb, but I am kinda regretting reporting this now, as I seem to have completely screwed up some of my favourite maps. TF2 in Minecraft (dustbowl) map is frickin' awesome by the way, Hypixel.
I think if we are not going to be able to have custom data values, at least have it so that they can give us items with extra data, for example, a BLUE leather chestplate enchanted with PROTECTION I. I for one would put up with this as a replacement for the negative datavalues "fix". However I guess that is a feature request as well because it would make things a heck of a lot easier for PvWhatever mapmakers. I think if that were to happen then the command doing the /give with custom data would have to be MCEdited in to prevent abuse.
I've already commented on this. Negative damage values are undefined, but we haven't bothered to change it because nobody's complained about them. Now there is a bug, and the proper fix is to remove the undefined values (otherwise we'll just keep on hunting bugs like these in the future). I've already said that this can be compensated with an enchantment, but it can also be compensated with some kind of tag data (such as a boolean tag stating "indestructible"), but our focus now is to fix bugs and not add new features.
But then we need to wait some months, just to work on our maps properly! And that would be bad
I have to say, that is really bad even if that fix stays for one week, that's making so much awesome maps useless and breakin my pvp map project...
Yeah I see, but it is just a suggestion for the future. It seems the mapmakers will have to wait a bit longer...
Also, how hard would it be to support negative values? Most vanilla PvP maps depend on command blocks giving items that are "indestructible" anyway. I think most of the framework for negative values is there anyway, so it would be good for negative damage, rather than dispensers which don't work forever but give the item with a tag for example doItemdamage or something similar.
Yes add the boolean indestructible tag!
I would support the boolean tag along with the enchantment, also rarely found in dungeon chests, but more rare than others. I keep losing armor not dedicated to mobs, so those pieces being indestructible would be marvelous. However, maybe as a downside so this isn't abusable in vanilla survival, is probably make it so that armor with it doesn't count to your protection? Such as if I had an indestructible Respiration and Aqua Affinity along with an indestructible Feather Falling, they would give me my water and falling buffs, but not take effect in combat. Perhaps only additives with enchantments, and only the enchantments of those affect damage and not their default armor value? Just a thought.
I in all honesty would support all three actually, but the negative damage values need to be implemented. This is breaking a lot of maps, and the truth is command blocks (theoretically) work forever, but dispensers (which would have to be used if the extra data idea was put as a REPLACEMENT to negative damage) don't.
Without the custom durabilities, it's breaking tons of maps. So please either get it back, or add a indestructible enchantment or tag ASAP. I really need this and tons of maps are unplayable now.
And actually, enchantments give it the glowing effect and you can't give it with Command Blocks. This fix is the exact opposite of a fix. Please find a solution to this!
I think items with damage ID -1 should be indestructible, every other negative ID would be blocked, like this we can give them with commandblocks and it wouldn't bee too complicated to use them!
Nope, Ali. All negative damage values won't work.
No, that was no hint, it was more something like a suggestion!
Ali, that is actually a nice idea! But what if we just want it to last a few more uses than normal?
I think just also have a command like this
/uses <player> <How many uses you want left/max/min>
Then that outputs something like
Setting <itemid> <resultingDamageValue> Succeeded!
Then the two fields can be easily copied into a command block.
Example:
/uses iPwnTNT 500 (assume I am holding a new iron sword)
Custom setting of 267 -249 succeeded!
Why -249 damage? (Or something similar)
Because an iron sword usually lasts 251 uses and 251 - 500 = -249
Please discuss feature requests at the MineCraft Forums: Suggestions.
but the suggestions at the forum get ignored most of the time and these custom damages are pretty important for us
I totally agree with the suggestions. The custom damages are VERY important to us.
...I just want unbreakable swords.
This problem needs to be solved soon. It's breaking a ton of maps. We NEED (I repeat: NEED) the custom damage values. It was permissible before, its just that the behaviour is a bit weird. I think the undefined behaviour needs to be fixed rather than the custom damages completely removed.
I agree with the people saying that we need negative damage values. I use them. And so do a lot of people. An "indestructible" boolean cannot be given by command blocks without the inclusion of the givechest (http://www.minecraftforum.net/topic/1561812-now-that-we-have-the-command-block/) Just undo this fix and re-fix it by editing the clear command.
Closed. This is no discussion forum here.