Paste to Logistics Storage Chest filter

[gnomister]

So much manual work...

I created this account because this has bothered me so much past.

When I create mall/hub, I have to setup so many storage chest filters!
I want to copy-paste settings to them like I do to request chests. If there are more outputs than one - I don't care - at least use the right-left-click functionality for anything at least-

e: How do I put images?

My played time: https://imgur.com/a/FonPZBl
My hub/mall last built: https://imgur.com/a/LhAGpHp ofc many storage chests

[Koub]

e: How do I put images?

Drag and drop the image in the post you're writing, or click on the "Attachments" tab.

[BlueTemplar]

Pictures don't show because you didn't link them — you linked the page instead.

The reason image storage websites (especially free ones) don't make it as easy as it could be is because by doing this everyone downloading (by looking) at that image is leeching their computing resources.
(It's still easy though, just link the image itself.)

But you should avoid using them anyway, as they cannot be relied on :
https://wiki.archiveteam.org/index.php/ImageShack

You should rather upload the media here, where it will be kept together with the rest of your post, and will avoid these kinds of issues with lost images :
https://www.matrixgames.com/forums/view ... 2#p2827272
(Also I think it makes it easier for back up crawler bots, like those of the Internet Archive ?)

[BlueTemplar]

This is indeed something that a lot of players have wished for, and so made mods for :
https://mods.factorio.com/search?query= ... =relevancy
(I'm kind of surprised that you seem to be the first to make a suggestions thread about it ?!)

[RusselRaZe]

TL;DR:
Copy paste assembler settings to storage chest to set storage chest filter

What?
This suggestion is to let us copy paste (shift+right click > shift+left click) from an assembler to a storage chest (yellow logistics chest) to set the storage chest's filter. Some players, like me, prefer to keep mall items in yellow chests with an item filter instead of red chests because if I need to trash the item, I know it goes back to the chest the assembler is placing it in, which the red chest doesn't do.

Why?
Since we've had copy paste assembler recipe to inserter for a while, being able to quickly set storage chest filter when setting up an assembler would be a nice QoL change that saves the player a few clicks.

[mmmPI]

I like this, there are only very few exceptions i can think of where the assembly machine has more than 1 output , and i think it would be fine in those cases if the first item is the one that gets used as filter.

(edit: i was wrong, for biochamber or assembly processing gleba's fruit, they have 2 ouput, the first one being the seed, for a ctrl shift to paste filer on a storage chest, i would expect the seed to not be the only filter for the storage chest )

[Sworn]

Yah I was going to say, yellow box has only 1 filter slot

[Hares]

Hard +1 on that

[Pzixel]

So it sets the filter based on the machine.

Right now you have to set the chest filter by choosing an item from a huge menu with lots of tabs, it's so inconvenient that a lot of people just place a passive provider chest instead.

It would be a nice QoL change if you could just copy the recipe from the machine and it would set the filter. For example it would really simplify the mall creation process:

1. place a machine
2. place a storage chest
3. select a recipe
4. shift-right click the machine to copy the recipe
5. shift-left click the chest. Now the chest has the same filter as the output of copied machine.
6. repeat for all mall machines.

You can see how much time it saves rather than searching for an item in a menu as you have to do now.

[IsaacOscar]

You can try click the assembling machine, hover over the output slot, press q (the 'pipette' key), click onto the storage chest, then click the filter.
Still a hassle though.

I can't seem to get this to work if the output is a placable building (you cant open the chest, as it will be trying to place a (ghost) building there)

[Koub]

[Koub] Merged several threads with the same suggestion.

[mrvn]

Right now you have to set the chest filter by choosing an item from a huge menu with lots of tabs, it's so inconvenient that a lot of people just place a passive provider chest instead.

The reason you want a passive provider chest is so that any of the item stored somewhere else is used up first.

The reason why you want a storage chest with filter is so that deconstruction returns the item so it can be used as input to the next stage, e.g. yellow belts become red belts.

What you really want is a buffer chest so you get both. It's too bad that that then screws up the roboport statistics because there is no option to read requests without buffer chests.

[IsaacOscar]

The reason why you want a storage chest with filter is so that deconstruction returns the item so it can be used as input to the next stage, e.g. yellow belts become red belts.

I've been using a requester chest or buffer for this purpose...., how is a storage chest beter?
(we should really just delete all of the logistic chests except buffer, and just add some checkbox options as to whether taking items from it is allowed, or storing random trash in it is allowed)

[Hares]

The reason why you want a storage chest with filter is so that deconstruction returns the item so it can be used as input to the next stage, e.g. yellow belts become red belts.

I've been using a requester chest or buffer for this purpose...., how is a storage chest beter?
(we should really just delete all of the logistic chests except buffer, and just add some checkbox options as to whether taking items from it is allowed, or storing random trash in it is allowed)

Requester chest will generate "unfulfilled requests" signal in roboports, possibly triggering a craft or delivery, if such signal is read and processed.

[mrvn]

The reason why you want a storage chest with filter is so that deconstruction returns the item so it can be used as input to the next stage, e.g. yellow belts become red belts.

I've been using a requester chest or buffer for this purpose...., how is a storage chest beter?
(we should really just delete all of the logistic chests except buffer, and just add some checkbox options as to whether taking items from it is allowed, or storing random trash in it is allowed)

+1. I made a similar suggestion before.

But instead of checkmarks the request should have 3 sliders:

1) if below the first then items are requested
2) if above the second the items are requested
3) if above the third then items are trashed (active provider)

