[MCPE-12856] Comparators don't reliably detect items in dispenser Created: 30/Jan/16  Updated: 28/Apr/16  Resolved: 28/Apr/16

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.14.0 Beta 2, 0.14.0 Beta 3
Fix Version/s: None

Type: Bug
Reporter: skribe
Resolution: Duplicate Votes: 0
Labels: None

Attachments: PNG File 2016-01-30 05.04.48.png     PNG File 2016-01-30 05.06.34.png     PNG File 2016-01-30 05.06.53.png     PNG File 2016-01-30 05.07.24.png    
Issue Links:
Duplicate
duplicates MCPE-11353 Redstone dot doesn't power blocks on ... Resolved
Confirmation Status: Unconfirmed
Platform: Tablet - Android - Samsung Galaxy Tab 4 Nook

 Description   

I'm trying to make a chicken farm which involves eggs being fired from a dispenser. I have the eggs fed into the dispenser (via a hopper) and then a comparator detects that it's got content and fires the dispenser. If there is still content in the dispenser then it fires again and again until it is empty.

However, the dispenser only fires the once: when the circuit is first completed. I can break the circuit and rebuild it and it will fire again but only once. The comparator doesn't appear to be detecting the remaining content. After the first shot it remains unlit. I've included screenshots of the problematic circuit design (which works fine in MCPC 1.8.x).

I managed to create a working version using a different circuit but that has problems in that the dispenser stops firing when there are still ten eggs remaining. Additional eggs will fire but it never drops below ten. The dispenser refuses to fire until there are ten eggs inside. Unlike the other circuit the comparator remains lit. I've included a screenshot of the relevant part.



 Comments   
Comment by PHO [ 28/Apr/16 ]

The redstone torch shown in your last screenshot should not be lit in the first place when the dispenser is empty:

So this is a direct consequence of now-fixed MCPE-11353. I cannot reproduce this in 0.14.2 / iOS.

Generated at Sat Jan 11 14:57:37 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.