Entity ID based wireless redstone sometimes triggers when no signal sent - items picked up by wrong hopper
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
I've been operating wireless redstone referenced in #6277, and one of the issues I get running it on PaperMC is that items are getting picked up by the wrong hopper. This is all running in the same chunk, there is an ender pearl stasis chamber also in the same chunk, but when I'm offline there are other players nearby (so this is probably getting lazy-loaded at some stage).
The system outputs items from 2 droppers, separated by 2 trapdoors. These items sit on other trapdoors which are then triggered to open, dropping them into 2 hoppers. The trapdoors are set up so that they open inwards, blocking the hoppers from each other. The items should be collected by their respective hoppers, but periodically I come online and find one of the hoppers has started picking up both sets of items.
Observed/Actual behavior
Items start getting collected by the southern hopper, but the configuration of trapdoors means the items ejected above the northern hopper should be collected by the northern hopper
Steps/models to reproduce
Run the wireless redstone receiver referenced in #6277 on a multiplayer server, after time all the items are stuck in one side
Plugin and Datapack List
Same as in #13321
Paper version
Same as in #13321
Other
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the wireless redstone receiver referenced in #6277 and the plugin and Paper-version details referenced in #13321. Reproduce the issue on a multiplayer server with the described hopper and trapdoor setup, then compare item collection after the system has been running and chunks have unloaded or loaded. Done means each hopper consistently collects only its intended items.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100