using /blockdata command to set dispenser to have tnt amount to negative value will fire 1 tnt and set the amount of item to 0
(I'm not sure about other item fire out of dispenser , but this problem isfound when I want to use my trap)
What I expected to happen was...:
using /blockdata command to set dispenser to have tnt amount to negative value will continue to fire tnt and set the amount from item to -2,-3,-4,...
using /blockdata command to set dispenser to have tnt amount to negative value will fire 1 tnt and set the amount of item to 0
how to reproduce it:
step 1: make a new world (cheat is enabled!) or just use your world that have cheat enabled
step 2: set a dispenser
step 3: made a very fast clock and wire it to dispenser (not a command block clock one-that will be too fast so the dispenser can shoot once)
step 4: stop the clock
step 5: set on the dispenser and type following command
/blockdata ~ ~-1 ~ {Items:[0:{slot:0b,id:"minecraft:tnt",Count:-1b}],id:"trap",Lock:""}
or just copy it from cmd.txt file (it's the command to set the tnt in 1st slot to -1 , I'm not sure about other slot)
step 6: start the clock and you will see the problems
test if it occur to all negative value :
in step 5 change command from
/blockdata ~ ~-1 ~ {Items:[0:{slot:0b,id:"minecraft:tnt",Count:-1b}],id:"trap",Lock:""}
to
/blockdata ~ ~-1 ~ {Items:[0:{slot:0b,id:"minecraft:tnt",Count:<other negative integer>b}],id:"trap",Lock:""}
(be sure to change the <other negative integer> to negative integer!)
or you can copy 2nd command from cmd2.txt
(again ,be sure to change the <other negative integer> to negative integer!)
Attachments
Comments 10
Uh, the comment you quoted just stated that this is a bug? "-1 item count is not something we actually support, and is a bug when it works at all"
I rather thought that he meant that anything regarding Count:-1 is a bug. Anyways I changed it now to the comment by jeb
Yes, he did mean that. The fact that -1 count is possible is a bug! Both of your quoted comments have stated this.
I don't think he meant it that way. You can use commands like */blockdata*
or */entitydata*
to give set block Damage values to an incorrect value or item values to an incorrect values as well. I guess what he rather meant was that it was possible to have blocks with items with a negative count which would cause infinite items. Now the game just seems to treat them as 1 and that is fine I guess.
However this report is still invalid
How can you possibly think that negative stack size is an intended feature? From your quote:
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.
How is this unclear?
@unknown can you please stop it. The report was about the fact that dispenser with an item of the Count of 0 or less won't shoot infinite and that is definitely invalid because of the quote. If you think it is a bug that you can create items with Count of 0 or less you can create a new report. However then all other tags need to be fixed as well, as you can use for nearly everthing invalid values (like numbers higher than 32767 for shorts...)
Like I said that is not the bug described in this report. It might be a bug that you can get items with the count of -1.
If you think it is a bug that you can create items with Count of 0 or less you can create a new report.
However this report here is invalid
I am sorry KingSupernova that I was maybe rude. But the problem here is probably also for the developers to implement that. They would need than to add this for all NBT tags because most of them are only made to contain positive numbers, but by default all data types include the negative numbers as well. It is even dubious if MC-67514 is then really invalid because the game defaults the count to 0 (which is invalid) instead of defaulting it to 1. I can only assume that jeb meant rather that they care at first about the bugs caused by negative items and don't support any functionalities of them any longer (but I can only assume that).
Probably invalid because of
https://bugs.mojang.com/browse/MC-10112?focusedCommentId=48798&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-48798
Edit: Changes quote