Logistics Chests - Configurable cap on concurrent worker actions
Posted: Fri Jan 11, 2019 3:04 pm
Yo
So at the moment, logistic chests don't have a cap on the number of requests or deliveries that can be made at once. This leads to some undesirable surging behaviour if you start loading high volumes - say for example, an ore train. If you try to load an ore train from a robo-mine an entire factory's bot count can be sent to one place. At the moment the only way to avoid this is separated logistic areas for volume loading, or avoiding bots.
It strikes me that it'd be a graceful addition to the chest settings to be able to set a cap on concurrent request or pick-up movements - for example a chest may only be allowed to have 10 or 100 bots flying to or from it at once. This would solve the problem of 4,800 logistic bots flying across the entire base to satisfy a refill request of 4800 while not limiting throughput so long as the player sets an appropriate cap.
If the flights are short - as they should be for volume loading - it would mean the closest [n] bots would be allocated to the active chest by the logic, but once the chest is worker capped these same [n] bots will sit in their little work/charge loop and be re-used for further requests rather than waiting for new bots from progressively further and further to arrive.
So at the moment, logistic chests don't have a cap on the number of requests or deliveries that can be made at once. This leads to some undesirable surging behaviour if you start loading high volumes - say for example, an ore train. If you try to load an ore train from a robo-mine an entire factory's bot count can be sent to one place. At the moment the only way to avoid this is separated logistic areas for volume loading, or avoiding bots.
It strikes me that it'd be a graceful addition to the chest settings to be able to set a cap on concurrent request or pick-up movements - for example a chest may only be allowed to have 10 or 100 bots flying to or from it at once. This would solve the problem of 4,800 logistic bots flying across the entire base to satisfy a refill request of 4800 while not limiting throughput so long as the player sets an appropriate cap.
If the flights are short - as they should be for volume loading - it would mean the closest [n] bots would be allocated to the active chest by the logic, but once the chest is worker capped these same [n] bots will sit in their little work/charge loop and be re-used for further requests rather than waiting for new bots from progressively further and further to arrive.