Quick Answer
A basic hopper sorter exists to do one job: pull one chosen item into one storage lane while everything else keeps moving. The classic tileable design works because the filter hopper holds just enough items to produce the right comparator signal, temporarily unlocking the hopper below it.
Minecraft Wiki’s standard item sorter layout uses 41-1-1-1-1 for normal 64-stack items:
- slot 1 holds 41 of the target item
- slots 2 to 5 each hold 1 filler item
That number pattern is popular because it is stable in tileable designs and helps stop neighboring filters from unlocking at the same time.
Understand These Three Parts First
| Part | What it does | Common mistake |
|---|---|---|
| Input line above | Carries items past the filters | Thinking the filter hopper alone is the whole system |
| Filter hopper | Holds the target item and filler pattern | Treating it like a random buffer instead of a tuned signal source |
| Locked hopper below + torch | Releases filtered items only when the signal threshold is reached | Forgetting this output is supposed to stay locked most of the time |
Stable 64-Stack Filter Pattern
| Slot | What to place |
|---|---|
| Slot 1 | 41 target items |
| Slots 2-5 | 1 filler item each |
Good filler items should be:
- something that does not normally enter your item stream,
- preferably renamed,
- and not a real item type you expect the sorter to handle later.
That protects the filter from eating the wrong item and breaking its own threshold.
What About 16-Stack Items
Items such as ender pearls, eggs, and snowballs cannot use the same 41-item pattern. A common stable approach is 10-1-1-1-1 instead, because the stack cap is much lower and the comparator threshold has to change with it.
Why Sorters Overflow or Cross-Trigger
| Symptom | Usual cause |
|---|---|
| Neighboring filters unlock too | The filter signal climbed high enough to bleed into the next lane |
| Target items skip the chest | The filter numbers are wrong or the transport line is pushing beyond what the design expects |
| Filler items disappear | The filler item type is also present in the real item stream, or it was never renamed |
| One lane eventually breaks the whole wall | The sorter was built without real overflow protection |
Best Troubleshooting Order
- Check the five slots in the filter hopper first.
- Confirm the filler items have not been replaced by real sorted items.
- Recheck comparator, dust, repeater if used, and torch orientation.
- Only then ask whether the transport line is too fast for the design.
Most “my sorter broke” problems are not full rebuild problems. They are slot-count problems.
When Not To Use A Basic Sorter
| Situation | Better approach |
|---|---|
| You want non-stackable sorting | Use a dedicated non-stackable filter design |
| You want one lane to handle multiple variants | That often needs a more advanced system or manual sorting |
| You are building a very high-throughput main hall | Plan the transport line and higher-end filter design first |
| A server plugin changes hopper timing | Verify server behavior before blaming vanilla logic |
Build Checklist Before You Tile A Whole Wall
- Build one lane first and test it before expanding.
- Prepare and rename filler items early.
- Confirm hopper directions before adding storage rows.
- Test with real item stacks immediately instead of after finishing the whole array.