mojira.dev
MCPE-72407

Hopper not emptying loot chests

Maybe I'm doing this wrong, but I've tried this on chests in a bastion and also tested it on a buried treasure chest in the overworld

A chest will not empty into a hopper unless you open the chest first.  This defeats the purpose of using the hopper to empty the chest - the point of using the hopper is to not aggravate the piglins by opening the chest.  Maybe this isn't a bug, but based on the excerpt below from https://minecraft.gamepedia.com/Piglin, it seems that the emphasis on opening hoppers around piglins implies that it's a bug: 

"Piglins are provoked when players attack them, break or open a chesttrapped chestender chestbarrel, or a shulker box near them. They are also provoked by a player breaking blocks of goldgold oregilded blackstone and nether gold ore. However, they will not get provoked if a player near them opened other containers such as hoppersfurnacesbrewing stands, etc."

I'm assuming the issue is that the loot table isn't generating items unless the chest is opened or broken (breaking a loot chest before opening releases contents) - both of which agro the piglins (unless you use something like TNT, which I haven't tried yet)

Steps to Reproduce:

  1. Find a naturally generated chest

  2. Place a hopper underneath the chest

  3. Open the hopper

  4. Notice the hopper is not emptying the chest

Attachments

Comments 5

I also wanted to report this just. The bug is that when a hopper interacts with a loot chest where the loot hasn’t been generated yet the loot doesn’t generate. On java it does. If this doesn’t get fixed many players on bedrock will try to loot chests with a hopper an wonder why it doesn’t work while java players can do this without any issue.

Can confirm. What's even wierder is that you can place items in the chest with a hopper and fill it, preventing the loot from being generated. I actually came across this in the end.

That's what I showed in the video I attached.

Seems to be fixed in 1.16.0.63 beta

Yeah can confirm, it is fixed. I could not reproduce this in 1.16.1.

Dave Fritz

(Unassigned)

344278

Confirmed

Windows

Windows

1.16.0.61 Beta, 1.16.0.60 Beta, 1.16.0.58 Beta

1.16.1

Retrieved