[2.0.76] Logistic chests can't access logistic network wirelessly for logic purposes
Posted: Mon Apr 20, 2026 10:34 pm
It seems to be more of an oversight than a bug per se and can easily be reproduced:
In the inserter and belt UI one can press the "logistic network" button (on the top right) to allow the machine to read contents of logistic network remotly and have logic implemented based on its contents.
However, logistic chests (all types) don't have this button and don't have this functionality. It leads to silly situations, for example in order to turn a requester chest on or off based on the network's contents, one needs to manually connect it with wire to a roboport.
It is especially annoying with blueprints, as one can't create a blueprint without a roboport when in need of such a mechanism. In both of the examples below the machine (inserter/chest) is turned on or off based on the network, but one of those blueprints is much more cumbersome:
In the inserter and belt UI one can press the "logistic network" button (on the top right) to allow the machine to read contents of logistic network remotly and have logic implemented based on its contents.
However, logistic chests (all types) don't have this button and don't have this functionality. It leads to silly situations, for example in order to turn a requester chest on or off based on the network's contents, one needs to manually connect it with wire to a roboport.
It is especially annoying with blueprints, as one can't create a blueprint without a roboport when in need of such a mechanism. In both of the examples below the machine (inserter/chest) is turned on or off based on the network, but one of those blueprints is much more cumbersome: