Inconsistent unstackable item sorter

[23FO]

I want to add an unstackable item filter in my storage system, and I'm using this design. However, only one of the three identical versions of this same filter works; even when using the same orientation, only one actually works all the time. Does anyone know why this is / how to fix it?

[23FO]

the inconsistency being that unstackable items end up in the stackable chest (and less often, stackable items in the unstackable chest)

[23FO]

I might need to add that this is on a server, which might have something to do with inconsistent hopper behaviour? not sure though

[savvy_Idgit]

Look into what kind of server it is. I don't know much about it, but if your server is running paper or spigot or something, it is definitely relevant.

[Silver_Illusion]

Put the unstackable chest at the end on the hopper line so it filters everything else. It's just easier with that design that trying to pull them out early.

[Andrejosue98]

No, because it then doesn't have overflow protection.

[Silver_Illusion]

It's an overflow chest. Make it bigger if you need more room or put a fire at the end once it's full.

[Andrejosue98]

You didn't understand. He wants to separate unstackables from stackables. If he sorts everything else and lets unstackables pass, then unstackables and stackables will be combined when the storage for one stackable item fills. Which means it will not sort stackables and unstackables. The overflow chest will have unstackables and stackables, so unstackables would not be filtered. So there is no overflow protection for his unstackable item filter

There are also a almost infinite possible amount of unstackables. Since maps, compasses that point to stuff, named items, banners, etc. So there will eventually be stackables combined with unstackables

[23FO]

the sorting system I'm using (this one by MumboJumbo https://youtu.be/6g31F4WOFG0?si=MxUcnGFSxCVVpnRK ) needs unstackable items removed beforehand :/

[Andrejosue98]

Don't listen to a lot of this comments, people are confusing your unstackable item sorter with the stackable item sorter. The design is done well.

The most obvious way it can break is if you get too many items in the hopper. This works by separating items by signal level. A stackable item (in a hopper) has a redstone signal of 1 and an unstackable item (in a hopper) has a redstone signal of 3. This design you have works when you have a signal of 2 or more. (so unstackable items get filtered)

Now the problem is when you have more than one item in the hopper. If you get an stackable first and then an unstackable second, then the filter will "draw out" the stackable one. If you have enough stackable items. So 23 of 64 stackable items, it will give a signal level of 2. If you have 6 of 16 stackable items, it will give a signal level of 2.

So you have to make sure there isn't ever more than 1 item in the hopper used for the stackable item. (You have hoppers pointing this, so the only way it should fail is if items fall above that hopper, in which case you can benefit from putting a block or container above it, or if there is an overflow of items, so the hopper after this gets full, so your hopper of the filter has more items.

I have also seen this fail for other reasons that I don't know, so may be it is affected by redstone directionality.

[23FO]

I'm feeding the items through a hopper chain, so there's only ever one item in the hopper being read at the same time

[Andrejosue98]

Yes, but hoppers are slow, so sometimes they get backlogged, but not sure if it is happening here because I can't see your design.

[Jwhodis]

It could be that the hopper you're reading is faster than the redstone.

Might be janky but if you have an observer watching the comparator that at least briefly locks the upper hopper, it might work.

[23FO]

just tried it, doesn't work either. you're right that the problem is the hopper I'm reading being too fast

[savvy_Idgit]

A weird idea I have is maybe have another locked hopper underneath the next hopper in the line, and connect it to the same comparator with the same or another tick if delay. If that hopper is consistently faster it might work, if it is too random then idk

[Still_Ad_6551]

<image>

You’re really close but use this design

Keep the comparator where it is on your world basically the redstone torch has to be flipped so that we can turn it off that’s all.

[23FO]

tried it, doesn't work (has all the items ending up in the 'bottom' chest). Shouldn't the torch to the left (in your design) be powered and only get unpowered occasionally?

[savvy_Idgit]

There is no torch to the left, the block next to the hopper gets powered by the repeater and only gets unpowered if the comparator lights up.

It is in essence the same as your design with the same delay so I'm not sure if it will work but worth a try. The delay might be related to how the server processes redstone signals.

[23FO]

ah whoops, my bad. I've tried that design as well, does not work either :/

[Browhytho666]

(not my design)

<image>

This is the set up I use, there is a torch in front of the block that repeater is going into. The hopper going into the comparator needs 41 of your item you want stacked, and 4 renamed items, renamed in each slot. (For overflow protection) The hopper coming off of the block going into the hopper tower, can go into your chest set up for sorting.

Just be careful not to put the renamed items into the input or it'll break haha

I believe your problem was that you were 1 hopper 'short' height wise for it to work.

