Always keep one in Storage Chest

[SHiRKiT]

Hello,

I'd like to suggest to Storage Chests to be able to always store 1 of it in it's contents. Or mark them to only accept one kind of item. Although I have almost everything automated (I have factories making almost everything with robots helping them out), sometimes I need to take a look at random items. And I want to organize them. But I just can't, since or I make Requester Chests and request everything from the network (then, I wouldn't be able to use them in the logistics systems) or things goes crazy and I never know in which of my storage chests my items are in.

So:
- Add somehow to storage chests always hold 1 from the logistic network. When picking a place, it would give it priority as expected, but when providing items, if there's only 1 of it, it would provide 0 instead.

[DaveMcW]

You can do this with requesters and smart inserters.

Requester chest requests one item.
Smart inserter moves it to storage chest if the storage chest has no items (circuit condition).

[n9103]

AFAIK, all chests can have filters defined, permanently reserving one slot (or more) for a specific type of item.
I assume this is the solution you're looking to get.
It will ensure everything in storage chests is where you tell it to be.

P.S. The filters on chests are defined the same as anything else, middle mouse button.

[Turtle]

AFAIK, all chests can have filters defined, permanently reserving one slot (or more) for a specific type of item.
I assume this is the solution you're looking to get.
It will ensure everything in storage chests is where you tell it to be.

P.S. The filters on chests are defined the same as anything else, middle mouse button.

Chests do not have filters.

[n9103]

Ah, yes, my mistake, I was thinking about train cargo cars. That's what I get for not clearing my head before trying to answer questions.

Hmm. In that case, I would venture to say that you shouldn't use logistic storage chests at all, and stick to the tried and true provider/requester setups, with a low requester limit. Buffers can be implemented either on the production side by allowing the provider chests to completely fill, or on the consumption side by either requesting more, or putting in a chest between the requester chest and it's destination.

Personally, I would generally avoid much of a buffer beyond what the belts already create.

[Turtle]

What's your playstyle like in terms of storage? Do you want a centralized place to keep extras? Do you like to keep belts backed up or keep them flowing with just enough parts to keep things working?

[Khyron]

@SHiRKiT
Hey, can you explain the problem more clearly? I don't understand how that solution will help.