Ability to create a logistic request, without putting it in the list
Posted: Tue Nov 12, 2024 8:21 pm
So far as I can tell if you create a logistic request either for personal logistics, or through a constant combinator whatever it is will be put up on the logistic list.
I want to request a selection, or a checkbox (on by default I think) for placing the particular request on the list.
While this is generally useful there are cases where doing so simply pollutes up the list, for example if I want to make a logistical train for automated base building I tend to have a bunch of requester chests with long arm inserters. So on one side I might have say 12 requester chests each or most of them requesting a single type of item. The reason I do this is because I filter the contents of the cargo wagon for various needed items. If all requester chests request all the things that might end up in that wagon what can happen is that one inserter will fill up the last slot, but other inserters have already grabbed an item that goes in that slot. What happens now is they hold it until the slot becomes available again, but while that's happening they don't fill up the wagon with other stuff.
So requesting one type of item per requester solves this. But that pollutes the list with a whole bunch of single item requests. Forcing the use of the search function in the future.
But that's not all, if I have a receiving train stop like this
I will use the constant combinator to request items that might be needed in this particular outpost. But since each place will be different it will require different numbers of assemblers/smelters etc. Thus requiring another listing (for example Logistic-Wagon1-StationXYZ) for each combinator for each station. Further polluting the list.
Now if this feature already exists, or it can be circumvented in some fashion I apologise for the hassle, but it seems to me to be worthwhile.
I want to request a selection, or a checkbox (on by default I think) for placing the particular request on the list.
While this is generally useful there are cases where doing so simply pollutes up the list, for example if I want to make a logistical train for automated base building I tend to have a bunch of requester chests with long arm inserters. So on one side I might have say 12 requester chests each or most of them requesting a single type of item. The reason I do this is because I filter the contents of the cargo wagon for various needed items. If all requester chests request all the things that might end up in that wagon what can happen is that one inserter will fill up the last slot, but other inserters have already grabbed an item that goes in that slot. What happens now is they hold it until the slot becomes available again, but while that's happening they don't fill up the wagon with other stuff.
So requesting one type of item per requester solves this. But that pollutes the list with a whole bunch of single item requests. Forcing the use of the search function in the future.
But that's not all, if I have a receiving train stop like this
- obraz.png (1.01 MiB) Viewed 831 times
Now if this feature already exists, or it can be circumvented in some fashion I apologise for the hassle, but it seems to me to be worthwhile.