Steven E
- steve104
- steve104
- Europe/Stockholm
- Yes
- No
I found this when testing snapshot 13w05a in my redstone world.
I had built a few devices using a dropper/hopper based randomizer in the 13w04a snapshot, and they all worked as expected. After installing 15w05a I found none of them worked.When an item is placed into a hopper by a dropper, the hopper does not change the state of any comparator attached to it.
Process:
1. Place a dropper anywhere.
2. Place a hopper facing the output side of the dropper.
3. Place a comparator for redstone output of the hopper.
4. Put any item of any amount in the dropper.
5. Power the dropper. A button works well for this example.Expected result:
The dropper puts one item in the hopper.
The comparator would activate and stay on for as long as the item remains in the hopper.
The hopper puts the item back in the dropper.Observed result:
The comparator did not activate.
The comparator becomes a BUD, activating by any block update around it, provided the hopper still holds items.I found this when testing snapshot 13w05a in my redstone world.
I had built a few devices using a dropper/hopper based randomizer in the 13w04a snapshot, and they all worked as expected. After installing 13w05a I found none of them worked.When an item is placed into a hopper by a dropper, the hopper does not change the state of any comparator attached to it.
Process:
1. Place a dropper anywhere.
2. Place a hopper facing the output side of the dropper.
3. Place a comparator for redstone output of the hopper.
4. Put any item of any amount in the dropper.
5. Power the dropper. A button works well for this example.Expected result:
The dropper puts one item in the hopper.
The comparator would activate and stay on for as long as the item remains in the hopper.
The hopper puts the item back in the dropper.Observed result:
The comparator did not activate.
The comparator becomes a BUD, activating by any block update around it, provided the hopper still holds items.
Thanks for the quick confirmation. I was really disappointed by this one. Looking forward to a fix soon.
I can confirm this.
In my case, it used "@p" as a player name, which was added to the team. So the team list was
"Steve104, Player, @p".
Not a duplicate. Tested in 13w06a, and it still exists as reported, even though MC 8776 and duplicates have been fixed.