Joined storage Inheritance
Item/Loose/Fluid storage that is joined directly from output to input should inherit "Stored product" and "keep full/empty" settings from the existing container, and changes to one container should propagate to all connected storages.
Comments: 6
-
28 Sep, '21
Robbin70And if possible set Export to of and Import to off on item connecting to.
-
03 Oct, '21
jack lockwoodYeh it would be good to have the joined storages merge into one entity when directly connected with just one interface
-
14 Oct, '21
DawnmistThere are a few (very few) situations where this would be a nuisance - in particular for maintenance generation where you're wanting to switch from one recipe to another. Being able to queue up the new material into a second container that is connected to the first means that you can do the change-over from one recipe to the next pretty seamlessly/without having to watch the building for when the "old" material runs out to then replace it with the "new" material.
So maybe have it so that by default the storages would inherit their settings, but have a toggle in their interface window to turn inheritance off for those few situations where it would be desired that they have different settings? -
17 Oct, '21
AzanekActually, i think this idea will indrance our freedom. In my gameplay, i build big buffer storage near the coal mine. 6 column of 3 loose storage. The first one is set to keep full, with no export, and the 3rd is set to keep empty with no import. With the advance logistic research it is pretty usefull to manage coal supply around the factory
-
19 Jun, '22
jamesI think the is a good idea, as I have done a similar thing to @Azanek, but some times a truck assigned to the last storage will empty it but just go to the first storage.
-
14 Jul, '22
MoffmasterInheriting the 'full/empty' setting is a bad idea, because then you can't do the "2-chained-storages for mining" thing, where you have the first in the chain assigned to a mine control tower, and the last one set to 'keep empty'.