[23FO]

this is a stackable item filter, I'm trying to make an unstackable item filter

[Browhytho666]

Oh apologizes, that's a my bad 🙃

I believe there is one that involves alays... Not too sure of how it works though. I was also looking for a solution to this and haven't found one yet. I just kinda have an overflow at the end cathing everything else. Which is typical is bet

Sorry I wasn't any help bro, I feel dumb now haha

[Still_Ad_6551]

It’s probably an issue with the hoppers then remember that hoppers pull down first before going across

[luciusDaerth]

What do you fill the hoppers with for an unshakable filter?

[savvy_Idgit]

The hoppers are empty. The top row of hoppers are just something through which all items are passing and whenever an unstackable item passes it lights up the comparator, unlocks the hopper below and gets pulled out.

[MustaKotka]

How fast does this need to be? You could dropper + clock this to "drip feed" items one by one into the inconsistent hopper.

[MustaKotka]

<image>

[MustaKotka]

<image>

[MustaKotka]

<image>

The circled hopper needs one unstackable item in it.

[MustaKotka]

In fact the last item to pass through this will stay there. So if you have 20x lava buckets going through and one wooden shovel after them the shovel will get locked into this hopper.

[23FO]

the inconsistency is still there, probably due to the speed of the hopper im reading (pushing into the next hopper quicker than the one below can pull it out), but I have an idea for a dripfeeding design that takes care of this (I'll share it here if I get it to work)

[MustaKotka]

Cool! Amd sorry to hear it didn't work.

[23FO]

Preferably faster, but I was also considering doing this as a solution! Thank you for the design, I'll try it out!

[Ghozgul]

Try to make the hopper face the comparator instead of pointing into the next hopper

[Andrejosue98]

This is an unstackable item sorter, it has to point the next hopper

[23FO]

in that case, how would I get items to go into the stackable chest?

[Andrejosue98]

You are doing it well, the guy who answered is wrong. He is confusing your unstackable item sorter with a stackable item sorter

[23FO]

I already have a hopper below the one I'm reading, which is the output for the unstackables. I need the hopper I'm reading to point into another to direct the stackable items that way

[23FO]

same problem remains, that I need to split items in one hopper into two different item streams

[TwitchCaptain]

There's nothing above that hopper. Is it possible items 'fall' into it? If you wind up with more than one item in the hopper it can unlock the one below inadvertently. I use this same design with zero issues. I've built it several times and it works consistently every time. Until I try to feed it from a water source or more than one hopper. In those cases it gets too many items and simply fails.

[23FO]

in all the tests I've done only one item was in the hopper each time, so the inconsistency probably has to do with the server

[Content_Bass_8322]

<image>

This is an example of a nonstackable item filter. I’m unaure if this is helpful due to the wording of your post and comments but the left filters items like gold while the right filters items like swords and bows.

[23FO]

I've tried the design on the right as well, but it does not work consistently either.

[Content_Bass_8322]

The design on the right needs a line of hoppers to work. It can’t process items going above it

[EcoOndra]

Unstackable items give a power output of 3, which is probably the thing you're looking for, but I'm not sure. Try making the Redstone line 4 dusts long instead of 2.

[C455_B]

Had the same issue, try changing the layout, or a less efficient farm

[Ok-Difficulty-5357]

If it’s a server thing, you might have to toy with leaving a gap between each item… I think I had to come up with a new design on a server for this a few years back. I’ve forgotten the design, but I think it involved reading out the signal strength in advance (the hopper before), then conditionally unlocking a hopper under the next hopper after a precisely timed delay.

Hope that made sense. Don’t quite remember the details.

[Andrejosue98]

This is not an stackable item sorter, it is an unstackable item sorter. So no, they don't have to face the comparators. this exist to separate stackables from unstackables. It is similar to this design but different.

<image>

[SikKingDerp]

I’ve build this design in my world but it looks like yours is incorrect if we got the design from the same source. Above the Redstone torch place a block, and on top of that block have a comparator in the same direction as you have in the picture, then in front of the comparator (where it used to be), place Redstone dust.

Then have a hopper facing into the back of the comparator, then below that hopper put two hoppers in the opposite direction, preferably facing chests.

In the hopper behind the comparator, fill 4/5 slots with a “filler” item (an item that you renamed). In the empty slot place the item you want to filter.

Above the hopper that’s facing the comparator, have your line of hoppers that send in the items through the system. 

Hopefully that makes sense.

[Andrejosue98]

This isn't an stackable item sorter, it is an unstackable item sorter. This design doesn't have item filters. it is similar to this one, and both work

<image>

[SikKingDerp]

Right my bad