A checkmark for "accepts items for storage" would be nice I guess. And allow "anything"/"everything" as item filter.

[Hares]

@mrvn, and how to define where to trash items to?

[mrvn]

@mrvn, and how to define where to trash items to?

The "accept items for storage" checkmark would allow bots do deposite items up to the upper limit, turns it into a storage chest. And the "everything" / "anything" symbols would allow storage of any item. Differecne being that "everything" has the limit for the total items and "anything" a limit per item.

[Pzixel]

Right now you have to set the chest filter by choosing an item from a huge menu with lots of tabs, it's so inconvenient that a lot of people just place a passive provider chest instead.

The reason you want a passive provider chest is so that any of the item stored somewhere else is used up first.

The reason why you want a storage chest with filter is so that deconstruction returns the item so it can be used as input to the next stage, e.g. yellow belts become red belts.

What you really want is a buffer chest so you get both. It's too bad that that then screws up the roboport statistics because there is no option to read requests without buffer chests.

But this is what I said, no? For example I'm creating a belt processing factory, I'd like to use storage chests with filter so that when deconstructing the older belts splitters etc they end up in this factory to be processed into higher tier items. But ATM I just use passive providers *while it's not exactly correct* just because setting each storage chest takes a lot of time. When your mall has a hundred of them you end up thinking like "okay maybe I won't have all items being placed at their proper places, but at least I won't be spending 30 minutes clicking on the boxes".

[IsaacOscar]

But this is what I said, no? For example I'm creating a belt processing factory, I'd like to use storage chests with filter so that when deconstructing the older belts splitters etc they end up in this factory to be processed into higher tier items. But ATM I just use passive providers *while it's not exactly correct* just because setting each storage chest takes a lot of time. When your mall has a hundred of them you end up thinking like "okay maybe I won't have all items being placed at their proper places, but at least I won't be spending 30 minutes clicking on the boxes".

When I upgrade stuff, I just used a requester chest that requests a ridiculous amount of the outdated versions. (a buffer chest would also work)

[mrvn]

Right now you have to set the chest filter by choosing an item from a huge menu with lots of tabs, it's so inconvenient that a lot of people just place a passive provider chest instead.

The reason you want a passive provider chest is so that any of the item stored somewhere else is used up first.

The reason why you want a storage chest with filter is so that deconstruction returns the item so it can be used as input to the next stage, e.g. yellow belts become red belts.

What you really want is a buffer chest so you get both. It's too bad that that then screws up the roboport statistics because there is no option to read requests without buffer chests.

But this is what I said, no? For example I'm creating a belt processing factory, I'd like to use storage chests with filter so that when deconstructing the older belts splitters etc they end up in this factory to be processed into higher tier items. But ATM I just use passive providers *while it's not exactly correct* just because setting each storage chest takes a lot of time. When your mall has a hundred of them you end up thinking like "okay maybe I won't have all items being placed at their proper places, but at least I won't be spending 30 minutes clicking on the boxes".

I'm not disagreeing with you. Just elaborating why people use each chest type.


Have you tried using the template parameters with a blueprint? At a minimum you need to set the recipe in the assembler. I like to also program the inserter removing the product to be limited by the amount in the logistic system. So that's two things I have to set to the product. The storage chest makes 3. But I think they could all be set to a template parameter in a blueprint and then you only set one thing and the assembler, inserter and storage chest all get the item type set.