How to reproduce this bug:
1. place a dispenser with about 64 items in it
2. power it; shoots out one.
3. Place redstone (not connected to the input that is powering the dispenser) or any other block near the diespenser (radius of 2 or 3 blocks)
4. It shoots out another item.
ATTENTION!
screenshot-1.jpg is the bug I'm talking about, not others! Comparators are intended to make constant updates, and dispenser BUD.jpg is acutally not BUD, because the redstone dust is powering the block and that powers the dispenser. I would like to remove the picture but I don't know how and I don't even know if I can.
Related issues
is duplicated by
relates to
Attachments
Comments


Can confirm. Redstone dust placed in positions 1 or 2 will trigger the dispenser, but not on dust removal.
Placing dust in positions 3, 4 or 5 however won't trigger dispenser, but will trigger on removal.
Position 6 has no effect

WARNING : this is a well known and useful bug. A lot of people use it to make the dispensers shoot faster. You should check with the community before fixing it.
Google "rapid fire dispenser"
https://www.google.ch/search?q=rapid+fire+dispenser

A good fix would be to simply make the dispenser fire as fast as whatever clock you're using can go. It would not only resolve the update bug but also remove the need to use a silly workaround to make the dispenser fire quickly.

@Kumasasa : Why did you update fix version to "Minecraft 1.4.5" ? Has this been fixed ?

I believe it's a request to fix version 1.4.5, not a version in which it is fixed. English is a silly language.

Corrected

Thanks for fixing the fix, I intended to set the affected version to 1.4.5, not the fixed version.

An added complication is that, if a comparator is attached to a dispenser filled with non-stacking items (e.g. potions) the comparator output changes each time an item is dispensed, causing a redstone update that triggers the dispenser again. See screen-shot for example set-up.

This even works when a redstone line two blocks below the dispenser is updated.

Same for the Dropper.

If a comparator is placed facing into a dispenser or dropper and a switch is placed on the side then flipping the switch will make the dispenser/dropper fire continuously. Even though the comparator is un-powered, it seems to cause redstone updates every tick.

This is an intended feature of dispensers and droppers.
When they receive a redstone update, as comparators do constantly, the dispenser or dropper will fire repeatedly.

This is a well known bug, but definitely not intended.

If it were intended, it would have been marked as "Works as intended" as soon as it was confirmed. But no, this report is marked as Confirmed and Unresolved.

Hey, the Bug I reported isn't the same like that one. You've to wtach the video COMPLETE not the first 10 seconds. The real Bug is that the Dispenser/Dropper is ticking despite the Dispenser/Dropper isn't connected with redstone.

This is the same bug.

screenshot-1.jpg is the bug I'm talking about, not others! Comparators are intended to make constant updates, and dispenser BUD.jpg is acutally not BUD, because the redstone dust is powering the block and that powers the dispenser. I would like to remove the picture but I don't know how and I don't even know if I can.

This bug is OLD and useful, is it really a bug, or just complicated redstone?

The rules of redstone are very simple when you know them. No other device takes a block update as an input, except piston bud switches, which is also confirmed to be a bug. It also causes more problems than it solves, as redstone that isn't pointing at the dispenser, and in some cases not even next to the dispenser, will set it off.

Have added a photo. If I power the signal, all three droppers fire one item. When I unpower the signal, a dropper will fire again if the delay between any two droppers is greater than two ticks. (so if the repeater is set to the second slot or more, it will fire an item when the signal is turned off).

Do remove the picture if you can, or tell me how to (since I started the issue). That is not a bug, or at least not what I'm trying to say anyways. If you consider this as a bug, there won't be a compact piston elevator. What I'm trying to say in this issue was screenshot-1.jpg, not other pictures from people who doesn't understand redstone.

It is actually the same problem, but we don't need tons of screenshots. Deleted.

Comparator was suppose to update blocks that are in contact with it (If my English makes sense); But this has been changed in 13w05a. But anyways thanks and hopefully people won't get confused when they see this (When the hell is Mojang going to see this?)

This bug is widely used by the community, however I believe it should be fixed. As with the 'constantly updating comparator' issue it causes far more issues than it solves. One of the stated goals of 1.5 is to make redstone logic 'more predictable and consistent', and fixing this issue is a perfect way to do that.

I couldn't have said it better myself.

um...Comparator are already fixed so that it won't constantly update blocks 😛 Which made the redstone more consistent.

Allow me to clarify: I think that the dispenser update bug should be fixed for the same reasons that the comparator bug was fixed.

I was making a contraption with a dropper and a Comparator. The redstone dust from the comparator(changing the redstone strength) was causing a update, which messed up the timing/item count. Hopefully his bug gets fixed soon. Vote for it.

The powered dispenser dispense the lava cause of an update in front of it and don't stop until we remove the bucket from the dispenser. The dispenser act like a BUD but not only with redstone

http://youtu.be/qyzFkmp3G3c that's what it does on the latest snapshot

There is a way to rewire everything so that it works with the new behavior. It is always better to have something be larger than founded on bugs. And if you don't like the behavior, you can always run 13w10a.

@William Pearson: One of the goals of the Redstone Update was to make Redstone more reliable and self-consistent. No other block activates on redstone updates, and the behavior didn't even make sense. Yes, it IS all bug.