Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Emptying large chests incorrectly on hoppers #319

Open
Mart-y-McFly opened this issue Oct 22, 2024 · 2 comments
Open

[Bug]: Emptying large chests incorrectly on hoppers #319

Mart-y-McFly opened this issue Oct 22, 2024 · 2 comments
Assignees
Labels
triage The bug is unconfirmed and needs to be tested

Comments

@Mart-y-McFly
Copy link

Mart-y-McFly commented Oct 22, 2024

Version of BlockProt

Paper 1.21.1 build #122, BlockProt 1.2.2

Description of the bug

If a large chest is emptied into two hoppers, only the side that was used to unlock the chest is emptied into the hopper under the chest.

Steps to reproduce

  1. build a large chest.
  2. place two single chests one row below and one row in front.
  3. now place the two hoppers under the large chest that lead into the two individual chests.
  4. unlock all the hoppers and chests.
  5. place any stack of items in the large chest and see what happens.

Additional context

In my case, only the chest that is under the side of the large chest that was clicked to unlock is filled.

@Mart-y-McFly Mart-y-McFly added the triage The bug is unconfirmed and needs to be tested label Oct 22, 2024
@Mart-y-McFly
Copy link
Author

The problem also seems to depend on the direction of construction.

@Mart-y-McFly
Copy link
Author

After installing some updates on the server (paper, Geyser, Java, etc.) the problem seems to be solved.

I can't find in the Minecraft documentation whether there is a sequence that regulates which hopper something is passed on to if you only put a single item in a large chest. Maybe that was the problem too, I'll keep watching and tinkering for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage The bug is unconfirmed and needs to be tested
Projects
None yet
Development

No branches or pull requests

2 participants