Mid-tier Logistics Chest
Posted: Fri Sep 23, 2016 8:36 pm
This seems straight forwards enough that I would have thought it was proposed before, but a cursory search didn't find anything.
I would like to see a priority tier between red and blue. That is, a chest that has an item request, and acts as a blue chest, except that requests from the high priority chests can be fulfilled by taking items from it.
This would serve two primary purposes:
1. Easily allow for a low-priority use for items in logistics. Currently this can be done with networked inserters and "network-has > X" rules, but it's a little cumbersome.
2. Allow for item caching. By having a chest attempt to keep a stockpiile of items, burst-loads (such as a player, construction project, etc.) could be fulfilled from that location rather than from however far away the nearest primary-production location is. This would both lower the time to complete the task, and increase off-time robot utilization (effectively by off-loading work to be done at off-peak times). There is no (non-terrible) pure-logistics solution for this currently, as any attempt to request and provide items at the same time will result in a loop.
I would like to see a priority tier between red and blue. That is, a chest that has an item request, and acts as a blue chest, except that requests from the high priority chests can be fulfilled by taking items from it.
This would serve two primary purposes:
1. Easily allow for a low-priority use for items in logistics. Currently this can be done with networked inserters and "network-has > X" rules, but it's a little cumbersome.
2. Allow for item caching. By having a chest attempt to keep a stockpiile of items, burst-loads (such as a player, construction project, etc.) could be fulfilled from that location rather than from however far away the nearest primary-production location is. This would both lower the time to complete the task, and increase off-time robot utilization (effectively by off-loading work to be done at off-peak times). There is no (non-terrible) pure-logistics solution for this currently, as any attempt to request and provide items at the same time will result in a loop.