If it has storage, robots will dock with it, there's no real way to have something that launches them but not let them dock. (or in the case of logistic zone, just set to the size of the footprint of the entity itself, so if it overlaps with another zone, it becomes part of it) the only control you have over what features the roboport has is simply if they're specified or not. Given that everything (Robochest, Logistic zone expander, Charging port and Logistic zone interface) is just a modded roboport. Think of it as a push only Robochest that does not allow robots to land in it.
It would be nice to have a robot launcher platform. Alternativly the ability to filter what kind of robots can land at a given robochest. However, these invariably fill up with the other kind of robots at some point, preventing further release of robots into the wild. I use an inserter to add robots to a robochest, one for logistics, one for construction. While I am here, I would also like to make a suggestion for an additional robot item for Bob: Is there another item that offers this feature? Or do I need to enable vanilla roboports just to have this access available? With Bobs, I am unable to attach a circuit network wire to either the "Robochest" or the "Logistic Zone Expander". This can return the total number of robots (construction and logistics), and how many are free. In vanilla, there is an option to read network contents. This may change based upon responses here. I'm currently working on my robot manufacturing facility, and have come across some items surrounding roboports that I hope to get some clarity around.įor my current settings, I have disabled the default roboports. Bobs is first on the list of major changes, and to wrap my head around it I am working on my blueprints for how things work. Having finished vanilla, I am getting into mods.
0 kommentar(er)
